Formal

1) Submit a Formal Change Request Form to Configuration Management

2) CM will post the proposal on the web and will inform parties that will be affected by the change to read the proposal

3) CM will schedule a Change Control Board meeting with Project Management and representatives of parties to be affected by the change. The meeting's purpose will be to assess the change proposal's impact on the project. The proposal will either be accepted, rejected, or deferred.

4) Results from the Change Control Board meeting will be posted on the web and the team will be notified.

5) If a change has been approved, the work product administrator will update the document and carry out steps outlined in the 'Updating a document' section of the Work Product Change Control Summary

Ask Administrator

1) Ask the administrator to update the document with a certain change. The administrator acts as the change control board for the document he's administering and decides whether or not to implement the change.

2) The administrator will inform you of his decision about your change.

3) If you're current work load is less than that of the document administrator, it's allowed (and recommended) that you become in charge of the document temporarily so that you can implement your suggested change.

4) If step 3 was followed (i.e., you took became in charge of the document temporarily to implement your suggested change) it is your responsibility to carry out the steps outlined in the 'Updating a document section of the Work Product Change Control Summary

5) If a change has been approved, the work product administrator will update the document and carry out steps outlined in the 'Updating a document' section of the Work Product Change Control Summary

Changes to source code

Changes to source code will be done using CVS. A brief tutorial on how to use CVS is posted here. Changes to the source code that affect the design and architecture of ETA (like changing a method's parameter list, adding a new class, removing a public method, etc) are considered changes to the Software Architecture and must go through the process of changing the Software Architecture.

Change Control Board

The Change Control Board consists of all members of Lucky Strike Software. The board will meet on Thursdays from 1:30-3:00pm as needed to consider Formal Change Requests.

Document Version Stamps

Example of Last Modified Tag (LMT)

Last Updated: Jan 12, 2001 by John Doe

Example of Document History Table (DH)

Date	Author	Change
1/10	jsmith	updated table of contents
1/9	jsmith	initial posting