Structuring the Application - Screen Changes vs. Screens with Multiple Areas

Tasks | Users | Data

At the beginning of the design process, you need to decide about the basic type of your web application. There are two choices, though mixtures between them are quite common:

  • Applications with screen changes
    • No or only few different areas on one screen/page
    • Provides simple, sequential navigation
  • Applications using screens with multiple areas
    • Few or no changes of the main screens/pages, several areas with lot of interaction between them
    • Provides stable context

The following table provides criteria for selecting the basic type or structure for a web application.

 

Tasks

Criterion

Screen Changes

Screen with Multiple Areas

Duration of Processing

long

short

Changes of Processed Objects

few

often

Detail View

seldom needed

often needed

Views

only one view at a time needed

views needed in parallel (e.g. overview and details needed in parallel)

 

Users

Criterion

Screen Changes

Screen with Multiple Areas

Beginner, Casual User

guidance through wizard,
simple rules for screen sequences

only if simple and understandable

Expert

yes, if guidance is useful

complex screens possible/needed

 

Data

Criterion

Screen Changes

Screen with Multiple Areas

Structure

flat (list)

hierarchical data structure (e.g. overview and details)

Volume

wide tables,
large number of fields (forms)

narrow tables,
small number of fields (forms)

 

top

Source:  SAP Interaction Design Guide for Internet Application Components