Interface should be dependent on model
From CSSEMediaWiki
(Difference between revisions)
JaninaVoigt (Talk | contribs) (→See also) |
m |
||
| Line 1: | Line 1: | ||
| − | + | :''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. | 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. | ||
| Line 13: | Line 11: | ||
*[[Circular dependency]] | *[[Circular dependency]] | ||
*[[Separation of concerns]] | *[[Separation of concerns]] | ||
| + | |||
| + | [[Category:Riel's heuristics]] | ||
Revision as of 23:54, 20 July 2009
- 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.
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.
