including the planning of CM, configuration identification, configuration control, CM reporting, and baseline verification. Configuration Management will be applied across the life of the project to provide the appropriate level of control for all project configuration items. Each of these groups, listed below, consist of formally controlled configuration items (CIs). Changes to these formally controlled items are managed via change control: Statement of Work Requirements Documentation User Acceptance Testing Approach and Documentation AAMVA Casual and Structured Testing Approach and Documentation User Training Approach and Documentation The project will use Microsoft Visual Source Safe (VSS) for source code configuration management. All configuration are controlled within the repository using labels to manage the baselines. The versioning of Configuration Items (CIs) is handled using the native versioning within VSS and the integrity of the data is maintained through the implementation of access controls to prevent unauthorized changes. File locking is used to prevent multiple from updating the same file in parallel. Procedures have been implemented to ensure that only exclusively locked files are read-write in a user’s working area, unlocked files are stored as read-only. The native operating system standards prevent users from creating and/or adding files with duplicate file names to the same location. 6.8.1 For each deliverable, the document’s title, completion date, and version will be included on the cover page. Documents will also maintain a Revision History to record major changes and updates to each deliverable. The following versioning for document deliverables will be followed: Versioning Major Version Definition 1.X Initial Draft 2.X Review Ready Draft 3.0 Accepted Deliverable revisions also will be reflected with changes to the numbers to the right of the decimal.
including the planning of CM, configuration identification, configuration control, CM reporting, and baseline verification. Configuration Management will be applied across the life of the project to provide the appropriate level of control for all project configuration items. Each of these groups, listed below, consist of formally controlled configuration items (CIs). Changes to these formally controlled items are managed via change control: Statement of Work Requirements Documentation User Acceptance Testing Approach and Documentation AAMVA Casual and Structured Testing Approach and Documentation User Training Approach and Documentation The project will use Microsoft Visual Source Safe (VSS) for source code configuration management. All configuration are controlled within the repository using labels to manage the baselines. The versioning of Configuration Items (CIs) is handled using the native versioning within VSS and the integrity of the data is maintained through the implementation of access controls to prevent unauthorized changes. File locking is used to prevent multiple from updating the same file in parallel. Procedures have been implemented to ensure that only exclusively locked files are read-write in a user’s working area, unlocked files are stored as read-only. The native operating system standards prevent users from creating and/or adding files with duplicate file names to the same location. 6.8.1 For each deliverable, the document’s title, completion date, and version will be included on the cover page. Documents will also maintain a Revision History to record major changes and updates to each deliverable. The following versioning for document deliverables will be followed: Versioning Major Version Definition 1.X Initial Draft 2.X Review Ready Draft 3.0 Accepted Deliverable revisions also will be reflected with changes to the numbers to the right of the decimal.
MVD%20C-Mod%20PMP%20v2.0%202011-08-24.docx