BIS 310 Week 8 BIS 310 Structured Analysis

BIS 310: Week 8 BIS 310: Structured Analysis and Design Input/Output Design User Interface Design - Physical design of output reports and input forms

BIS 310: Week 8 System Boundary

BIS 310: Week 8 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

BIS 310: Week 8 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 reenters the system as an input

BIS 310: Week 8

BIS 310: Week 8

BIS 310: Week 8 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.

BIS 310: Week 8

BIS 310: Week 8

BIS 310: Week 8 Output Media • • • Paper Screen Microfilm/Microfiche Video/Audio CDROM, DVD Other electronic media

BIS 310: Week 8 Output Formats • • Tabular output Zoned output Graphic output Narrative output

BIS 310: Week 8 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.

BIS 310: Week 8

BIS 310: Structured Designing Effective Analysis and. Input Design BIS 310: Week 8

BIS 310: Week 8 Input Methods • Batch input – Key-to-disk (KTD) and key-to-tape (KTT) • On-line input – graphical user interface (GUI) – Remote batch

BIS 310: Week 8 Trends in Automatic Data Collection Technology • • Biometric ADC Electromagnetic (radio) Magnetic (MICR) Optical (Bar coding ) – optical-mark reader (OMR) or opticalcharacter reader (OCR) • Smart Cards • Touch

BIS 310: Week 8 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.

BIS 310: Week 8

BIS 310: Week 8 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

BIS 310: Week 8 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

BIS 310: Week 8 1 2 5 4 3

BIS 310: Week 8 Example

BIS 310: Week 8

BIS 310: Week 8 User Interface Design • User interface design is the specification of a conversation between the system user and the computer.

BIS 310: Week 8 Interaction Methods and Devices • Command Language Interaction – Natural Language Interaction • Form Interaction (Fill-in-the-blank) – Key-word search • Menu Interaction • Object-Based Interaction (GUI)

BIS 310: Week 8 Controlling Data Input • One objective of interface design is to reduce data entry errors • Role of systems analyst is to anticipate user errors and design features into the system’s interfaces to avoid, detect and correct data entry mistakes

BIS 310: Week 8 Providing Feedback 1. Status Information – – Keeps users informed of what is going on in system Displaying status information is especially important if the operation takes longer than a second or two 2. Prompting Cues – Best to keep as specific as possible 3. Error and Warning Messages – – Messages should be specific and free of error codes and jargon User should be guided toward a result rather than scolded Use terms familiar to user Be consistent in format and placement of messages

BIS 310: Week 8 Providing Help • Place yourself in user’s place when designing help • Guidelines – Simplicity • Help messages should be short and to the point – Organization • Information in help messages should be easily absorbed by users – Demonstrate • It is useful to explicitly show users how to perform an operation

BIS 310: Week 8 Designing Dialogues • Dialogue – Sequence in which information is displayed to and obtained from a user • Primary design guideline is consistency in sequence of actions, keystrokes and terminology • State Transition Diagram

BIS 310: Week 8 Sample State Transition Diagram

BIS 310: Week 8 The Process of Finalizing Design Specifications • Deliverables and Outcome – Set of physical design specifications • Contains detailed specifications for each part of the system

BIS 310: Week 8 Assignment 5: Input/Output Design • Sample reports: outputs created from your prototype system OR your design • Sample Input forms (Web-based) • Sample of help functions