Object-Oriented Systems Analysis and
Design
Joey F. George, Dinesh Batra,
Joseph S. Valacich, Jeffrey A. Hoffer
13-1
© Prentice Hall, 2004

 - Concept of User interface
– Forms and reports
– General guidelines for forms and reports
– Dialogue design
– Usability Testing; Web Usability
Chapter 13
© Prentice Hall, 2004
13-2

Note: In OO Development, user interface is designed in cycles.
Chapter 13
© Prentice Hall, 2004
13-3

• UI refers to all the screens through which
User provides input to the system and gets output from the system.
• Forms and reports are types of UI supporting access to databases.
- Very common since databases part of almost any system.
- BUT, not only type of UI!!! (book’s bias)
Chapter 13
© Prentice Hall, 2004
13-4

 - Input and output object
 - Input form object: A business document that contains some predefined data and may include some areas where additional data are to be filled in
 - Typically based on a database record or query
Chapter 13
© Prentice Hall, 2004
13-5

 A business document that contains only predefined data
 A passive document meant only for reading or viewing, not data input
 Typically contains data from many unrelated transactions or records
Chapter 13
© Prentice Hall, 2004
13-6

Visual Basic and other development tools provide computer-aided GUI form and report generation.
Chapter 13
13-7
© Prentice Hall, 2004

Chapter 13
© Prentice Hall, 2004
A typical form design specification:
Based on a use case connection –
Boundary Class
Involves three parts:
1) Narrative overview
2) Sample design
3) Assessment
13-8

Chapter 13
© Prentice Hall, 2004
13-9

Chapter 13
© Prentice Hall, 2004
13-10

Chapter 13
© Prentice Hall, 2004
13-11

Grouping, organization, layout, and highlighting are important considerations in form design
Chapter 13
© Prentice Hall, 2004
13-12

Highlighting can include use of upper case, font size differences, bold, italics, underline, boxing, and other approaches.
Chapter 13
© Prentice Hall, 2004
13-13

Chapter 13
© Prentice Hall, 2004
13-14

Business reports are static, no user interaction.
Therefore, business reports are often printed in hardcopy form.
Chapter 13
© Prentice Hall, 2004
13-15

Chapter 13
© Prentice Hall, 2004
13-16

Bar and line graphs give pictorial summary information that can enhance reports and graphs.
Chapter 13
© Prentice Hall, 2004
13-17

 Dialogue - A sequence of interactions between the system
 and a user. Design includes:
–
–
–
–
Layout (of widgets, text, and table data)
Structuring data entry (tab order)
Controlling data input (validation and format controls)
Systems’ Feedback (prompting, status, warning, and error messages)
– Dialogue sequencing
Chapter 13
© Prentice Hall, 2004
13-18

Chapter 13
© Prentice Hall, 2004
A typical interface/dialogue design specification:
Similar to form design, but includes multiple forms and dialogue sequence specifications
13-19

Data entry structure is concerned with navigation flow.
Chapter 13
© Prentice Hall, 2004
13-20

Navigation flow should be natural and intuitive to the user, not disjointed and confusing.
Chapter 13
© Prentice Hall, 2004
13-21

Chapter 13
Also a guideline for UI: Never make slide
13-22

 Status information – keep user informed of what’s going on, helpful when user has to wait for response
 Prompting cues
– tell user when input is needed, and how to provide the input
 Warning or Error
– informs user that something is wrong, either with data entry or system operation
Chapter 13
13-23
© Prentice Hall, 2004

– Consistency
– Allow sequence, shortcuts, and reversals in navigation
– Frequent feedback
– Logical grouping and sequencing of diagrams, with beginning, middle, and end
– Comprehensive error handling
– Maximize ease and control of use
Chapter 13
© Prentice Hall, 2004
13-24

Dialogue sequencing
Chapter 13
© Prentice Hall, 2004
13-25

Chapter 13
© Prentice Hall, 2004
Dialogue diagrams depict the sequence, conditional branching, and repetition of dialogues.
13-26