Chapter15-16.输出输入设计.ppt

* No additional notes. * * No additional notes. * No additional notes: * * No additional notes: * No additional notes. * * No additional notes. * No additional notes. * No additional notes * * 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 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. * No additional notes * 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 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. * No additional notes * 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 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 Optio