Figure 10-2 The layout of a data input form using a coding sheet
1. Narrative overview
2. Sample design
3. Testing and usability assessment
Figure 10-3A A data input screen designed as a wireframe
Figure 10-3B A data input screen designed in Microsoft’s Visual Basic.NET
The first section of a design specification contains a general overview of the characteristics of the target users, tasks, system, and environmental factors in which the form or report will be used. The purpose is to explain to those who will actually develop the final form why this form exists and how it will be used so that they can make the appropriate implementation decisions. In this section, you list general information and the assumptions that helped shape the design. For example, Figure 10-4 shows an excerpt of a design specification for a Customer Account Status form for Pine Valley Furniture (PVF). The first section of the specification, Figure 10-4a, provides a narrative overview containing the relevant information to developing and using the form within PVF. The overview explains the tasks supported by the form, where and when the form is used, characteristics of the people using the form, the technology delivering the form, and other pertinent information. For example, if the form is delivered on a visual display terminal, this section would describe the capabilities of this device, such as whether it has a touch screen and whether color and a mouse are available.
Figure 10-4 Design specification for the design of forms and reports
In the second section of the specification, Figure 10-4b, a sample design of the form is shown. This design may be hand drawn using a coding sheet, although in most instances it is developed using standard development tools. Using actual development tools allows the design to be more thoroughly tested and assessed. The final section of the specification, Figure 10-4c, provides all testing and usability assessment information. Procedures for assessing designs are described later in this chapter. Some specification information may be irrelevant when designing some forms and reports. For example, the design of a simple Yes/No selection form may be so straightforward that no usability assessment is needed. Also, much of the narrative overview may be unnecessary unless intended to highlight some exception that must be considered during implementation.
Figure 10-5 Contrasting customer information forms (Pine Valley Furniture)
Figure 10-5 (b) Improved design for form
Figure 10-6 Customer account status display using various highlighting techniques (Pine Valley Furniture)
Figure 10-7 Contrasting the display of textual help information
(b) An improved design for a help screen
Figure 10-8 Contrasting the display of tables and lists (Pine Valley Furniture)
Figure 10-8 (b) Improved design for form
Figure 10-9 Tabular report illustrating numerous design guidelines (Pine Valley Furniture)
Figure 10-10 Graphs for comparison
(a) Line graph
image6.png
image7.png
image8.png
image9.png
image10.tiff
image11.tiff
image12.png
image13.png
image14.tiff
image15.png
image16.png
image17.png
image18.png
image19.tiff
image20.tiff
image21.png
image22.png
image23.tiff
image24.tiff
image25.png
image26.tiff
image27.tiff
image28.tiff
image29.png
image30.png
image31.png
image32.png
image33.png
image1.png
image2.tiff
image3.tiff
image4.tiff
image5.tiff
__MACOSX/._CH 10 Part 2.docx