Model View Controller Research Paper

5. SYSTEM DESIGN
5.1 SYSTEM ARCHITECTURE DESIGN
The Model-View-Controller (MVC) design pattern assigns objects in an application one of three roles: model, view, or controller. The pattern defines not only the roles objects play in the application, it defines the way objects communicate with each other. Each of the three types of objects is separated from the others by abstract boundaries and communicates with objects of the other types across those boundaries. The collection of objects of a certain MVC type in an application is sometimes referred to as a layer—for example, model layer.
MVC is central to a good design for a Cocoa application. The benefits of adopting this pattern are numerous. Many objects in these applications tend to be more

Both the UIKit and AppKit frameworks provide collections of view classes, and Interface Builder offers dozens of view objects in its Library.
View objects learn about changes in model data through the application’s controller objects and communicate user-initiated changes—for example, text entered in a text field—through controller objects to an application’s model objects. v Controller Objects & Communication:
A controller object acts as an intermediary between one or more of an application’s view objects and one or more of its model objects. Controller objects are thus a conduit through which view objects learn about changes in model objects and vice versa. Controller objects can also perform setup and coordinating tasks for an application and manage the life cycles of other objects.
A controller object interprets user actions made in view objects and communicates new or changed data to the model layer. When model objects change, a controller object communicates that new model data to the view objects so that they can display it. In most Cocoa applications, notifications of state changes in model objects are communicated to view objects through controller objects.
SOCET(IT) 37 GROUP ID:

It is a range between which the user and the system application & device and individual interact.
Purpose:
Ø The purpose of it is to allow the user to interact with the brain of the software.
Ø It will allow user to control the system as per the requirements.
Ø A good and simple interface design results in functional and efficient performance of the system. Ø It helps user to understand and get used to the functionalities.
Ø Interface design with less complexity results in close to nil User errors.
Ø Prevents any action that creates processing or memory