Verbal+Visual: MVC Structure. Model, View, Controller.
0 likes324 views
The MVC (Model-View-Controller) is a software architecture pattern that divides applications into three components: model, view, and controller, enhancing maintainability and promoting separation of concerns. The model manages data and business logic, the view represents the user interface, and the controller handles user input and updates the model or view accordingly. This design pattern was developed in the late 1970s by Trygve Reenskaug while at Xerox PARC.
Verbal+Visual: MVC Structure. Model, View, Controller.
- 2. Model View Controller MVC is a pattern of software architecture/development that divides an application into three interrelated components: Model, View, and Controller. MVC is designed and implemented to improve maintainability and provide Separation of Concerns, a key principle in computer science. examples of MVC frameworks include:
- 3. Norwegian computer scientist Trygve Reenskaug is credited with conceiving of MVC as a design pattern in the late 1970’s while visiting Xerox PARC*. *PARC is credited with developing laser printing, Ethernet, the modern personal computer, GUI, object-oriented programming, and much more.
- 4. M: Model The Model is responsible for managing the the data, logic, and rules of an application.
- 6. V: View View is what's presented to the users and how users interact with the application. The view is made with HTML, CSS, JavaScript and often templates, e.g. .liquid and embedded-ruby, etc.
- 8. The controller accepts input and converts it to commands for the model or view. C: Controller
- 11. A controller can send commands to the model to update the model's state (e.g., editing a document). It can also send commands to its associated view to change the view's presentation of the model (e.g., by scrolling through a document). A model stores data that is retrieved to the controller and displayed in the view. Whenever there is a change to the data it is updated by the controller. A view requests information from the controller. The controller fetches it from the model and passes it to the view that the view uses to generate an output representation to the user.