Model -- view -- controller - wikipedia Model -- view -- controller Diagram of interactions within the MVC pattern. Model -- view -- controller is commonly used for developing software that divides an application into three interconnected parts. This is done to separate internal representations of information from the ways information is presented to and accepted from the user. The MVC design pattern decouples these major components allowing for efficient code reuse and parallel development. Traditionally used for desktop graphical user interfaces ( GUIs ), this architecture has become popular for designing web applications and even mobile, desktop and other clients. Popular programming languages like Java, C#, Ruby, PHP and others have popular MVC frameworks that are currently being used in web application development straight out of the box. Contents 1 Descriptions 1.1 Components 1.2 Interactions 2 History 3 Use in web applications 4 Goals of MVC 4.1 Simultaneous development 4.2 Code reuse 5 Advantages & disadvantages 5.1 Advantages 5.2 Disadvantages 6 See also 7 References 8 Bibliography Descriptions As with other software patterns, MVC expresses the `` core of the solution '' to a problem while allowing it to be adapted for each system. Particular MVC architectures can vary significantly from the traditional description here. Components The model is the central component of the pattern. It expresses the application 's behavior in terms of the problem domain, independent of the user interface. It directly manages the data, logic and rules of the application. A view can be any output representation of information, such as a chart or a diagram. Multiple views of the same information are possible, such as a bar chart for management and a tabular view for accountants. The third part or section, the controller, accepts input and converts it to commands for the model or view. Interactions In addition to dividing the application into three kinds of components, the model -- view -- controller design defines the interactions between them. The model is responsible for managing the data of the application. It receives user input from the controller. The view means presentation of the model in a particular format. The controller responds to the user input and performs interactions on the data model objects. The controller receives the input, optionally validates it and then passes the input to the model. History One of the seminal insights in the early development of graphical user interfaces, MVC became one of the first approaches to describe and implement software constructs in terms of their responsibilities. Trygve Reenskaug introduced MVC into Smalltalk - 76 while visiting the Xerox Palo Alto Research Center ( PARC ) in the 1970s. In the 1980s, Jim Althoff and others implemented a version of MVC for the Smalltalk - 80 class library. Only later did a 1988 article in The Journal of Object Technology ( JOT ) express MVC as a general concept. The MVC pattern has subsequently evolved, giving rise to variants such as hierarchical model -- view -- controller ( HMVC ), model -- view -- adapter ( MVA ), model -- view -- presenter ( MVP ), model -- view -- viewmodel ( MVVM ), and others that adapted MVC to different contexts. The use of the MVC pattern in web applications exploded in popularity after the introduction of NeXT 's WebObjects in 1996, which was originally written in Objective - C ( that borrowed heavily from Smalltalk ) and helped enforce MVC principles. Later, the MVC pattern became popular with Java developers when WebObjects was ported to Java. Later frameworks for Java, such as Spring ( released in October 2002 ), continued the strong bond between Java and MVC. The introduction of the frameworks Django ( July 2005, for Python ) and Rails ( December 2005, for Ruby ), both of which had a strong emphasis on rapid deployment, increased MVC 's popularity outside the traditional enterprise environment in which it has long been popular. MVC web frameworks now hold large market - shares relative to non-MVC web toolkits. Use in web applications Although originally developed for desktop computing, MVC has been widely adopted as an architecture for World Wide Web applications in major programming languages. Several web frameworks have been created that enforce the pattern. These software frameworks vary in their interpretations, mainly in the way that the MVC responsibilities are divided between the client and server. Some web MVC frameworks take a thin client approach that places almost the entire model, view and controller logic on the server. This is reflected in frameworks such as Django, Rails and ASP.NET MVC. In this approach, the client sends either hyperlink requests or form submissions to the controller and then receives a complete and updated web page ( or other document ) from the view ; the model exists entirely on the server. Other frameworks such as AngularJS, EmberJS, JavaScriptMVC and Backbone allow the MVC components to execute partly on the client ( also see Ajax ). Goals of MVC This section possibly contains original research. Please improve it by verifying the claims made and adding inline citations. Statements consisting only of original research should be removed. ( February 2017 ) Simultaneous development Because MVC decouples the various components of an application, developers are able to work in parallel on different components without impacting or blocking one another. For example, a team might divide their developers between the front - end and the back - end. The back - end developers can design the structure of the data and how the user interacts with it without requiring the user interface to be completed. Conversely, the front - end developers are able to design and test the layout of the application prior to the data structure being available. Code reuse By creating components that are independent of each other, developers are able to reuse components quickly and easily in other applications. The same ( or similar ) view for one application can be refactored for another application with different data because the view is simply handling how the data is being displayed to the user. Advantages & disadvantages Advantages Simultaneous development -- Multiple developers can work simultaneously on the model, controller and views. High cohesion -- MVC enables logical grouping of related actions on a controller together. The views for a specific model are also grouped together. Low coupling -- The very nature of the MVC framework is such that there is low coupling among models, views or controllers Ease of modification -- Because of the separation of responsibilities, future development or modification is easier Multiple views for a model -- Models can have multiple views Disadvantages Code navigability -- The framework navigation can be complex because it introduces new layers of abstraction and requires users to adapt to the decomposition criteria of MVC. Multi-artifact consistency -- Decomposing a feature into three artifacts causes scattering. Thus, requiring developers to maintain the consistency of multiple representations at once. Pronounced learning curve -- Knowledge on multiple technologies becomes the norm. Developers using MVC need to be skilled in multiple technologies. See also Hierarchical model -- view -- controller Model -- view -- adapter Model -- view -- presenter Model -- view -- viewmodel Presentation -- abstraction -- control Action -- domain -- responder Observer pattern Strategy pattern Naked objects References Jump up ^ `` More deeply, the framework exists to separate the representation of information from user interaction. '' The DCI Architecture : A New Vision of Object - Oriented Programming -- Trygve Reenskaug and James Coplien -- March 20, 2009. Jump up ^ Burbeck ( 1992 ) : ``... the user input, the modeling of the external world, and the visual feedback to the user are explicitly separated and handled by three types of object. '' Jump up ^ Davis, Ian. `` What Are The Benefits of MVC ? ''. Internet Alchemy. Retrieved 2016 - 11 - 29. Jump up ^ Gamma, Erich et al. ( 1994 ) Design Patterns Jump up ^ Moore, Dana et al. ( 2007 ) Professional Rich Internet Applications : Ajax and Beyond : `` Since the origin of MVC, there have been many interpretations of the pattern. The concept has been adapted and applied in very different ways to a wide variety of systems and architectures. '' Jump up ^ Burbeck, Steve ( 1992 ) Applications Programming in Smalltalk - 80 : How to use Model -- View -- Controller ( MVC ) Jump up ^ Simple Example of MVC ( Model -- View -- Controller ) Design Pattern for Abstraction Jump up ^ Buschmann, Frank ( 1996 ) Pattern - Oriented Software Architecture. Jump up ^ Model -- View -- Controller History. C2.com ( 2012 - 05 - 11 ). Retrieved on 2013 - 12 - 09. Jump up ^ Notes and Historical documents from Trygve Reenskaug, inventor of MVC. Jump up ^ `` A note on DynaBook requirements '', Trygve Reenskaug, 22 March 1979, SysReq. pdf. Jump up ^ Krasner, Glenn E. ; Pope, Stephen T. ( Aug -- Sep 1988 ). `` A cookbook for using the model -- view controller user interface paradigm in Smalltalk - 80 ''. The Journal of Object Technology. SIGS Publications. Also published as `` A Description of the Model -- View -- Controller User Interface Paradigm in the Smalltalk - 80 System '' ( Report ), ParcPlace Systems ; Retrieved 2012 - 06 - 05. Jump up ^ The evolution of MVC and other UI architectures from Martin Fowler. Jump up ^ Hot Frameworks ^ Jump up to : Leff, Avraham ; Rayfield, James T. ( September 2001 ). Web - Application Development Using the Model / View / Controller Design Pattern. IEEE Enterprise Distributed Object Computing Conference. pp. 118 -- 127. Bibliography Wikibooks has a book on the topic of : Computer Science Design Patterns / Model -- view -- controller hide Software design patterns Gang of Four patterns Creational Abstract factory Builder Factory method Prototype Singleton Structural Adapter Bridge Composite Decorator Facade Flyweight Proxy Behavioral Chain of responsibility Command Interpreter Iterator Mediator Memento Observer State Strategy Template method Visitor Concurrency patterns Active object Balking Binding properties Double - checked locking Event - based asynchronous Guarded suspension Join Lock Monitor Proactor Reactor Read write lock Scheduler Thread pool Thread - local storage Architectural patterns Front controller Interceptor MVC ADR ECS n - tier Specification Publish -- subscribe Naked objects Service locator Active record Identity map Data access object Data transfer object Inversion of control Model 2 Other patterns Blackboard Business delegate Composite entity Dependency injection Intercepting filter Lazy loading Mock object Null object Object pool Servant Twin Type tunnel Method chaining Delegation Books Design Patterns Enterprise Integration Patterns Patterns of Enterprise Application Architecture Analysis patterns People Christopher Alexander Erich Gamma Ralph Johnson John Vlissides Grady Booch Kent Beck Ward Cunningham Martin Fowler Robert Martin Jim Coplien Douglas Schmidt Linda Rising Communities The Hillside Group The Portland Pattern Repository Retrieved from `` https://en.wikipedia.org/w/index.php?title=Model -- view -- controller&oldid = 842259450 '' Categories : Software design patterns Architectural pattern ( computer science ) Hidden categories : All articles with unsourced statements Articles with unsourced statements from October 2016 Articles that may contain original research from February 2017 All articles that may contain original research Talk Contents About Wikipedia Wikibooks Azərbaycanca Български Català Čeština Dansk Deutsch Eesti Ελληνικά Español Esperanto فارسی Français 한국어 Հայերեն हिन्दी Hrvatski Bahasa Indonesia Italiano עברית Latviešu Magyar Монгол Nederlands 日本 語 Norsk Polski Português Română Русский Српски / srpski Srpskohrvatski / српскохрватски Suomi Svenska தமிழ் ไทย Тоҷикӣ Türkçe Українська Tiếng Việt 中文 32 more Edit links This page was last edited on 21 May 2018, at 08 : 51. Text is available under the Creative Commons Attribution - ShareAlike License ; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia ® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. About Wikipedia

Question: what is the main purpose of mvc architecture
Answer: to separate internal representations of information from the ways information is presented to and accepted from the user