Wrapping the class in a view model that provides notification (and maybe validation, editing support etc.) is the usual approach. The question is whether the underlying object is modified elsewhere in your process and, if so, whether you want those changes to be automatically reflected in the UI. If you do, you'll need a more centralized approach - usually by way of a service that manages those objects.
If the binding is for reading only you can get away with not implementing INotifyPropertyChanged and just having the binding.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.