title: In MVVM, is every ViewModel coupled to just one Model?
body: <p>In an MVVM implementation, is every <code>ViewModel</code> coupled to just one <code>Model</code>?</p>
  
  <p>I am trying to implement the MVVM pattern in a project but I found that sometimes, a <code>View</code> may need information from multiple <code>Models</code>. </p>
  
  <p>For example, for a <code>UserProfileView</code>, its <code>UserProfileViewModel</code> may need information from <code>UserAccountModel</code>, <code>UserProfileSettingsModel</code>, <code>UserPostsDataModel</code>, etc.</p>
  
  <p>However, in most articles I read about MVVM, the ViewModel only consists on one Model via Dependency Injection. So the constructor takes in only one Model.</p>
  
  <p>How would the <code>ViewModel</code> work when it has to get information from multiple <code>Models</code>? Or would such a situation ever occur in MVVM?</p>
  
  <p>PS: I am not using the Prism or Unity Framework. I am trying to implement similar patterns into a project that I am working on which doesn't use Prism or Unity. That's why I need to understand exactly how some of these things work.</p>