" Hence the term architectural pattern may be useful (Buschmann, et al 1996), or perhaps an aggregate design pattern. Operation In broad terms, constructing an application using an MVC architecture involves defining three classes of modules . Model: This is the domain-specific representation of the information on which the application operates. The model is another name for the domain layer. Domain logic adds meaning to raw data e. g. calculating if today is the user's birthday or the totals, taxes and shipping charges for shopping cart items. Boat Model Race View: This renders the model into a form suitable for interaction, typically a user interface element. MVC is often seen in web apps: the view is the html page and the code which gathers dynamic data for the page. "

"? Just because an application responds to events does not mean it is "event driven". Event driven means it spends much of its time waiting for an event and then takes action if and when an event occurs. Contrast this with some programs that do not respond to events at all, but simply do their job and terminate. For example, an operating system command to display the current time. It displays the time and is done; it does not wait for events. For more information, see: Event-driven_programming Implementations The pattern was first described in 1979 by Trygve Reenskaug, then working on Smalltalk at Xerox research labs. This original implementation inspired many other GUI frameworks such as: The NeXTSTEP and OPENSTEP development environments encourage the use of MVC. Boat Devitt Model Cocoa, based on these technologies, also uses MVC. Microsoft Foundation Classes (MFC). "