The purpose of this activity is to prepare illustrative examples of all outputs and inputs in the system  

OVERVIEW

One of the most difficult tasks is to verbally describe what a report or screen should look like. There have been more misunderstandings in this area than in any other area of information systems design. These misunderstandings can cause re-design and re-programming which will add additional expense and time to the project. A good illustrative example overcomes this problem.

Illustrative examples are needed to allow the user to visualize how the inputs and outputs will actually appear when completed. As they are prepared, actual data values should be used so the user can visualize field alignment (values such as "XXXXX," "ZZZZ.ZZ," "00000," etc. should be avoided). This then becomes the basis for defining the physical characteristics of data (length, class, precision, scale, justification, fill character, void state, validation, etc.).

For additional design tips for creating inputs and outputs that cross geographical borders, see: Creating Universal Systems.

Prototyping aids are very helpful for creating illustrative examples and should be used in this activity. In the absence of such tools, pencil/paper, text editors, etc. should be used to mock-up the outputs and inputs.

When preparing examples, it is important to try and show not only an input or output in its pristine form, but to also show how errors, inconsistencies, messages, and default overrides will be represented. Consideration should also be given to foreign translation.

It is recommended that output examples be prepared before the input examples. Well defined outputs will provide the necessary insight for creating appropriate inputs.

After creating the illustrative examples, Systems Engineering prepares a textual narrative to describe each input and output. This text is appended to the ID/OD Descriptive Text and should describe:

• How headings and footers are produced (including pagination).

• How the body is produced, including special processing rules.

STEPS IN EXECUTION

1. Systems Engineering prepares an illustrative example for each Output and Input in the System.

2. Based on the examples, Systems Engineering updates the physical characteristics of the Data Definitions.

3. Systems Engineering reviews and updates the Descriptive Text for each OD and ID to textually explain the physical appearance of each. This is used to produce the Input Discussion & Examples, and the Output Discussion & Examples for inclusion in the final Phase 2 "System Design Manual."