Software Architecture Guide

Graphical User Interfaces provide a rich interaction between the
user and a software system. Such richness is complex to manage, so it’s
important to contain that complexity with a thoughtful architecture. The Forms
and Controls pattern works well for systems with a simple flow, but as it
breaks down under the weight of greater complexity, most people turn to
“Model-View-Controller” (MVC). Sadly MVC is one of the most misunderstood
architectural patterns around, and systems using that name display a range of
important differences, sometimes described under names like Application Model,
Model-View-Presenter, Presentation Model, MVVM, and the like. The best way to
think of MVC is as set of principles including the separation of presentation
from domain logic and synchronizing presentation state through events (the
observer pattern).