User interface modeling: Difference between revisions

Revision as of 09:49, 11 September 2013

Revision as of 01:26, 17 November 2013

Line 36:

== Model types ==

The different aspects of a user interface requires different model types. Some of the models that may be considered for UI-modeling are:

* [[Domain model]], including data model (defines the objects that a user can view, access and manipulate through the user interface)

<ul>

* <li>[[DomainNavigation model]], includingdefines data model (defineshow the objects that a user can view, accesscould andbe manipulatenavigated through the user interface)</li>

<li>* [[NavigationTask model]],. defines how(describes the objectstasks thatan aend user viewperforms couldand bedictates navigatedwhat throughinteraction thecapabilities usermust interfacebe designed)

* <li>[[User model]] (represents the different characteristics of end users and the roles they are playing within the organization)</li>

</li>

* <li>[[Platform model]] (used to model the physical devices that are intended to host the application and how they interact with each other)</li>

<li>[[Task model]]. (describes the tasks an end user performs and dictates what interaction capabilities must be designed)</li>

* <li>[[Dialogue model]] (how users can interact with the objects presentation (as push buttons, commands, etc.), with interaction media (as voice input, touch screen, etc.) and

<li>[[User model]] (represents the different characteristics of end users and the roles they are playing within the organization)</li>

the reactions that the user interface communicates via these objects)</li>

<li>[[Platform model]] (used to model the physical devices that are intended to host the application and how they interact with each other)</li>

* <li>[[Presentation model]] (application appearance, representation of the visual, haptic and auditory elements that the user interface offers to its users)</li>

<li>[[Dialogue model]] (how users can interact with the objects presentation (as push buttons, commands, etc.), with interaction media (as voice input, touch screen, etc.) and

* <li>[[Application model]] (commands and data the application provides)</li>

the reactions that the user interface communicates via these objects)</li>

<li>[[Presentation model]] (application appearance, representation of the visual, haptic and auditory elements that the user interface offers to its users)</li>

<li>[[Application model]] (commands and data the application provides)</li>

</ul>

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.