SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Understanding MVC: The Model-View-Controller Design Pattern in Object-Oriented Programming

phelan-christensen avatar
phelan-christensen
10 diapositives · 254 Views · Oct 25, 2014

In object-oriented programming, the hardest aspect is determining which objects to create and their responsibilities. Design patterns aid in organizing solutions to common challenges. MVC (Model-View-Controller) is a widely used pattern that separates the application into three components. The Model represents the application's data, the View displays its state, and the Controller manages user input. This separation of concerns enhances flexibility and robustness, ensuring that changes in one part do not impact the others. Learn how to effectively implement this design pattern for scalable applications.

Understanding MVC: The Model-View-Controller Design Pattern in Object-Oriented Programming - slide 1
01 / 10Understanding MVC: The Model-View-Controller Design Pattern in Object-Oriented Programming
1 / 17

Télécharger la présentation

Understanding MVC: The Model-View-Controller Design Pattern in Object-Oriented Programming
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. MVC Fall 2005 OOPD John Anthony

  2. Design Patterns • The hard problem in O-O programming is deciding what objects to have, and what their responsibilities are • Design Patterns describe the higher-level organization of solutions to common problems • More on these later….

  3. The MVC pattern • MVC stands for Model-View-Controller • The Model is the actual internal representation • The View (or a View) is a way of looking at or displaying the model • The Controller provides for user input and modification • These three components are usually implemented as separate classes

  4. The Model • Most programs are supposed to do work, not just be "another pretty face" • but there are some exceptions • useful programs existed long before GUIs • The Model is the part that does the work--it models the actual problem being solved • The Model should be independent of both the Controller and the View • But it can provide services (methods) for them to use • Independence gives flexibility, robustness

  5. The Controller • The Controller decides what the model is to do • Often, the user is put in control by means of a GUI • the GUI and the Controller are often the same • The Controller and the Model can almost always be separated (what to do versus how to do it) • The Model should not depend on the Controller

  6. The View • Typically, the user has to be able to see, or view, what the program is doing • The View shows what the Model is doing • The View is a passive observer; it should not affect the model • The Model should be independent of the View, but (but it can provide access methods)

  7. Combining the Controller and View • Sometimes the Controller and View are combined, especially in small programs • Combining the Controller and View is appropriate if they are very interdependent • The Model should still be independent • Never mix Model code with GUI code!

  8. Separation of concerns • As always, you want code independence • The Model should not be contaminated with control code or display code • The View should represent the Model as it really is, not some remembered status • The Controller should talk to the Model and View, not manipulate them • The Controller can set variables that the Model and View can read

  9. MVC Model Receives notifications from creates Retrieves state from View Controller User interface User input

  10. View Model Controller Another view….