Output Design and Prototyping Objectives:

1. 15-1 Output Design and PrototypingObjectives: Distinguish between internal, external, and turnaround outputs. Differentiate between detailed, summary, and exception reports. Identify several output implementation methods. Differentiate among tabular, zoned, and graphic formats for presenting information. Distinguish among area, bar, column, pie, line, radar, donut, and scatter charts and their uses. Describe several general principles that are important to output design. Design and prototype computer outputs. No additional notesNo additional notes

2. 15-2 Taxonomy for Computer-Generated Outputs Teaching Notes This slide (and the next) is positioned after the definitions in the belief that students often learn better in lecture situations by first learning details and then seeing how those details fit together. If you prefer to teach structure first and then fill in the details, then move these two slides to just after the Chapter Map. If this slide is difficult to read, refer students to Figure 15-1 in the text. Note that these categories are not necessarily mutually exclusive.Teaching Notes This slide (and the next) is positioned after the definitions in the belief that students often learn better in lecture situations by first learning details and then seeing how those details fit together. If you prefer to teach structure first and then fill in the details, then move these two slides to just after the Chapter Map. If this slide is difficult to read, refer students to Figure 15-1 in the text. Note that these categories are not necessarily mutually exclusive.

3. 15-3 Taxonomy for Computer-Generated Outputs (concluded) Teaching Notes This slide (and the previous one) is positioned after the definitions in the belief that students often learn better in lecture situations by first learning details and then seeing how those details fit together. If you prefer to teach structure first and then fill in the details, then move these two slides to just after the Chapter Map. If this slide is difficult to read, refer students to Figure 15-1 in the text. Note that these categories are not necessarily mutually exclusive.Teaching Notes This slide (and the previous one) is positioned after the definitions in the belief that students often learn better in lecture situations by first learning details and then seeing how those details fit together. If you prefer to teach structure first and then fill in the details, then move these two slides to just after the Chapter Map. If this slide is difficult to read, refer students to Figure 15-1 in the text. Note that these categories are not necessarily mutually exclusive.

4. 15-4 Internal Outputs Internal output � an output intended for system owners and system users within an organization. Detailed report � an internal output that presents information with little or no filtering Example: A listing of all customers Summary report � an internal output that categorizes information for managers Do not have to wade through details. Increasingly presented in graphical formats using charts Example: A count of customers by region Exception report � An internal output that filters data to report exceptions to some condition or standard. Example: A listing of customers with past due accounts No additional notesNo additional notes

5. 15-5 Detailed Report No additional notesNo additional notes

6. 15-6 Summary Report No additional notesNo additional notes

7. 15-7 Exception Report No additional notesNo additional notes

8. 15-8 External Outputs External outputs � an output that leaves the organization organization. Intended for customers, suppliers, partners, or regulatory agencies. Turnaround documents � an external output that may re-enter the system as an input. Most �bills� and invoices include a stub to be returned by the customer with payment. No additional notesNo additional notes

9. 15-9 External Document No additional notesNo additional notes

10. 15-10 Turnaround Document No additional notesNo additional notes

11. 15-11 Implementation Methods for Outputs Printed output Tabular output presents information in columns. Zoned output places text and numbers into designated areas Screen output Graphic output is the use of pictorial charts to convey information and demonstrate trends and relationships that cannot be easily seen in tabular formats. Point-of-sale terminals Multimedia E-mail Hyperlinks Microfilm or microfiche No additional notesNo additional notes

12. 15-12 Chart Types Teaching Notes This is material from Figure 15-5. It has been pulled out of the figure so that the text can be larger and more readable.Teaching Notes This is material from Figure 15-5. It has been pulled out of the figure so that the text can be larger and more readable.

13. 15-13 Chart Types (concluded) Teaching Notes This is material from Figure 15-5. It has been pulled out of the figure so that the text can be larger and more readable.Teaching Notes This is material from Figure 15-5. It has been pulled out of the figure so that the text can be larger and more readable.

14. 15-14 Output Design with an Old Style Printer Spacing Chart Teaching Notes When all printouts were done on dot matrix and line printers with mono-spaced fonts (meaning that every character took the same horizontal amount of space), these charts were very useful in laying out charts. Students can see that these charts can be considered �models� or even prototypes of reports. Today GUIs have changed the focus from character spacing to pixels, making these charts irrelevant.Teaching Notes When all printouts were done on dot matrix and line printers with mono-spaced fonts (meaning that every character took the same horizontal amount of space), these charts were very useful in laying out charts. Students can see that these charts can be considered �models� or even prototypes of reports. Today GUIs have changed the focus from character spacing to pixels, making these charts irrelevant.

15. 15-15 Output Design with a Modern CASE Tool Teaching Notes As shown here with System Architect, many CASE tools include facilities for report and screen layout Another approach used today is to develop working prototypes with PC-database applications. Tools such as Visio or even spreadsheets can be used to quickly develop non-working output prototypes.Teaching Notes As shown here with System Architect, many CASE tools include facilities for report and screen layout Another approach used today is to develop working prototypes with PC-database applications. Tools such as Visio or even spreadsheets can be used to quickly develop non-working output prototypes.

16. 15-16 Output Design with a Report Writer Tool Teaching Notes A final way to design output with a GUI report writer tool, such as Seagate Crystal Reports (shown here). Tools such as this create the actual �code� to be integrated in the operational information system.Teaching Notes A final way to design output with a GUI report writer tool, such as Seagate Crystal Reports (shown here). Tools such as this create the actual �code� to be integrated in the operational information system.

