STEP 8. BETA 2 DOCUMENTATION

Table of Contents

 

Project Title

1.0 PRELIMINARY REQUIREMENTS SUMMARY

2.0 USE CASE SUMMARY

3.0 INSTALLATION PLAN

4.0 HARDWARE ARCHITECTURE (DEVELOPMENT, TEST AND PRODUCTION CONFIGURATIONS)
  1. SOFTWARE ARCHITECTURE (DEVELOPMENT, TEST AND

    2. PRODUCTION CONFIGURATIONS)

  2. VERSION DESCRIPTION DOCUMENT
  3. CODE TESTING PLAN
  4. TRACEABILITY MATRIX
  5. OPEN ISSUES LOG
  6. CODE AND DOCUMENTATION
  7. CODE INSTALLATION INSTRUCTIONS
  8. APPROVAL/CONCURRENCE

Appendices

BETA 2 DOCUMENTATION Instructions

Project Title

  1. PRELIMINARY REQUIREMENTS SUMMARY

    2. Beta 2 builds upon the foundation provided by Beta 1 by including some business rules, button functionality, data verification and record updates to the database. It is the first iteration of a working prototype. It represents the look and feel of the projected functionality with some business logic in a working version of the proposed system module.
  2. USE CASE SUMMARY

    3. This section should summarize the results of the JAD session(s) and "business use case" material(s) that have been developed to-date. Beta 2 is given once again to the JAD participants and is also seen by other appropriate business users.
  3. INSTALLATION PLAN

    4. This section should cover the general Beta 2 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 2 test.
  5. SOFTWARE ARCHITECTURE (DEVELOPMENT, TEST AND

    6. PRODUCTION CONFIGURATIONS)

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

    7. 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. CODE TESTING PLAN

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

  8. TRACEABILITY MATRIX

    9. This section should identify the specific system requirements being covered by the beta 2 version of the software and provide a crosswalk of requirements to functions developed and tested in the bets 2 version.
  9. OPEN ISSUES LOG

    10. All JAD issues are tracked and open issues are tracked in this section of the beta 2 documentation.
  10. CODE AND DOCUMENTATION

    11. This section summarizes all code and system documentation files/sources required for beta 2 in a quick reference table format for review and reference information.
  11. CODE INSTALLATION INSTRUCTIONS

    12. This section should cover specific code installation instructions for a

    beta 2 installation process.
  12. APPROVAL/CONCURRENCE

Include an appropriate SC concurrence/approval section.

Appendices

Use appendices to document any specific alternative vendor information.