View source

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: Users.
• You must confirm your e-mail address before editing pages. Please set and validate your e-mail address through your user preferences.

You can view and copy the source of this page:

:''In applications that consist of an object-oriented model interacting with a user interface, the model should never be dependent on the interface. The interface should be dependent on the model.'' --Riel's Heuristic 3.5, [[Arthur Riel 1996]] This heuristic basically says that the model (i.e. the classes that represent domain concepts) should have no knowledge of the user interface. Instead, the interface should know about the domain classes and it should know how to display them. Some flavour of [[Model view controller]] is typically used to accomplish this. One of the reasons why it is bad for the model to know about the interface is that it will make it much harder to switch to using a different user interface. If the user interface is changed (e.g. from text-based to graphical) the model will also be affected. This rule is a more specific version of [[Circular dependency]]. ==See also== *[[Acyclic dependencies principle]] *[[Circular dependency]] *[[Separation of concerns]] *[[Model view controller]] [[Category:Riel's heuristics]]

Return to Interface should be dependent on model.