1 / 33

Input/Output Design

Input/Output Design. - Physical design of output reports and input forms. System Boundary. Output-design Objectives. Serve the intended purpose Deliver the right quantity of output Deliver it to the right place Provide output on time. Types of Outputs.

jada
Download Presentation

Input/Output Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Input/Output 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

  4. Types of Outputs • Internal outputs stay inside the system to support the system's users and managers • Detailed, Summary, Exception reports • 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

  5. Internal 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. • Summary Reports: • Categorizes information for managers • Exception Reports: • Filter data before it is presented to the manager as information. • Exception reports only report exceptions to some condition or standard.

  6. Detailed Reports

  7. Summary Reports

  8. Exceptional Reports

  9. External Outputs • 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

  10. External Output

  11. Turnaround Output

  12. Output Media • Paper – tabular, zone output • Screen – graphic output • Point-of-Sale (POS) terminal • Video/Audio • Email • Hyperlink

  13. Sample Report Prototype

  14. Example of Graphic Output

  15. Web based Output

  16. System User Issues for Output Design • Besimple to read and interpret. • Be dated and time-stamped. • Include sections and headings • Only required information should be displayed • Computer jargon and error messages should be omitted

  17. Input Design

  18. Input Methods • Keyboard, Mouse, Touch Screen • Point-of-Sale (ATM) • Sound, Speech • Optical Mark (OMR, Barcode) • Smart card • Biometric

  19. Taxonomy • Data capture • the identification and acquisition of new data • Data entry • the process of translating data into a computer-readable format • Data processing

  20. Data Entry / Processing • Batch input • Key-to-disk (KTD) and key-to-tape (KTT) • On-line input • graphical user interface (GUI) • Remote batch

  21. Trends in Automatic Data Collection Technology • Biometric ADC (automatic data capture) • Electromagnetic (radio) • Optical (Bar coding ) • optical-mark reader (OMR) or optical-character reader (OCR) • Smart Cards • Touch

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

  23. Suggestions for capture data • Include instructions for completing the form • Minimize the amount of handwriting • Data to be entered should be sequenced so that it can be read like book, top to bottom and left to right • When possible, use design based on known metaphors

  24. Use Known Metaphors

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

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

  27. Review Input Requirement

  28. Prototype the Input Screen

  29. Well-designed Source Document

  30. Web-based Input Prototype for Web Shopping Cart

More Related