Again, I had it wrong originally, updated, and still might contain stuff wrong, If someone can write a proper answer I'm all for it.
Okay, so I had it wrong. Updated:
THE MVC
- The Model is the background bussiness logic used to work with the data, it can contain the ORM model you have in your example many other things
- The Controller is the class doing something with The Model and producing Data Transfer Object or ViewModel and passing it to the View
- The View uses the Data Transfer Object/ViewModel to present itself
The MVVM
- The Model is the background business logic used to work with the data, it can contain the ORM model you have in your example (same as MVC)
- The ViewModel is the class doing something with The Model and populating data structures (properties) in itself. Then there is something listening (for simplification and because I'm lacking proper knowledge too, let's call it a view)
- The View reacts to the event, looks at the ViewModel property that changed, and draws/updates itself