1. Output and User Interface Design
PHASE 3: SYSTEMS DESIGN
Chapter 6
Output and User Interface Design

2. Phase Description
Systems Design is the third of five phases in the systems development life cycle (SDLC)
Now you are ready to begin the physical design of the system that will meet the specifications described in the system requirements document
Systems design tasks include output and user interface design, data design, and system architecture

3. Chapter Objectives
Discuss output design issues and various types of output
Design various types of reports, and suggest output controls and security
Explain the concept of user interface design and human-computer interaction, including the basic principles of user-centered design
List specific guidelines for user interface design 3

4. Chapter Objectives
Describe user interface techniques, including screen elements and controls
Explain input design concepts, techniques, and methods
Describe guidelines for data entry screen design
Use validation checks for reducing input errors 3

5. Introduction
Output and user interface design is the first task in the systems design phase of the SDLC
Output design focuses on user needs for screen and printed forms of output, while user interface design stresses user interaction with the computer, including input design and procedures 4

6. Output Design Before designing output, ask yourself several questions:
What is the purpose of the output?
Who wants the information, why it is it needed, and how will it be used?
What specific information will be included?
Will the output be printed, viewed on-screen, or both? What type of device will the output go to?
Your answers will affect your output design strategies

7. Output Design Screen and Print Output
New technology has created other output delivery methods
Specialized Forms of Output
Types of Reports
Screen and Print:
Although we said many years ago we would go to a paperless society, that has not come to be. Because printed reports are still convenient and necessary. Easier to read too.
New Technology:
1) Internet Delivery 2)
3) Audio (clip)
Specialized:
1) ATMs – bank transactions (print deposits/withdraw slips)
2) Plotters producing high-quality maps, blueprints, imaging

8. Printed and Screen Output Reports
Detail reports - Figure 6-4, 6-5
Used to carry out day-to-day business
A well designed detail report provides totals for numeric fields.
They contain:
Detail lines – each record of output
Can be quite lengthy

9. Printed and Screen Output Reports
Exception reports – Figure 6-6
Displays records that meet a specific condition or conditions
Useful when details are not necessary

10. Printed and Screen Output Reports
Summary reports – Figure 6-7
Totals – no details
Higher level = less detail

11. Output Design User Involvement in Output Design Design
Get user approval with each design submission (mock-up or prototype)
Design
Attractive
Easy to understand
Useful information
Too little information  no value to user
Too much information  confusing
GOAL: match report to user’s specific needs
Output must be accurate, complete, current, and secure

12. User Interface Design
Interaction with system  h/w, s/w, screens, menus, output, programs, etc.
Dr. Clare-Marie Karat states that “in this new computer age, the customer is not only right, the customer has rights.”

13. User Interface Design The user rights cited by Dr. Karat include
Perspective  problems are system/not user problems
Installation  user should install/uninstall easily
Compliance  system performs as promised
Instruction  easy-to-use instructions
Control  user should be in control of system
Feedback  system provides clear feedback
Dependencies  system requirements are readily available
Scope  system limits are known
Assistance  system help is provided
Usability  system is intuitive to use

14. User Interface Design Basic Principles of User-Centered Design
Understand the underlying business functions
Look at goals, Analyze FDD
Maximize graphical effectiveness
Use GUI
Profile the system’s users
Accommodate novice to experienced
Think like a user
Terms/metaphors familiar to user
Use prototyping
Storyboard - sketch
Usability metrics – measure user interaction w/system

15. User Interface Design Basic Principles of User-Centered Design
Design a comprehensive interface
Include tasks, commands, communications
Continue the feedback process
Monitor usage after operational and ask for suggestions
Document the interface design
Document screen designs for later use

16. User Interface Design Guidelines for User Interface Design
Focus on basic objectives
Build an interface that is easy to learn and use
Provide features that promote efficiency
Make it easy for users to obtain help or correct errors
Minimize input data problems
Provide feedback to users
Create an attractive layout and design
Use familiar terms and images
Guidelines will help you design data entry screens
Restrict user access to screen locations where data is entered
Provide a descriptive caption for ever field, and show the user where to enter the data and the required or maximum field size
Display a sample format if a user must enter values in a field in a specific format
Require an ending keystroke for every field
Do not require users to type leading zeroes for numeric fields
Do not require users to type trailing zeroes for numbers that include decimals
Provide a way to leave the data entry screen at any time without entering the current record
Provide users with an opportunity to confirm the accuracy of input data before entering it
Provide a means for users to move among fields on the form
Design the screen form layout to match the layout of the source document
Allow users to add, change, delete, and view records
Provide a method to allow users to search for specific information

17. Input Design Input Errors
Reducing the number of input errors improves data quality
A data validation check improves input quality by testing the data and rejecting any entry that fails to meet specified conditions

18. Input Design Input Errors
At least eight types of data validation checks
Sequence check
out of order error
Existence check
record not found
Data type check
no mathematic calculation on character data
Range check – limit check
daily hour range is 0-24
If validation check has MIN or MAX  Limit
if daily hour range is > 0
Reasonableness check
Does the value make sense?

19. Input Design Input Errors
Data Validation checks (continued)
Validity check
referential integrity
Combination check
2+ fields consistent when considered together
Batch controls
totals to verify batch input

20. Chapter Summary Any questions?
The chapter began with a discussion of output design issues and a description of various types of output
User-centered design principles require an analyst to understand the business functions, maximize graphical effectiveness, profile the system’s users, think like a user, use prototyping, design a comprehensive interface, continue the feedback process, and document the interface design
Any questions? 49