← Older revision

Revision as of 14:03, 23 May 2013

Line 1:

+

= Structure =

+

== Conceptual Model ==

+

<cite>The conceptual model is the most fundamental aspect of the interface, describing the relationship between the interface and the outside world. The purpose of the conceptual model is to draw on the user’s past experiences so they can readily understand basic operations and accurately predict functionality.</cite>

+

* Real World, Vision

+

== Task Flow ==

+

<cite>The task flow is concerned with the manner in which users’ complete specific operations with the system. In contrast to the conceptual model, the task flow is largely dependent on the product’s technical environment.</cite>

+

* Core usability goals, Use cases / User requirements, Task aggregation

+

* Personas, Scenarios, Usability criteria, Feature list

+

== Organizational Model ==

+

<cite>The organizational model describes how the system’s content and functionality are ordered and categorized. Also known as the information architecture, the organizational model encompasses both the classification scheme as well as the model of association, hierarchy versus index for example. </cite>

+

* Information architecture, Interface management, Window style, Basic arrangement, Screen design, Design Pattern

+

* [[Projects/Usability/HIG/CentralConfiguration|central configuration]] (content tbd.)

+

* [[Projects/Usability/HIG/NotificationMechanism|Notification mechanism]] (content tbd.)

+

= Behaviour =

+

== Viewing and Navigation ==

+

<cite>The Viewing and Navigation layer encompasses the wide variety of behaviors and operations that allow users to navigate the interface and effect its presentation. </cite>

+

=== General navigation ===

+

* Overlay/Secondary window

+

* Accordion

+

* Tabs

+

* Toolbar

+

* Status bar

+

* Paging

+

=== Access functions ===

+

* Menus

+

* Buttons

+

* Links

+

* Keyboard Access

+

=== Grouping ===

+

* Group box, Panel

+

* Splitter

+

=== Complex views ===

+

* List view

+

* Tree view

+

* Grids

+

== Editing and Manipulation ==

+

<cite>The Editing and Manipulation layer contains the behaviors that result in permanent changes to user’s stored information. … Behaviors in this layer can often be recognized by the following traits: they result in permanent, stored changes; they require an implicit or explicit save operation; and they typically require validation of the input data. </cite>

+

=== Selection ===

+

* 1 of a few n selection (Radio button)

+

* n of a few m selection (Check box)

+

* 1 of some n selection (Drop-down list)

+

* 1 of n selection with possibility to add item (Combo box)

+

* 1 of a huge number of n selection (Extended drop-down list)

+

* n of m selection

+

=== Unconstrained input ===

+

* Edits and Text boxes

+

* Lists with direct input

+

* Complex views with direct input (Grid cell editing)

+

=== Constrained input ===

+

* Numeric input within a range and with fix steps (Spin control)

+

* Arbitrary changes within a range for immediate feedback (Slider)

+

* Special controls (Date picker)

+

== User Assistance ==

+

<cite>Interface elements that inform users of the application’s activity and status, as well as elements dedicated to user education, are all contained in the User Assistance layer. This includes online help, error alerts, and status alerts. </cite>

+

=== User-driven information ===

+

* Tool-tip

+

=== System triggered notification ===

+

* Balloon

+

* [[Projects/Usability/HIG/Notifications|Notification]] is a system-triggered message used to acknowledge about events out of the current context.

+

* Progress indicator

+

=== Disruptive messages ===

+

* Message dialog

+

=== Help system ===

+

* KDE Help

+

= Presentation =

+

== Layout ==

+

<cite>The various design decisions governing the placement and ordering of onscreen elements are expressed in the Layout layer. In addition to providing an ordered visual flow, the Layout layer also supports the Behavior tier by arranging elements in a manner that helps communicate behavior, importance, and usage.</cite>

+

* Resizing

+

* Default and minimal size

+

* Spacing

+

* Alignment & Placement

+

* Color

+

* Icons

+

== Style ==

+

<cite>Like many forms of visual design, the Style layer is concerned with emotion, tone, and visual vocabulary. Because it is the most visible and concrete aspect of an interface, it typically accounts for people’s first impression of a product. Paradoxically however, the ultimate effect of style on overall usability or user satisfaction is minimal.</cite>

+

== Text ==

+

<cite>Contained within the Text layer are all the written, language-based elements of the interface. This includes the labels used to represent the organizational model, the names of the input and navigational controls contained in the Viewing and Navigation layer, and the alert messages and help text used by the User Assistance layer.</cite>

+

* Language localizations

+

* Static text

+

* Control labels

+

<pre>----------------------------------------------legacy stuff--------------------------------------</pre>

__NOTOC__

Please add any guidelines questions or requests to the [[Projects/Usability/HIG_Questions|HIG Questions]] page.

KDE TechBase - Changes related to "Development/Guidelines" [en]

Projects/Usability/HIG