30.3. The Model-View Separation Principle
This principle has been discussed several times; this section summarizes it.
What kind of visibility should other packages have to the Presentation layer? How should non-window classes communicate with windows? It is desirable that there is no direct coupling from other components to window objects because the windows are related to a particular application, while (ideally) the non-windowing components may be reused in new applications or attached to a new interface. The is the Model-View Separation principle.
In this context, model is a synonym for the Domain layer of objects. View is a synonym for presentation objects, such as windows, applets and reports.
The Model-View Separation principle[4] states ...
Get Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
