STEP 9. BETA 3 DOCUMENTATION

Table of Contents

Project Title

  1. FINAL REQUIREMENTS SUMMARY
  2. USE CASE SUMMARY
  3. INSTALLATION PLAN
  4. HARDWARE ARCHITECTURE (DEVELOPMENT, TEST AND

    5. PRODUCTION CONFIGURATIONS)

  5. SOFTWARE ARCHIETECTURE (DEVELOPMENT, TEST AND

    6. PRODUCTION CONFIGURATIONS)

  6. VERSION DESCRIPTION DOCUMENT
  7. CODE TESTING PLAN
  8. TRACEABILITY MATRIX
  9. OPEN ISSUES LOG
  10. CODE AND DOCUMENTATION
  11. CODE INSTALLATION INSTRUCTIONS
  12. APPROVAL/CONCURRENCE

Appendices

BETA 3 DOCUMENTATION Instructions

 

 

Project Title

  1. FINAL REQUIREMENTS SUMMARY

    2. Beta 3 is a pre-production level module that contains any changes identified in Beta 2 as well as any missing functionality identified in the design. This is provided to JAD participants, business users, and business system testers for final review prior to a production build that will be used by AIM in testing, training and rollout to SC users.
  2. USE CASE SUMMARY
    3.

    This section should summarize the results of the Beta 3 JAD session(s) and "business use case" material(s) that have been developed to-date. This document is provided to JAD participants.
  3. INSTALLATION PLAN
    4.

    This section should cover the general Beta 3 installation procedures to allow AIM to setup and configure the beta version for user testing.

  4. HARDWARE ARCHITECTURE (DEVELOPMENT, TEST AND

    5. PRODUCTION CONFIGURATIONS)

    This section should provide and overview of the proposed hardware architecture required for support of a Beta 3 test.
  5. SOFTWARE ARCHIETECTURE (DEVELOPMENT, TEST AND

    6. PRODUCTION CONFIGURATIONS)

    This section should provide an overview of the proposed software architecture required for support of a beta 3 test.
  6. VERSION DESCRIPTION DOCUMENT

Version Description Document is computer instructions and data definitions expressed in a programming language or in a form that is output by an assembler, compiler, or other translator.

The development of SC systems is augmented by the sound use of version control software. All work products will be held in version control. This includes source code, images, database scripts, data model, design documents and other work products.

7.0 CODE TESTING PLAN

This section should summarize the development code testing plan steps and procedures to be followed prior to turning over the beta 3 code to AIM.

8.0 TRACEABILITY MATRIX

This section should identify the specific system requirements being covered by the beta 3 version of the software and provide a crosswalk of requirements to functions developed and tested in the beta 3 version.

 

9.0 OPEN ISSUES LOG

All JAD issues are tracked and open issues are tracked in this section of the beta 3 documentation.

10.0 CODE AND DOCUMENTATION

This section summarizes all code and system documentation files/sources required for beta 3 in a quick reference table format for review and reference information.

11.0 CODE INSTALLATION INSTRUCTIONS

This section should cover specific code installation instructions for a

beta 3 installation process.

 

12.0 APPROVAL/CONCURRENCE

Include an appropriate SC concurrence/approval section.

Appendices

Use appendices to document any specific alternative vendor information.