Why MVC?

Posted by vgondi on May 23rd 2003 to Uncategorized

The present day usability techniques involve the placement of buttons, their names, and interface layout. This is similar to designing the interior layout in architecture. It is important, but It only changes the layout of the room and is not a solution to the bigger problem. We need to look at higher architectural principles to find a pattern in order to understand what is going on. Model view controller paradigm decouples three different components of the system. Thinking about a system along this architectural paradigm makes understanding it a lot simpler. Put in another way, this is a methord for “thinking out of the box”.

The Model refers to a computational approximation or abstraction of some real world process or system the user is dealing with. It not only captures the state of the system, but also how it works. (Nouns and their relationships)

The View caters to the needs of the user while interacting with the system and is responsible for displaying the output of the system.

The Controller is the logic that is present in the system which takes the users interactions and and modifies the model accordingly.

Comments Off on Why MVC?

Comments are closed.