[Paper Review] A comparison of model view controller and model view presenter

M. Rizwan Jameel Qureshi, Fatima Sabir|arXiv (Cornell University)|Aug 25, 2014

Software Engineering and Design Patterns2 references19 citations

TL;DR

This paper compares the Model View Controller (MVC) and Model View Presenter (MVP) architectural patterns in web application development, analyzing their design aspects, implementation methodologies, and suitability for different platforms and environments. The study finds that while both patterns improve separation of concerns, MVP offers better testability and decoupling, making it more suitable for complex, maintainable web applications when proper implementation environments are used.

ABSTRACT

Web application frameworks are managed by using different design strategies. Design strategies are applied by using different design processes. In each design process, requirement specifications are changed in to different design model that describe the detail of different data structure, system architecture, interface and components. Web application frame work is implemented by using Model View Controller (MVC) and Model View Presenter (MVP). These web application models are used to provide standardized view for web applications. This paper mainly focuses on different design aspect of MVC and MVP. Generally we present different methodologies that are related to the implementation of MVC and MVP and implementation of appropriate platform and suitable environment for MVC and MVP.

Motivation & Objective

• To analyze and compare the design aspects of Model View Controller (MVC) and Model View Presenter (MVP) patterns in web application frameworks.
• To evaluate the implementation methodologies and environmental requirements for both MVC and MVP in software development.
• To identify the most suitable platforms and development environments for effective deployment of MVC and MVP.
• To assess the impact of architectural choice on code maintainability, testability, and component decoupling.

Proposed method

• The study uses a comparative analysis of MVC and MVP based on design principles, component responsibilities, and data flow.
• It evaluates both patterns through conceptual modeling and illustrative diagrams (five figures) to depict component interactions.
• The authors examine how each pattern handles separation of concerns, particularly between business logic, user interface, and data management.
• Implementation considerations are discussed, focusing on platform compatibility and development environment requirements.
• The analysis includes a review of existing literature and established practices in software engineering for web frameworks.

Experimental results

Research questions

• RQ1 How do MVC and MVP differ in their architectural responsibilities and component interactions?
• RQ2 What are the key design advantages and limitations of MVC and MVP in web application development?
• RQ3 Which pattern offers better testability and maintainability in complex web applications?
• RQ4 What platform and environmental factors influence the effective implementation of MVC and MVP?

Key findings

• MVP provides better decoupling between the view and controller components, enhancing testability and maintainability.
• MVC tends to have tighter coupling between the view and controller, which can complicate unit testing.
• Both patterns improve separation of concerns, but MVP's explicit presenter layer makes it easier to manage complex UI logic.
• The choice of development platform significantly affects the ease of implementation and long-term maintainability of both patterns.