" 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. View: This renders the model into a form suitable for interaction, typically a user interface element. 1 1200 Model Ship MVC is often seen in web apps: the view is the html page and the code which gathers dynamic data for the page. Controller: This responds to events, typically user actions, and invokes changes on the model (but *not* the view). "

"e. , the model is supposed to deviate from the original and as long as there is a good reason for that one doesn't worry. Software process models are in an idealizing reference mode to the actually realized software process. As the software process model describes how software shall be developed under ideal conditions there is no reason to be worried if one deviates from the model because the real conditions are not ideal. (4) constituting, i. e. , the original is constituted by the model and that makes devations from model to original imposible. Admiralty Model Ship On ontology is in constituting reference mode to the domain it constitutes. The distinction between descriptive and prescriptive reference mode goes at least back to Wieringa, [2]. "