Dialog Design I

Basic Concepts of Dialog Design

Dialog Outline

Evaluate User ProblemRepresentations, Operations, Memory Aids

Generate Dialog DiagramOutline the structure of the dialog on

paperStart with a Simple Hierarchy StructureRobust and easy to manage

Generate Skeleton Code -- Functions LaterCode that calls screens without actions

Dialog Purpose

Produce Output RepresentationsEnable User to Call Operations and Feed Parameters to ThemAccess Memory AidsProvide Control Mechanisms

Objectives of Good Dialog

Promote man/machine symbiosis.

Identify Problem to be SolvedIdentify Users for the SystemIdentify Functions to be SupportedDesign Dialog

Dialog Design Principles

Machine StatusPrint screen name on screen display, record parameter status.

Shop StandardsConsistent presentation for common operations and messages.

DocumentationRecord objectives. Internal documentation.

ROMC

RepresentationsOperationsMemory AidsControls

Fundamental Principles

Plan ContentMatch User NeedsPlan and TestDetermine Formats

Plan Content

CriteriaBasic output requirementsProcessUser interface needsContentData and processing requirements

beforeFormat

Match User Needs

Natural Action SequencesMinimize Stress FromLack of controlUnexpected EventsNoveltyPoor Responses (e.g. codes)

Focus on HELP whenGetting StartedGetting StuckRecovering

Planning and Testing

Sketch dialog before coding TestRepresentative usersAll hardwareSaturation and degradationLogs (errors, system failures, recovery)SecurityAcceptance measures

Format

InputMatch user expectationsAssure consistent keystrokesPlan defaultsRequest input in user terms

Format

OutputMeet system objectivesPerform business tacticHuman likesShort linesHighlightsAccurate labels, units and titlesMinimize clutterBeware of codesProvoke action (so what?)

Dialog Diagramming

Machine DisplayUser ResponsesMachine Actions* Data* Process

Machine Display

Access Forms and ReportsLinked or Embedded Objects

Design should describe the approximate display. Graphical design tools will do the details.

User Responses

Identify All responsesAssure that there is a machine action for all user actions

Machine Action

Describe the code module or macro that is to be executed. Describe objective rather than code detail.

Formal Design Models

Comparison of tools used for designing program architectures

Web Map

Used to describe Web and other event driven interfacesHas a navigation component and a sequence component

P1P2

Process

Body

P3

P1Home OfficeSmall BusinessEtc.

P2

Process

Action/Event Diagram

Object/Event Hierarchy

Screen NameData Source

Object 1 Event 1.1 ActionData SourceNew Focus

Event 1.2 ActionData SourceNew Focus

Object 2