The document discusses different design patterns for separating logic and representation in applications, including MVC, MVP, MVVM, and others. MVC separates an application into three main components: the model, the view, and the controller. The model handles application data and logic, the view handles displaying data, and the controller handles user input and updating the model. Variations like MVP and MVVM shift responsibilities between components in different ways. The goal of these patterns is to make applications easier to manage, test, and maintain by separating concerns.

1. MVC, MVP, MMVM, ...
Or how I stopped worrying and learned to
separate logic and representation

2. Motivation?
The MVC separation helps you manage complex
applications, because you can focus on one aspect a
time. For example, you can focus on the view
without depending on the business logic. It also
makes it easier to test an application.

3. Model
View
Controller
calls
updates
notifies

4. The Model is the part of the application that handles
the logic for the application data.
Often model objects retrieve data (and store data)
from a database.
The View is the parts of the application that handles
the display of the data.
Most often the views are created from the model data.
The Controller is the part of the application that
handles user interaction.
Typically controllers read data from a view, control
user input, and send input data to the model.

5. ● The view objects in an application are actually a composite
● A controller object implements the strategy for one or more
view objects
● A model object keeps interested objects in an application—
usually view objects—advised of changes in its state.
Classical MVC

6. Model–view–adapter (MVA)
or
mediating-controller MVC
or...
MVP?

7. Behavior of the active model

8. Behavior of the passive model

9. ● View is more loosely coupled to
the model. The presenter is
responsible for binding the model
to the view.
● Easier to unit test because
interaction with the view is
through an interface
● Usually view to presenter map
one to one. Complex views may
have multi presenters.
MVP
● Controller are based on
behaviors and can be shared
across views
● Can be responsible for
determining which view to
display
MVC

10. Presentation Model aka MVVM...
is all about binding (WPF, silverlight, flex, javaFX)

11. http://developer.apple.
com/library/mac/#documentation/General/Conceptual/Coco
aEncyclopedia/Model-View-Controller/Model-View-
Controller.html
Sources:
http://en.wikipedia.
org/wiki/Model%E2%80%
93view%E2%80%
93controller
http://msdn.microsoft.
com/en-us/library/ff649643.
aspx
http://stackoverflow.
com/questions/2056/what-are-
mvp-and-mvc-and-what-is-the-
difference
http://alexander.lds.lg.ua/2010/05/mvvm-model-view-view-model-design-pattern-
for-net-windows-forms-winforms/

12. MVC in Java world
MODEL 1
(not bro)
MVC MODEL 2
(bro)
http://www.javaranch.com/journal/200603/Journal200603.jsp#a5

13. The request processing workflow in
Spring Web MVC (high level)
http://static.springsource.org/spring/docs/3.2.x/spring-framework-reference/html/mvc.html