Input/Output Design User Interface Design

1. Input/Output DesignUser Interface Design - Physical design of output reports and input forms

2. System Boundary

3. 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

4. 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

7. 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.

10. Output Media • Paper • Screen • Microfilm/Microfiche • Video/Audio • CDROM, DVD • Other electronic media

11. Output Formats • Tabular output • Zoned output • Graphic output • Narrative output

12. 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.

14. Designing Effective Input

15. Input Methods • Batch input • Key-to-disk (KTD) and key-to-tape (KTT) • On-line input • graphical user interface (GUI) • Remote batch

16. 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

17. 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.

19. 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

20. 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

21. 3 1 2 5 4

22. Example

24. User Interface Design • User interface design is the specification of a conversation between the system user and the computer.

25. 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)

26. 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

27. Providing Feedback • 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 • Prompting Cues • Best to keep as specific as possible • 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

28. 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

29. 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

30. Sample State Transition Diagram

31. The Process of Finalizing Design Specifications • Deliverables and Outcome • Set of physical design specifications • Contains detailed specifications for each part of the system

32. Assignment5: Input/Output Design • Sample reports: outputs created from your prototype system OR your design • Sample Input forms (Web-based) • Sample of help functions