Classification of iViews

Classification Based on Typical Usage | Classification Based on Interface Elements

iViews may cover a wide range of applications. To structure the manifold potential types of iViews, this page attempts to classify iViews according to two different criteria: (1) the typical usage scenarios, and (2) the dominant interface element. The following pages present examples for iViews based on the dominant interface element; these are the alert, report, application, text, chart and graphic iView.

Further you can classify Views with respect to whether they are specific to a certain task or user role, or whether they are general in scope and may be used in a variety of contexts and roles. The latter class is called generic iViews. See page Generic iViews for an overview of potential generic iViews.

Classification Based on Typical Usage

The following classification and list of examples of iViews is based on typical uses.

Reports

Reports (tables, graphs)
Ad hoc queries
Quick directories
Top ten
Monitors (real-time reports)
Cockpits (multiple connected graphs and tables)

Information

Messages (transient)
Communication (permanent)
Workflow inbox
Notifications
News, information
Advertisements

Containers

Links as short cuts
MyObjects
Favorites
ToDo
On-Hold
Shared team folders

Applications

Simple data entry apps
Previews of full apps
Wizards
Remote control for devices
Time management
Tools
Toys

Interfaces to Third-Party Applications or ERP Systems

Siebel
Oracle
etc.

Classification Based on Interface Elements

The following iView classification is based on the dominant interface element that an iView contains:

Alert: Contains status information, e.g. status icons
Report: Contains a report (typically a table) or report result (typically a table or chart)
Application: Contains form elements, such as fields, selection elements, and buttons
Text: Contains larger pieces of text (possibly with graphics and links)
Chart: Contains a chart
Graphics: Contains an image, diagram, sketch, photo, or other graphical element

We use this classification for the iView examples on the following pages because from an interface and visual design point of view the interface elements are the relevant features of an iView.

top