User interface modeling: Difference between revisions

Revision as of 23:34, 18 January 2006

Revision as of 14:30, 27 January 2006

Line 1:

{{wfy}}{{uncat}}

==Definition==

<p>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].

device" [Trætteberg2002]</p>

<p>Modeling user interfaces is a well-established discipline in its own right. For example, modeling techniques can describe interaction objects, tasks, and lower-level dialogs in user interfaces. Using models as part of user interface development can help capture user requirements, avoid premature commitment to specific layouts and widgets, and make the relationships between an interface’s different parts and their roles explicit. [SilvaPaton2003]</p>

<p>Modeling user interfaces is a well-established discipline in its own right. For example, modeling techniques can describe interaction objects, tasks, and lower-level dialogs in user interfaces. Using models as part of user interface development can help capture user requirements, avoid premature commitment to specific layouts and widgets, and make the relationships between an interface’s different parts and their roles explicit. [SilvaPaton2003]</p>.

== Languages ==

<h3>===UML</h3>===

<p>Some aspects of user interface modeling can be realized using [[Unified Modeling Language|UML]]. However, the language is not mainly intended for this kind of modeling, which may render the models somewhat synthetic.</p>

<h3>===UMLi</h3>===

<p>

[[UMLi]] is an extension of [[Unified Modeling Language|UML]], and adds support for representation commonly occurring in user interfaces.

</p>

<p>

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 reaserch 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.

</p>

<h3>DiaMODL</h3>

<p>DiaMODL combines a dataflow-oriented language (Pisa interactor abstraction) with UML Statecharts which has focus on behaviour. It is capable of modeling the dataflow as well as the behavior of interaction objects. It may be used for documenting the function and structure of concrete user interfaces.</p>

<h3>===DiaMODL</h3>===

<p>DiaMODL combines a dataflow-oriented language (Pisa interactor abstraction) with UML Statecharts which has focus on behaviour. It is capable of modeling the dataflow as well as the behavior of interaction objects. It may be used for documenting the function and structure of concrete user interfaces.</p>

== Model types ==

Line 45 ⟶ 38:

== Approaches ==

There exists several approaches to modeling a user interface.

<h3>===Usage-Centered design</h3>===

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 complex problems requireing

<h3>===Content models</h3>===

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