원문 :http://en.wikipedia.org/wiki/Model-view-controller
As an architectural pattern
It is common to split an application into separate layers that run on different computers: the presentation/user interface (UI), business logic, and data access. In MVC the presentation layer is further separated into Model, view and controller, resulting in three layers.
Model
Is the domain-specific representation of the information on which the application operates. Domain logic adds meaning to raw data (for example, calculating whether today is the user's birthday, or the totals, taxes, and shipping charges for shopping cart items).
Many applications use a persistent storage mechanism (such as a database) to store data. MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the model.
-
View
Renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes.
-
- Controller
Processes and responds to events (typically user actions) and may indirectly invoke changes on the model.
