IFS310: Module 11

Input/Output Design

- Physical design of output reports and input forms

IFS310: Module 11

System Boundary

IFS310: Module 11

Output-design Objectives

• Serve the intended purpose

• Deliver the right quantity of output

• Deliver it to the right place

• Provide output on time

• Choose the right method

IFS310: Module 11

Types of Outputs

• Internal outputs stay inside the system to support the system's users and managers

• External outputs leave the system to trigger actions on the part of their recipients or confirm actions to their recipients – Turnaround outputs are those which are

typically implemented as a report eventually re-enters the system as an input

IFS310: Module 11

S o u n d S t a g e E n t e r t a i n m e n t C l u bF a x 3 1 7 - 4 9 4 - 0 9 9 9

T h e f o l l o w i n g n u m b e r m u s t a p p e a r o n a l l r e l a t e d c o r r e s p o n d e n c e ,s h i p p i n g p a p e r s , a n d i n v o i c e s :P . O . N U M B E R : 7 1 2 8 1 2

T o : S h i p T o :S o u n d S t a g e E n t e r t a i n m e n t C l u b S o u n d S t a g e E n t e r t a i n m e n t C l u b2 6 2 5 D a r w i n D r i v e S h i p p i n g / R e c e i v i n g S t a t i o nI n d i a n a p o l i s , I N 4 5 2 1 3 B u i l d i n g A

2 6 3 0 D a r w i n D r i v eI n d i a n a p o l i s , I N 4 5 2 1 3

P . O . D A T E R E Q U I S I T I O N E R S H I P V I A F . O . B . P O I N T T E R M S

5 - 3 - 9 6 l d b u p s N 3 0

Q T Y D E S C R I P T I O N U N I T P R I C E T O T A L

1 0 0 0 0 P o w d e r - V H S 1 9 . 9 9 1 9 9 , 9 0 0 . 0 0

5 0 0 0 N o w a n d T h e n - V H S 1 5 . 9 5 7 9 , 7 5 0 . 0 0

2 5 0 0 P u l p F i c t i o n S o u n d t r a c k - C D 7 . 9 9 1 9 , 9 7 5 . 0 0

4 5 0 U 2 o n T o u r - T - s h i r t 3 . 4 9 1 , 5 7 0 . 5 0

S u b t o t a l 3 0 1 , 1 9 5 . 5 0

T a x 1 5 , 0 5 9 . 7 7

T o t a l 3 1 6 , 2 5 5 . 2 7

1 . P l e a s e s e n d t w o c o p i e s o f y o u r i n v o i c e .

2 . E n t e r t h i s o r d e r i n a c c o r d a n c e w i t h t h e p r i c e s , t e r m s , d e l i v e r y m e t h o d , a n ds p e c i f i c a t i o n s l i s t e d a b o v e .

3 . P l e a s e n o t i f y u s i m m e d i a t e l y i f y o u a r e u n a b l e t o s h i p a s s p e c i f i e d .

M a d g e W o r t h y 5 - 4 - 9 6A u t h o r i z e d b y D a t e

IFS310: Module 11

I n v o i c e N o . 3 0 1 2 3 1

N a m e C a r l i n a S m i t h D a t e 7 / 2 1 / 9 7A d d r e s s 3 0 1 9 D u r o c D r i v e O r d e r N o . 3 4 6 9 1 0C i t y L i t t l e R o c k S t a t e A R Z I P 4 2 6 5 3P h o n e 5 0 2 - 4 3 0 - 4 5 4 5 P a y m e n t A m t

D e t a c h a n d r e t u r n t o p p o r t i o n w i t h p a y m e n t

Q t y D e s c r i p t i o n U n i t P r i c e T O T A L1 S t a r W a r s - E m p i r e S t r i k e s B a c k V H S $ 1 9 . 9 9 $ 1 9 . 9 91 E r i c C l a p t o n U n p l u g g e d C D $ 1 3 . 9 9 $ 1 3 . 9 91 A l l a d i n V H S $ 1 7 . 9 5 $ 1 7 . 9 5

S u b T o t a l $ 5 1 . 9 3S h i p p i n g & H a n d l i n g $ 7 . 0 0

C a s h T a x e s $ 2 . 9 5 C h e c k C r e d i t C a r d T O T A L $ 6 1 . 8 8

N a m e C C # O f f i c e U s e O n l y

E x p i r e s

R E T U R N T O P P O R T I O N W I T H P A Y M E N T

