Systems Analysis & Design 1

10th Edition

CHAPTER 7
Input, User Interface, and Output
Design
 Phase Description
2

 PLANNING
 ANALYSIS
 Requirements Modeling
 Data & Process Modeling
 Development Strategies
 DESIGN
 Output & User Interface Design
 Data Design
 System Architecture
 IMPLEMENTATION
 SYSTEMS OPERATION, SUPPORT &
 Content
3

 Input Design
 User Interface Design & human-

computer interaction (HCI)

 Output Design
 Input Design
4

 To ensure the quality, accuracy and

timeliness of input data

 The quality of the output is only as good

as the quality of the input
 Garbage in, garbage out (GIGO)

 Determine how data is captured and

entered
 Input and Data Entry Methods
5

 Batch input
 Data entry is performed on a specified time schedule

 Online input
 Online data entry

 Source data automation

 RFID tags or Magnetic data strips
 POS, ATMs
 Advantage: Immediate validation and availability of
data
 Disadvantage: Slower and more expensive without
the use of source data automation
 Input Volume
6

Guidelines to reduce input volume

1. Inputnecessary data only
2. Do not input retrievable or calculated data

3. Do not input constant data

4. Use codes
 Data Entry Screen Design
7

 Guidelines to data entry screens design

1. Restrict user access to screen locations where
data is entered
2. Provide a descriptive caption for every field
3. Display a sample format
4. Require an ending keystroke for every field
5. Do not require users to type leading zeroes for
numeric fields
6. Do not require users to type trailing zeroes for
numbers that include decimals
 Input Design
8

7. Display default values

8. Use a default value
9. Display a list of acceptable values for fields, and provide
meaningful error messages
10. Provide a way to leave the data entry screen at any time
without entering the current record
11. Provide users with an opportunity to confirm the accuracy
of input data before entering it
12. Provide a means for users to move among fields on the
form
13. Design the screen form layout to match the layout of the
source document
14. Allow users to add, change, delete, and view records
15. Provide a method to allow users to search for specific
information
 Input Errors
9

 Data quality
 Data validation
 Test data and reject any entry that fails to
specified conditions
 Input Errors
10

Types of data validation checks

1. Sequence check
2. Existence check

3. Data type check

4. Range check – limit check

5. Reasonableness check

6. Validity check – referential integrity

7. Combination check

8. Batch controls – hash totals

 Source Document
11

A form used to request and

collect data, trigger an
input action and provide
a record of original
transaction
 Input Control
12

• To ensure input data is correct, complete and

secure

• Audit trail(jejak balik sape yg wat mslh)

• Source of data item, when data entered
• How and when data is accessed/changed and by
whom
 Input Control
13

• Data security
• Policies and procedures protect data from loss or
damage or unauthorized access

• Records retention policy

• Encrypted – encryption
 Output Design
14

Start by answering the following

questions:
• Purpose?
• Who? Why? How? What?
• Printed? On-Screen? Both?
• Device type?
• Update frequency?
• Security & confidentiality?
 Output Design – Output Types &
Technology
15

• Internet-based information delivery printed output

• E-mail still is the most
common type of
• Instant Messaging output
• Wireless Devices
 Digital audio, images, and video
 Podcasts
 Automated facsimile systems (Faxback systems)
 Computer output microfilm (COM)
 Computer output to digital media
• Specialized Forms of Output
 Printed and Screen Output
16

Reports
• Detail reports
• Exception reports
• Summary reports
 Detail Report
17

Detail Lines
 Detail Report
18

Control
Breaks
Subtotals

Grand total
 Exception Report
19

 Information on records that might require

action
 Summary Report
20

 Less detail
 For upper level managers
 Report Design
21

 Prepare sample report

o Mock-up or prototype

 Get approval
 Report Design Principle
22

 Attractive, professional, and easy to read

 Report headers and footers
 Page headers and footers
 Column heading alignment
 Column spacing
 Field order
 Detail lines grouping
Report Design Principle

Report Header

Page Header

Group Footer

Report Footer

Page Footer
23
 Report Design Issues
24

0.0 not
printed
Store
number not
repeated

Clerk
position not
printed
 Report Design Principle
25
 Report Design Issues
26

 Uniform, consistent and share common

design elements
 Consistent abbreviations
 Consistent item report
 Preprinted form
 After approval, document the design in a
report analysis form
Fields, data types,
data length,
frequency &
distribution
 Designing Character-Based
Reports
27

• Fixed spacing characters

• High-speed impact printers
• Fast and inexpensive
• Printer spacing chart
 Printing Volume & Time
Requirement
28

• Accurate estimation of print volumes

& time is needed to ensure
 Efficient printing operations
 Timely delivery of reports
 Accurate forecasts of paper and storage

How much paper and how long

will it take to print a report with
2,100,000 records?
 Printing Volume & Time
Requirement
29

 Length calculations
 Time calculations
o Ppm (pages per
minute)
o Line printers often
use greenbar paper
 Output Control & Security
30

 Accurate, complete, current, and secure

 Output control method
 Title, report number & code
 Printing date
 Time period
 Page number and state end of report
 Control total & record count
 Randomly check
 Output Control & Security
31

 Output security
 protects privacy rights
 protects data from theft & unauthorized access
 Output security method
 Limit number of printed copies
 Procedures to ensure report for authorized
recipients
 Secure physical storage IT
 Shred department’s
 Diskless workstations responsibility
 User Interface Design
32

 User Interface describes how users interact

with a computer system.

 Human-computer interaction (HCI) describes

the relationship between computers and
people who use them to perform business-
related tasks

 Main objective is to create a user-friendly

design that is easy to learn and use
 User Interface Design
33

“The user is always right. If there is a

problem with the use of the system, the
system is the problem, not the user”

User rights by Dr. Clare-Marie Karat.

Go to page 302 of the book for other

rights
 Basic Principle of User Centered
Design
34

1. Understand the underlying business functions

2. Maximize graphical effectiveness
3. Profile the system’s users
4. Think like a user
5. Use prototyping
 Storyboard
6. Design a comprehensive interface
7. Continue the feedback process
8. Document the interface design
 User Interface Design
Guidelines
35

1. Focus on basic objectives

2. Build an interface that is easy to learn and use
3. Provide features that promote efficiency
4. Make it easy for users to obtain help or correct
errors
5. Minimize input data problems
6. Provide feedback to users
7. Create an attractive layout and design
8. Use familiar terms Please
and images
refer to text book for
a more comprehensive
guideline coverage
 Label clearly
36

Provide clear
instructions
 Organize tasks,
command and
functions
37
 User Interface Controls
38 Calendar
Control

Toggle
Button
Text Box

Drop-down
List Box Check Box

Radio Button

List Box
 User Interface Controls
39

Dialog Box

form
Switchboard
 User Interface Design
40

Good user interface design is based on a

combination of :
 Ergonomics

 How people work, learn & interact with computers

 Aesthetics
 How an interface can be made attractive and easy
to use
 Interface technology
 Provide operational structure to perform design
objectives
 Chapter Summary
41

 An effective way to reduce input errors is to

reduce input volume
 You can also reduce errors by using well-designed
data entry screens and by using data validation
checks
 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
 Chapter Summary
42

 The chapter ended with a discussion of

output design issues and a description of
various types of output

 Chapter 7 complete