Advantages of using MVC architecture
Sign up for access to the world's latest research
Abstract
AI
AI
The paper discusses the advantages of using MVC architecture in web application development, highlighting its benefits such as faster development processes, support for asynchronous techniques, multiple view creation, ideal suitability for large applications, data formatting flexibility, and ease of modification. It emphasizes how MVC allows for parallel development, reduces code duplication, and maintains separation of concerns, making it a favorable choice for optimizing web projects in modern development environments.
Related papers
2007
This paper presents a model-driven approach to the development of web applications based on the Ubiquitous Web Application (UWA) design framework, the Model-View-Controller (MVC) architectural pattern and the JavaServer Faces technology. The approach combines a complete and robust methodology for the user-centered conceptual design of web applications with the MVC metaphor, which improves separation of business logic and data presentation.
Procedia Engineering, 2014
In this paper, we present a model for rapid web application development. This model is based on the Model-View-Controller architecture (MVC) and has several other useful components like security, form generation and validation, database access and routing. This model was implemented using the PHP programming language, but it can be implemented in other development languages and environments using the same concepts. Improvements in both development and maintenance time have been the main objectives of this research, with the added benefit of correct and maintainable code.
The Model-View-Controller design pattern is cited as the architectural basis for many J2EE web development frameworks. This paper presents an analysis of those changes, and proposes a separate Web-MVC pattern that more accurately describes how MVC is implemented in web frameworks. The MVC is very useful for constructing dynamic software systems. Partitioning decisions can be changed without modifying the application. This paper brings the conception of Web-Application Partitioning, and programming model that allows engineers to implement the Model View Controller design pattern in a partition-independent manner.
The increasing growth in size and complexity of portals calls for a systematic way to web-application development that is able to face the stringent demands imposed on both the development and maintenance of these systems. Model-based approaches have been proposed to mitigate this situation. These approaches aim to find models, preferably orthogonal, that allow designers to declaratively specify a distinct concern of the application without being immediately immersed in details of implementations. This paper presents AtariX, a model-based tool that renders HTML pages from the declarative schemata specified by the designer. Each concern is described by a separate XML document: how data is integrated and structured (the content document), the topology of links (the navigation document) and the layout of each element (the presentation document). An application is then conformed by a set of schemata (i.e. model instances), for each of the distinct models. Separation of concerns and declarativeness enhance the application maintenability, as well as promoting concurrent development as each model can be assigned to a different team. AtariX has been fully implemented and its use is illustrated by designing and delivering a website for a scientific conference.
Actual Problems of Economics
Recently, the web applications are created in both desktop and mobile versions due to significant increase of mobile devices. This paper describes advantages of using MVC architectural pattern when building applications available on different devices. There are included theoretical analysis about development speed and quality as well as potential business implications of mobile version for the web-based applications.
— Model View Controller (MVC) architecture is implemented over the middleware. MVC is mainly used for developing web applications, because it helps the developer to have a clear understanding of all the modules. MVC architecture separates the business layer (Model logic), the display layer (View logic), and the control layer (Controller logic). This study attempted to understand the implementation difference of MVC architecture using the Struts framework and PHP. MVC architecture is basically used to implement complex real time applications. It is easier to implement MVC architecture in Struts since it supports various IDE (Integrated Development Environment) which has complete support of frameworks. In PHP, the developer needs to create manually frameworks for model, view, and controller. I. INTRODUCTION Model View Controller is popularly known as MVC architecture which is made up of three parts: Model, View and Controller. MVC was designed by Trygve Reenskaug in 1979, to provide better solution for large and complex problem. For the First time it was used in the Smalltalk-80 framework – Used in making Apple interfaces (Lisa and Macintosh) (Reenskaug, 1979). MVC is mainly used for developing web applications, because it helps the developer to have a clear understanding of all the modules. MVC architecture separates the business layer (Model logic), the display layer (View logic), and the control layer (Controller logic). MVC helps to organize the data and separate the code as per requirement, for reducing complexity and working on one file as business logic. Code reusability and flexibility can be achieved by implementing the MVC architecture. Using MVC, the developer has a clear understanding of all the modules.
2010 Seventh International Conference on the Quality of Information and Communications Technology, 2010
Despite several methodologies have been defined to support the disciplined development of Web applications, often such methodologies are not applied in the practice, mainly due to the short time-to-market and resource constraints. As a consequence, existing (i.e. legacy) Web applications often lack in design quality. This paper proposes a model-driven semi-automatic redesign approach to improve the design of existing Web applications. The approach analyzes the client side HTML pages of the application to recover its conceptual model according to the Ubiquitous Web Applications design methodology. The recovered model is then used as a starting point to define a new design for the application, adopting the Model-View-Controller architectural pattern and the JavaServer Faces technology. A concrete example of the application of the approach to redesign a real world Web site is also described.
2007
Refactoring has been growing in importance with recent software engineering approaches, particularly agile methodologies, which promote continuous improvement of an application's code and design. Web applications are especially suitable for refactoring because of their rapid development and continuous evolution.
Clei Electronic Journal, 2018
Many Web applications offer the possibility of distributing their data and their business logic between the client and the server, also allowing an asynchronous communication between them. These features, originally associated with the arrival of Rich Internet Applications (RIA), remain particularly relevant and desirable. In the area of RIA, there are few proposals that simultaneously consider these features, adopt Model-Driven Development (MDD), and use implementation technologies based on scripting. In this work, we start from MoWebA, an MDD approach to web application development, and we extend it by defining a specific architecture model with RIA functionalities, supporting the previously mentioned features. We have defined the necessary metamodels and UML profiles, as well as transformation rules that allow code based on HTML5, Javascript, jQuery, jQuery Datatables and jQuery UI to be generated. The preliminary validation of the proposal shows positive evidences regarding the effectiveness, efficiency and satisfaction of the users with respect to the modeling and code generation processes of the proposal.
CLEI Electronic Journal
Many Web applications have among their features the possibility of distributing their data and their business logic between the client and the server, also allowing an asynchronous communication between them. These features, originally associated with the arrival of Rich Internet Applications (RIA), remain particularly relevant and desirable. In the area of RIA, there are few proposals that simultaneously consider these features, adopt Model-Driven Development (MDD), and use implementation technologies based on scripting. In this work, we start from MoWebA, an MDD approach to web application development, and we extend it by defining a specific architecture model with RIA functionalities, supporting the previously mentioned features. We have defined the necessary metamodels and UML profiles, as well as transformation rules that allow you to generate code based on HTML5, Javascript, jQuery, jQuery Datatables and jQuery UI. The preliminary validation of the proposal shows positive evid...

Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.