Home > Articles > Programming > Windows Programming

  • Print
  • + Share This
This chapter is from the book

Differences Among MVP, MVC, and MVVM

From a high-level perspective, these three patterns are similar. They strive to separate the user interface (UI) logic from the business logic and data tier. The differences among the patterns are relatively small, but they are significant.

The main driver for many of the differences described in this section is testability. A goal of any application architecture is to make the code as testable as possible. In any application, the UI (Winforms, Windows Presentation Foundation [WPF] or Silverlight, or ASP) is notoriously difficult to test. Testing the UI classes means the UI must be instantiated, which causes many problems with automated test runners. Therefore, we try to move as much of our logic out of the view and into other classes.

Model Access

One of the differences among these three patterns is access to the data model. In MVC, both the view and the controller have a reference to the model, as illustrated in Figure 2.1 This structure makes it easier to build views because the view can bind to the data model properties directly. However, this means the views are more difficult to reuse outside of the current application because they are bound to a specific data model that might not be used in another application. It also means the binding logic cannot be tested because it resides in the view.

Figure 2.1

Figure 2.1. Model-View-Controller

MVP does not allow this reference from the view to the model, so the presenter must take on the responsibilities of binding the data model to the input controls, as illustrated in Figure 2.2. This enhances testability because more code is in the presenter rather than the view; however, implementing binding logic without having direct access to the UI controls can be challenging.

Figure 2.2

Figure 2.2. Model-View-Presenter (Passive view)

MVVM has a concept of a view model that is a class that holds data and logic specifically for that view. It is analogous to the controller or presenter in that it has logic to control the view and that logic is testable. However the question of whether the view should have access to the model is sidestepped with this pattern due to the binding features in WPF. MVVM is used with XAML-based applications, which provides a new way of binding data that does not need a direct reference to the object containing the data. With this new binding method, we can easily refrain from adding any model references to the view. Figure 2.3 shows the relationships in the MVVM pattern.

Figure 2.3

Figure 2.3. Model-View-ViewModel

View Models

Only the MVVM pattern mentions the existence of a view model, so it would appear that is the only pattern that uses one, but this isn’t true. An emerging standard is to also use a view model with MVC and MVP patterns, but using a different interpretation of the term view model.

Before we discuss the differences in the interpretations of view model, let’s discuss a common thread that runs through all of them. Whether being used in MVC, MVP, or MVVM, a view model is always used as a container for data necessary to display the view. To illustrate this concept, assume you have a view that manages a user and his security permissions. For the view to display the appropriate data, it needs access to the user entity, a list of security attributes granted to the user, a list of all security attributes that exist, and a system configuration setting of the minimum number of characters required in a password. Listing 2.1 illustrates the view, the controller, and the logic necessary to create the view and display it on the screen.

Listing 2.1. A Sample View Interface

using System.Collections.Generic;

namespace CodeSamples.Ch02_ApplicationArchitecture.Listing01
{

  public class SampleView
  {
    private User User { get; set; }
    private ICollection<UserRole> AvailableRoles { get; set; }
    private int RequiredPasswordChars { get; set; }

    public SampleView (User usr, ICollection<UserRole> roles,
 int passwordLen)
    {
      this.User = usr;
      this.AvailableRoles = roles;
      this.RequiredPasswordChars = passwordLen;
    }

    public void Show()
    {
      //show the view
    }
  }

  public class SampleViewController
  {
    public SampleViewController()
    {
      var repo = new Repository();
      var usr = repo.GetUserInfo();
      var roles = repo.GetUserRoles();
      var passwordLen = repo.GetPasswordChars();
      var view = new SampleView(usr, roles, passwordLen);
      view.Show();
    }
  }

  public class Repository
  {
    public User GetUserInfo()
    {
      //get user info from DB
      return new User();
    }

    public List<UserRole> GetUserRoles()
    {
      //get user roles from DB
      return new List<UserRole>();
    }

    public int GetPasswordChars()
    {
      //get required password length from dB
      return 6;
    }
  }

  public class User
  {
    //user info goes here
  }

  public class UserRole
  {
    //security role info goes here
  }
}

This sample uses the traditional controller approach by creating the view and setting each property appropriately before showing the view. A presenter pattern looks similar. The advantage of this approach is how obvious the information needed is for this view to function. Simply examining the constructor line shows the necessary inputs. The disadvantage of this approach is the amount of refactoring necessary should the list of required inputs change. If we decided to add a new parameter to the constructor line, we would have to search for every occurrence of this class and add the parameter, forcing a rebuild (and possibly redistribution to the end user) of every affected DLL.

Applying the common strategy of the view model that each presentation pattern supports, we would create a new class that would contain the data the view needs to use. This structure looks like Listing 2.2.

