Learn > Model & Process > Models
Navigation Model
|
The Navigation Model specifies which objects can be visited by navigation through the user interface, and how this navigation can be performed using access elements, concept and other special elements.
Additionally, the Navigation Model auto-exposes the domain semantics, as a view of the conceptual model.
Navigation design is a critical step in the guilding process. Even simple user interfaces with a non-deep hierarchical structure will very quickly become complex by adding new links. On one hand, additional links improve navigability; on the other hand, they increase the risk of losing orientation. Building a navigation model is not only helpful for documenting the application structure, it also allows for a more structured increase in navigability. 
Note that our Navigation Model is an adaptation of the UWE Navigation Model. We removed some elements, added others, and changed some rules. Below are the building blocks for this model in Himalia: Navigation Class: Represents a concept in domain model that is visited by the user during navigation, usually taking its name (Example: Book, in an application of book sale). Index: Represents an arbitrary collection of different items. An index has at least one default action corresponding to the item selection. Actions in an index could be defined at header or item level. Query: Represents the information gathered by the user, when he is looking for a concept in the user interface. A Query always has a default action: “Search”. Usually, the target of this action is an Index (with the search result). In the Query you can define search parameters and search spaces. Search parameters are user-input filters, while search spaces are a space categorization. For example, in a typical search engine, the input box is a search parameter while the Web/ Desktop/ Images/ Groups categorization are the search spaces. Menu: Gives access to a set of different objects. Each menu item is an action to another navigational element. Edition Class: Specifies a class where the user is entering/modifying data in the system (Examples: to enter a new payment, to modify customer data). Edition attributes denote fields that the user has to complete. Edition Index: Specifies a class where the user is entering/modifying a collection of homogeneous data in the system (Examples: to modify a list of cars sold, to modify the shopping cart content). Edition Index is an Index with edition capabilities. Special Elements: There are two kind of special elements in this model, "Back" and "Home". These nodes make navigation directives directly in the runtime. Action (navigation link): It is directed, and the only association type allowed in the model. It means that the destination element is accessed directly by navigation from the origin. Each connection has a name, an origin and a destination. One navigation connection can have several (but exclusive) destinations. |
| © Copyright 2006 Himalia. |