"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. 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). Many applications use a persistent storage mechanism (such as a database) to store data. MVC does not specifically mention this data access layer. Model Ship Builder It's common to think of an application as having three main layers: presentation (UI), domain,and data access. In MVC, the presentation layer is split into controller and view. "

" For an investigator I it makes only sense to consider an entity M as a substitute of an entity O, if I can (1) establish an analogy, similarity, or similar relation between M and O that permits the substitution of O by M with respect to purpose and means, time-horizon etc. , and (2) I can actually investigate M in the required way. That implies firstly that M does not have the properties of O that prevent I from investigating O. Also other properties of O may not be properties of M. In that sense a model is more abstract than its original. Secondly, a model M will in general have properties that O does not have and that actually aid I in investigating M. What the investigator I does in modeling is formulating a problem P in terms of the original O, translate that problem into a problem P' in terms of M, obtain a solution S' of P' and translate S' into a solution candidate S of P in terms of O. Military Ship Model If S is actually a solution of P then the modeling process was successful and can be terminated. If, however, that is not the case then the investigator I can start over with a different problem, model, means of investigation, or relation between model and original. "