Slide 2:
MODEL
Business Model
Internal Representation Controller
Business Logic
For user Input and Modification VIEW
Presentation Logic
Display Model MVC(Model View Controller)
Slide 3:
MVC Input --> Processing --> OutputController --> Model --> View
Slide 4:
MVC Architecture:
Slide 5:
The MODEL
Heart of the application
The Model should be independent of both the Controller and the View But it can provide services (methods) for them to use.
Many OO programs achieve independence of the Model from Controller and the View only partially.
Slide 6:
The Controller
Controller decides what the model is to do?
Often, user is in control communication with
the Controller by means of a GUI. In this case, the GUI and the Controller may be the Same.
Input Part: It relays commands from the user to the Model
Slide 7:
The VIEW
Able to see or view what the program is doing?
What the Model is doing?
Passive observer (not affect the model)
Provide methods to access the model
View should not display what the Controller thinks is happening
Outputs a picture of the Model's state
Slide 8:
Goals
Benefits
Separation of concerns
Reuse
Organizes code structure
Independent development
Helps solve the problem of updating an application’s views as its data changes
Independency gives flexibility
Slide 9:
Relationship Between Model and Controller
Almost always be separated
What to do? versus how to do it?
The design of the Controller depends on the Model
The Model should not depend on the Controller
Slide 10:
THANK U!