The Beta 1 Documentation is a paper prototype depicting graphical representation of the projected system features. It is to be used in JAD/RAD sessions to elicit user input and feedback as well as to give projections of look and feel concepts to be implemented. It is written concurrently with or soon after the completion of the Project Plan.

This section should summarize the results of the initial user interviews and "business use case" material(s) that have been developed to-date. Use Cases identify more than just the user interface. SC system development uses all Use Cases to identify detail design for each SC system module coded. Each Use Case is developed using Requisite Pro following a customized MS Word template in identifying actors, system requirements, and test requirements. Relationships are established between use cases and requirements to identify elements of the traceability matrix.

Provide a high level outline of the techniques for developing and testing a preliminary version of the project hardware/software (either as a whole or in modular units). The prototype should emulate functionality without such encumbering features as error handling, help messages, security controls and other utilities that are not part of the design logic. Participants in the JAD are provided with the user interface and basic screen flow in Beta 1.

Include an appropriate SC concurrence/approval section.