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.
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?)
Machine Display
Access Forms and ReportsLinked or Embedded Objects
Design should describe the approximate display. Graphical design tools will do the details.
Machine Action
Describe the code module or macro that is to be executed. Describe objective rather than code detail.
Web Map
Used to describe Web and other event driven interfacesHas a navigation component and a sequence component
Top Related