" A view object can register itself with the model and listen for changes but the model itself remains view-agnostic. The controller does not pass domain objects (the model) to the view although it might issue a command telling the view to update itself . The user interface waits for further user interactions, which begins the cycle anew. Benefits and liabilities Although widely used, MVC has both advantages and disadvantages compared to other design options, and individual circumstances should be used to choose the most appropriate design. We discuss some of those here. View instability vs. model stability If constructed correctly, models can enjoy a fair degree of stability (owing to the stability of the domain model), whereas user interface code usually undergoes frequent and sometimes dramatic change (typically because of usability problems, the need to support growing classes of users, or simply the need to keep the application looking "fresh"). Model Building Kit Separating the view from the model makes the model more robust, because the developer is less likely to "break" the model while reworking the view. Attempting to stitch these two worlds together in a hand coded method without architecture is very common, and results in the model object being polluted with knowledge of the interface, and vice-versa. "

" (4) constituting, i. e. , the original is constituted by the model and that makes devations from model to original imposible. 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]. More detail and references regarding models and modeling can be found, e. g. Monogram Model Kit, in [3]. II. "