History of Model View Controller - MVC
Version 2 | Current version | |
---|---|---|
Based upon http://en.wikipedia.org/wiki/Model_view_controller Model-View-Controller (MVC) separates an application's data (model), user interface, and control logic into three distinct components so that modifications to the view component can be made without impacting the data model component. This is useful since models typically enjoy a fair degree of stability, whereas user interface code usually undergoes frequent and dramatic change (owing to usability problems, the need to support growing classes of users, or simply the need to keep the application looking "fresh"). By separating the view from the model, the model becomes more robust, because the developer is less likely to "break" the model while reworking the view. Though MVC comes in different flavors, control flow generally works as follows:
Use of TestingSuites help ensure the model remains extremely stable, while the user interface and control code can be modified accordingly. | Based upon http://en.wikipedia.org/wiki/Model_view_controller Model-View-Controller (MVC) separates an application's data (model), user interface, and control logic into three distinct components so that modifications to the view component can be made without impacting the data model component. This is useful since models typically enjoy a fair degree of stability, whereas user interface code usually undergoes frequent and dramatic change (owing to usability problems, the need to support growing classes of users, or simply the need to keep the application looking "fresh"). By separating the view from the model, the model becomes more robust, because the developer is less likely to "break" the model while reworking the view. Though MVC comes in different flavors, control flow generally works as follows:
Use of TestingSuites help ensure the model remains extremely stable, while the user interface and control code can be modified accordingly. |