Work Product Change Control Summary 
 

Work products listed below are under change control. If you feel that one of these products need to be changed, follow the change control procedure for that document.
 

Work Product Administered By Change Procedure Version Stamp Archived by CM?
Change Control Plan Apel Formal DH no
Change Proposals Apel Ask Administrator DH no
Vision Statement Mike H Formal none yes
Top 10 Risks List John Ask Administrator LMT yes
User Interface Prototype Phil Formal DH yes
User Manual / Requirements Specification Phil Formal DH yes
Software Architecture John Formal DH yes
Software Integration Plan John Ask Administrator DH no
Staged Delivery Plan Wes Formal DH no
Coding Standard Apel Formal DH no
Software Test Cases John Ask Administrator DH yes
Software Build Insturctions Wes Ask Administrator LMT yes
Install Program Wes Ask Administrator LMT yes
Release Checklist Mike H. Formal DH no
Release Sign-Off Form Mike H. Formal DH no
Software Project Log Mike H. Ask Administrator LMT no
QA Plan Mike P. Formal DH no
Project Plan Mike H. Ask Administrator DH no
Software Project History Document Mike H. Ask Administrator LMT no

 

Updating a document

After a work product has been changed, administrators must submit their updated documents to Configuration Management so that the document can be archived if necessary. Administrators must also submit a brief description of what was changed so that the What's New section of the web page can be updated.

Administrators are also responsible for maintaining the version stamps for their documents, using the format listed for their document in the table above (see the Procedures page for a description of Last Modified Tags (LMT) and Document History tables (DH)).

Once a work product has been changed and the web page updated, Configuration Management will notify the team of the change.

Small Changes

Minor changes like correction of grammar/spelling errors, cosmetic changes to a document, minor defect corrections in the software, etc, are considered "automatically approved" and board meetings or notifications will not be executed.


Date Author Change
2/24 ayahinia Updated the list to reflect changes made after Release 2.
1/17 mhebron document baselined, project plan and history document added to plan
1/16 mhebron rough draft posted