17. 15-17 Output Design with a Report Writer Tool (continued) No additional notesNo additional notes

18. 15-18 Output Design Guidelines Outputs should be simple to read and interpret. Include a title. Date and time stamp. Include sections and headings to segment information. Clearly label all fields and columns. Include legends for all abbreviations. Include only required information. For online outputs, provide methods to expand and contract levels of detail. Report information in format that does not have to be manually edited. Information should be balanced across the page or screen. Provide for easy navigation. Avoid computer jargon and error messages. Teaching Notes If the designer does not understand the purpose of the report or the information in it well enough to do all of these things, then he or she is not yet ready to design the report! Design guidelines are continued on the next slide.Teaching Notes If the designer does not understand the purpose of the report or the information in it well enough to do all of these things, then he or she is not yet ready to design the report! Design guidelines are continued on the next slide.

19. 15-19 Output Design Guidelines (cont.) The timing of outputs is important. This can affect how the output is designed an implemented The distribution of (or access to) outputs must be sufficient to assist all relevant users. The choice of implementation method affects distribution Outputs must be acceptable to the system users who will receive them. Systems analyst must understand how the recipient plans to use the output No additional notesNo additional notes

20. 15-20 Output Design Process Identify system outputs and review logical requirements. Specify physical output requirements. As necessary, design any preprinted forms. Design, validate and test outputs using some combination of: Layout tools (e.g., hand sketches, spacing charts, or CASE tools. Prototyping tools (e.g., spreadsheet, PC DBMS, 4GL) Code generating tools (e.g., report writer) Teaching Notes The next slide shows a logical data structure for output requirements (related to step 1). Following slides present other output design principles.Teaching Notes The next slide shows a logical data structure for output requirements (related to step 1). Following slides present other output design principles.

21. 15-21 A Logical Data Structure for Output Requirements INVOICE = INVOICE NUMBER + INVOICE DATE + CUSTOMER NUMBER + CUSTOMER NAME + CUSTOMER BILLING ADDRESS = ADDRESS > + 1 { SERVICE DATE + SERVICE PROVIDED + SERVICE CHARGE } n + PREVIOUS BALANCE DUE + PAYMENTS RECEIVED + TOTAL NEW SERVICE CHARGES + INTEREST CHARGES + NEW BALANCE DUE + MINIMUM PAYMENT DUE + PAYMENT DUE DATE + ( DEFAULT CREDIT CARD NUMBER ) + ( [ CREDIT MESSAGE, PAYMENT MESSAGE ] ) ADDRESS = ( POST OFFICE BOX NUMBER ) + STREET ADDRESS + CITY + STATE + POSTAL ZONE Teaching Notes It may be useful to walk through this technique for specifying �logical� output requirements. The red and blue symbols are relational operators, that is, they specify the relationship between attributes to be included on the output in terms of Sequence + Selection [ data attributes] Iteration min { data attributes } max Optionality ( data attributes) Many CASE tools support this logical notationTeaching Notes It may be useful to walk through this technique for specifying �logical� output requirements. The red and blue symbols are relational operators, that is, they specify the relationship between attributes to be included on the output in terms of Sequence + Selection [ data attributes] Iteration min { data attributes } max Optionality ( data attributes) Many CASE tools support this logical notation

22. 15-22 Tabular Report Design Principles Teaching Notes Refer to Figure 15-9 in the text for a more readable version.Teaching Notes Refer to Figure 15-9 in the text for a more readable version.

23. 15-23 Tabular Report Design Principles (cont.) No additional notes No additional notes

24. 15-24 Tabular Report Design Principles (concluded) No additional notes No additional notes

25. 15-25 Screen Output Design Principles Teaching Notes Refer to Figure 15-10 in the text for a more readable version. Teaching Notes Refer to Figure 15-10 in the text for a more readable version.

26. 15-26 Report Customization Teaching Notes Adding a user dialogue to a report is a powerful way to give users the ability to customize a report for various kinds of detail, exceptions, and summarization (see Slide 4). These screens must be prototyped and approved by users as well as the reports. Ask students what types of things would be asked of users as they review this output customization dialogue prototype. Teaching Notes Adding a user dialogue to a report is a powerful way to give users the ability to customize a report for various kinds of detail, exceptions, and summarization (see Slide 4). These screens must be prototyped and approved by users as well as the reports. Ask students what types of things would be asked of users as they review this output customization dialogue prototype.

27. 15-27 Tabular Report Prototype Teaching Notes Ask students what types of things would be asked of users as they review this output prototype. Teaching Notes Ask students what types of things would be asked of users as they review this output prototype.

28. 15-28 Graphical Report Prototype No additional notes No additional notes

29. 15-29 Record-at-a-Time Output Prototype Teaching Notes This kind of output is useful for on-screen browsing and can eliminate a lot of printing costs Teaching Notes This kind of output is useful for on-screen browsing and can eliminate a lot of printing costs

30. 15-30 Web Database Output Prototype Teaching Notes Ask students how they would verify this prototype. Who would they ask? What would they ask them? How are web outputs different than other outputs? Teaching Notes Ask students how they would verify this prototype. Who would they ask? What would they ask them? How are web outputs different than other outputs?

31. 15-31 Windows/Web Media Player Output Prototype No additional notes No additional notes

32. 15-32 Output Design: Exercise Identify UI output design features that you believe will be most critical for your project. Explain.