Model View Controller Architecture
•        Model View Controller is commonly thought of as a software reuse pattern, but it is more of than a
pattern
-        Model View Controller is a way of architecting.
-        The well respected Small Talk framework pioneered MVC.
-        Java and especially J2EE uses an MVC architecture when describing web application best practices.
-        J2EE commonly call MVC “Model 2” in J2EE terminology because the J2EE Blueprints described a
variation of MVC as model 2.
•        MVC is a way of designing that separates three portions of an application.
-        The Model is the business rules and most commonly how the persistent information (Database) is
changed.
-        The View is the presentation or how the application looks.
-        The Controller represents how the application reacts to user input.
•        This separation of concerns allows the view, or Model to be independent of each other.
-        The model can remain unchanged with the view changes.
-        The model and view can use completely different technologies.
-        The controller (in a way) serves as the glue between the model and the view.
MVC
Table of Contents
online learning aid.  Any attempts to copy, reproduce, or use for training is strictly prohibited.
Courseware
Training Resources
Tutorials