title: MVC pattern in model with multiple classes
body: <p>When applying the MVC pattern to a design with multiple classes do I need to create a model, view and controller for each of the relevant classes?</p>
  <p>For example, for a design with a domain with <code>UserAccount</code> class, a <code>MultimediaContent</code> class, etc, would I need to design a <code>UserAccountModel</code>, <code>UserAccountView</code>, <code>UserAccountController</code>, and a <code>MultimediaContentModel</code>, <code>MultimediaContentView</code>, <code>MultimediaContentController</code>, etc?</p>
  <p>I've looked for examples online but they all use a single class.</p>