Listing 2.2. A Sample View Interface with View Model

using System.Collections.Generic;

namespace CodeSamples.Ch02_ApplicationArchitecture.Listing02
{

  public class SampleView
  {
    private SampleViewModel _viewModel;

    public SampleView(SampleViewModel viewModel)
    {
      _viewModel = viewModel;
    }

    public void Show()
    {
      //show the view
    }
  }

  public class SampleViewController
  {
    public SampleViewController()
    {
      var repo = new Repository();
      var vm = new SampleViewModel();
      vm.User = repo.GetUserInfo();
      vm.AvailableRoles = repo.GetUserRoles();
      vm.RequiredPasswordChars = repo.GetPasswordChars();
      var view = new SampleView(vm);
      view.Show();
    }
  }

  public class SampleViewModel
  {
    public User User { get; set; }
    public ICollection<UserRole> AvailableRoles { get; set; }
    public int RequiredPasswordChars { get; set; }
  }

  public class Repository
  {
    public User GetUserInfo()
    {
      //get user info from DB
      return new User();
    }

    public List<UserRole> GetUserRoles()
    {
      //get user roles from DB
      return new List<UserRole>();
    }

    public int GetPasswordChars()
    {
      //get required password length from dB
      return 6;
    }
  }


  public class User
  {
    //user info goes here
  }

  public class UserRole
  {
    //security role info goes here
  }

}

Listing 2.1 shows an additional class called SampleViewModel. This class has a property for every piece of information that the view needs to interact with the user as desired. To create and use the view, we create this view model class and fill it with the appropriate data. Though it is more difficult to see the data the view requires, refactoring to add additional information is simplified.

If we decide that the view requires more information, this pattern avoids the need to edit the constructor line of each view creation. However, we still have to visit the places where the view is used to fill the view model with the appropriate data, so this structure doesn’t buy us much.

A common implementation that solves this problem is to push view model population into the view model itself, so the caller needs to create only the view model without needing to know what goes inside of it. Consider the implementation shown in Listing 2.3.

Listing 2.3. A View Model Using Repository

using System.Collections.Generic;

namespace CodeSamples.Ch02_ApplicationArchitecture.Listing03
{

  public class SampleView
  {
    private SampleViewModel _viewModel;

    public SampleView(SampleViewModel viewModel)
    {
      _viewModel = viewModel;
    }

    public void Show()
    {
      //show the view
    }
  }

  public class SampleViewController
  {
    public SampleViewController()
    {
      var repo = new Repository();
      var vm = new SampleViewModel(repo);
      var view = new SampleView(vm);
      view.Show();
    }
  }

  public class SampleViewModel
  {
    public User User { get; set; }
    public ICollection<UserRole> AvailableRoles { get; set; }
    public int RequiredPasswordChars { get; set; }

    public SampleViewModel(Repository repo)
    {
      this.User = repo.GetUserInfo();
      this.AvailableRoles = repo.GetUserRoles();
      this.RequiredPasswordChars = repo.GetPasswordChars();
    }
  }

  public class Repository
  {
    public User GetUserInfo()
    {
      //get user info from DB
      return new User();
    }

    public List<UserRole> GetUserRoles()
    {
      //get user roles from DB
      return new List<UserRole>();
    }

    public int GetPasswordChars()
    {
      //get required password length from dB
      return 6;
    }
  }

  public class User
  {
    //user info goes here
  }

  public class UserRole
  {
    //security role info goes here
  }

}

In this code sample, we pass the Repository to the view model when creating it. This enables us to centralize the code necessary to populate the view model appropriately, and it insulates the controller from the need to know what parameters are necessary for the view model. However, notice that the view model properties are all public, so if there are special circumstances where the controller wishes to replace the default values in the view model, that is possible. When using a view model with the MVC or MVP pattern, this is the view model to use.

In this implementation, the only thing that is needed from the caller is the Repository to use. Even this requirement can be removed if we create our Repository inside the view model, but this is not a good idea for various reasons we discuss in Chapter 10, “Establishing the Foundation.”

Adding the logic for the view model to populate itself introduces the difference among all the interpretations of the responsibilities of a view model. The three presentation patterns disagree on the amount of business logic that should be placed in the view model. For strict MVC or MVP implementations, use the view model just like it is—as a convenient container for view data. The other end of the spectrum is the MVVM pattern, which places all of the business logic necessary for the view into the view model. Most MVC or MVP implementations fall somewhere in the middle.

In summary, though the use of a view model is not in the official description of the MVC or MVP patterns; using a view model with the presentation patterns can be useful and is becoming more commonplace. In this book, we stick with the strict definitions of MVP and MVC, which exclude a view model. However, if you like the pattern and want to use it, your preference does not affect the processes recommended here.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020