User interface modeling: Difference between revisions

Revision as of 14:30, 27 January 2006

Revision as of 21:45, 23 February 2006

Line 1:

{{wfy}}{{uncat}}

The term '''User Interface Modeling''' is mostly used in an [[IT]]-context. A [[user interface]] [[model]] is a representation of how the end user(s) interact with a computer program or another device and also how the system responds. The modeling task is then to show all the "''directly experienced'' aspects of a thing or device" [Trætteberg2002].

Line 13 ⟶ 12:

Because application models in UML describe few aspects of user interfaces,

and because the model-based user interface development environments (MB-UIDE)

lack ability for modeling applications, the University of Manchester started the reaserchresearch project UMLi in 1998.

UMLi aims to address this problem of designing and implementing user interfaces using a combination of [[Unified Modeling Language|UML]] and MB-UIDE.

Line 34 ⟶ 33:

UML can be used for several of the models mentioned above with varying degree of success, but it lacks support for user modeling, platform modeling and presentation model.

</p>

== Approaches ==

Line 40 ⟶ 38:

===Usage-Centered design===

In usage-centered design, the modeling task is to show how the actual presentation of a planned system and how the user interaction is supposed to happen. This is probably the most praised approach, and it has been used successfully on a variety of small and large-scale projects. Its strengths are in complex problems requireing .

===Content models===

Models of this kind shows the contents of a user interface and its different components. AestethicsAesthetics and behavior details are not included in this kind of models as it is in usage-centered design models.

== References ==

Line 70 ⟶ 66:

</tr>

</table>

[[Category:User interface markup languages]]

[[Category:Graphical user interface]]