The document discusses software configuration management processes for development, testing, and release. It outlines the key roles and responsibilities including an executive sponsor, project director, process owner, and configuration manager. The process includes developing code in a configuration management system, promoting code through development, systems testing, user acceptance testing, and finally to production. Requirements, documentation, and test criteria are defined for moving between each stage.

1. System Configuration Management

2. Software Configuration Management (SCM) plays a key role Development Testing Release Maintenance

3. Team Members Executive Sponsor – provide resources Project Director – insures team members follow CM procedures Process Owner – usually the Software Configuration Manager or analyst Process Holders Director Project Manager Configuration Manager Release Manager SCCB

4. Process Holders Director – direction of project planning Project Manager – insures process is agreed upon; Management and Implementation (Process Owner) Configuration Manager – administrator Release Manager – coordinates releases SCCB – manage change control process

5. Process Overview Develop Product Promote source to system integration CM performs baseline of code Changes recorded in source control tool Code checked in Adjustments made to environment Changes recorded in source control tool Installation scripts/procedures recorded in source control tool

6. Development to Systems Test Development environment open to all users Systems Test environment – code is locked down Record bugs/errors and send back to development Repeat this process until requirements are consistently met

7. Documents need to promote to Systems Test Environment Approved Change Requests Installation Guide Functional Specification System Specifications Special Test Instructions Release Schedule Modules to be released

8. Systems Test Entrance Criteria Code is base lined and under SCM control Design and code walk through Unit tests Integration testing Performance analysis and tuning No unresolved problems Functional and User Specifications All DB creation/updates, conversion scripts User Documentation

9. System Test Return Code to Development Bugs and errors found Test plans Test results

10. System Test Exit Criteria All defects corrected All high priority issues resolved System test report Final user documentation

11. System Test to User Acceptance Testing Application setup for testing by Production Project Plan document Design specification document Logical and physical data diagrams System configuration document Unit test has been completed System test has been completed All high priority errors have been resolved User guide available Installation guide available Application files installed

12. User Acceptance Testing Exit Criteria Successfully completed Test summary reviewed and accepted No unresolved high priority issues All installation problems resolved Final user guide documentation Disaster recovery plan and manual

13. Production All promoted to production