Model-View-Controller (MVC) is a classic software design pattern commonly used for applications that need the ability to maintain multiple views of the same data. The MVC pattern creates a clean separation of objects into one of three categories — models for maintaining data, views for displaying all or a portion of the data, and controllers for handling events that affect the model or view(s). The separation promotes independent innovation for models, views, and controllers.



Events cause a controller to change a model, view, or both. Dependent views are automatically updated whenever a controller changes an underlying model’s data or properties. Similarly, whenever a controller changes a view, for example, by revealing areas that were previously hidden, the view gets data from the underlying model to refresh itself.

Disclaimer

The views expressed in the blog are those of the author and do not represent necessarily the official policy or position of any other agency, organization, employer, or company. Assumptions made in the study are not reflective of the stand of any entity other than the author. Since we are critically-thinking human beings, these views are always subject to change, revision, and rethinking without notice. While reasonable efforts have been made to obtain accurate information, the author makes no warranty, expressed or implied, as to its accuracy.