S o u n d S t a g e E n t e r t a i n m e n t C l u b2 6 3 0 D a r w i n D r i v e - B l d g BI n d i a n a p o l i s , I N 4 5 2 1 33 1 7 - 4 9 6 - 0 9 9 8 f a x 3 1 7 - 4 9 4 - 0 9 9 9 I N V O I C E

P a y m e n t D e t a i l s

C u s t o m e r

P l e a s e r e t u r n t o p p o r t i o n i n v o i c e w i t h p a y m e n t . M a k e c h e c k s p a y a b l e t o : S o u n d S t a g e E n t e r t a i n m e n t C l u b .

IFS310: Module 11

Types of Outputs• Detailed Reports:

– Present information with little or no filtering or restrictions.

– Some detailed reports are historical in nature.

– Detailed reports confirm and document the successful processing of transactions and serve as an audit trail for subsequent management inquiry.

• Exception Reports:– Filter data before it is presented to the manager as information.

– Exception reports only report exceptions to some condition or

standard.

IFS310: Module 11

Page 1SOUNDSTAGE ENTERTAINMENT CLUB

Products Ordered on 6-31-1996

PO Number Product Number Product Type Quantity In Stock Quantity On Order

112312 102774 Merchandise 273 450202653 Title 75 325393752 Title 251 125

112313 109833 Merchandise 0 200111340 Title 46 150231045 Title 225 1,500253967 Title 332 850

112314 287904 Title 0 2,000699034 Merchandise 0 300836785 Merchandise 35 175984523 Title 213 250

IFS310: Module 11

Page 1SOUNDSTAGE ENTERTAINMENT CLUB

Delinquent Member Accounts as of 7-9-1996 (90 Days Overdue)

Number Name Area Code Phone Extension Balance Due

137842 Joe Dunn 317 490-0012 111 29.43142314 Bob Fischer 501 282-7996 43.97157723 Mary Slatter 218 993-9091 56.99209438 Harold Martin 823 231-8355 33.17237121 Kevin Ditmano 655 219-0988 99.23384563 Rick Carlina 501 454-6311 11.23421134 Barb Kitts 393 789-5412 231 23.66476688 Kenny Bum 443 234-8845 123.77

IFS310: Module 11

Output Media

• Paper

• Screen

• Microfilm/Microfiche

• Video/Audio

• CDROM, DVD

• Other electronic media

IFS310: Module 11

Output Formats

• Tabular output

• Zoned output

• Graphic output

• Narrative output

IFS310: Module 11

System User Issues for Output Design

• Be aware of output bias.• Computer outputs should be simple to read and

interpret.• The timing of computer outputs is important.• The distribution of computer outputs must be

sufficient to assist all relevant system users.• The computer outputs must be acceptable to

the system users who will receive them -> Need for training.

IFS310: Module 11

IFS310: Module 11

Designing Effective Input

IFS310: Module 11

Input Methods

• Batch input– Key-to-disk (KTD) and key-to-tape (KTT)

• On-line input– graphical user interface (GUI)– Remote batch

IFS310: Module 11

Trends in Automatic Data Collection Technology

• Biometric ADC• Electromagnetic (radio)• Magnetic (MICR)• Optical (Bar coding )

– optical-mark reader (OMR) or optical-character reader (OCR)

• Smart Cards• Touch

IFS310: Module 11

System User Issues for Input Design

• Capture only variable data.

• Do not capture data that can be calculated or stored in computer programs.

• Use codes for appropriate attributes.

IFS310: Module 11

Prepared by Kevin C. Dittman forSystems Analysis & Design Methods 4ed

by J . L . Whitten & L . D. Bentley

xxxxx

xxxxxxxxxx xx-xx-xx xxxx

xxxx xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

xxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx next linexxxx xxxxxxxxxxxxxxx xx x.xx xxx.xx stop

xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxx xxxxxxxxxx xx.xxx xx.xxx stop xx-xxx-xxx

Good

Bad

(a)

(b)

IFS310: Module 11

Internal Controls for Inputs

• To ensure that the data input to the computer is accurate and that the system is protected against accidental and intentional errors and abuse, including fraud

• Completeness checks

• Limit and range checks

• Combination checks

IFS310: Module 11

How to Prototype & Design Computer Inputs

• Step 1: Review Input Requirements

• Step 2: Select the GUI Controls

• Step 3: Prototype the Input Screen

• Step 4: If Necessary, Design or Prototype the Source Document

IFS310: Module 11

2

5

13

4

IFS310: Module 11

Example

IFS310: Module 11

IFS310: Module 11

Milestone 6: Input/Output Design

• Sample reports: outputs created from your prototype system OR your design

• Sample Input forms (screen shots)