A comparison of model view controller and model view presenter
M. Rizwan Jameel Qureshi, Fatima Sabir

TL;DR
This paper compares the design aspects of MVC and MVP frameworks in web applications, analyzing methodologies, implementation platforms, and environments to understand their differences and use cases.
Contribution
It provides a detailed comparison of MVC and MVP design strategies, highlighting their methodologies and implementation environments in web application development.
Findings
Different design methodologies for MVC and MVP
Implementation platforms vary for MVC and MVP
Analysis of environments suitable for MVC and MVP
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.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering and Design Patterns · Web Applications and Data Management · Service-Oriented Architecture and Web Services
