Configuration Management Plan Checklist
GUIDELINES FOR THE CONFIGURATION MANAGEMENT PLAN CHECKLIST:
This checklist is provided as part of the evaluation process for the Configuration Management Plan. The checklist assists designated reviewers in determining whether specifications meet criteria established in HUD’s System Development Methodology (SDM). The objective of the evaluation is to determine whether the document complies with HUD development methodology requirements.
Attached to this document is the DOCUMENT REVIEW CHECKLIST. Its purpose is to assure that documents achieve the highest standards relative to format, consistency, completeness, quality, and presentation.
Submissions must include the following three documents, and must be presented in the following order: (First) Document Review Checklist, (Second) the Configuration Management Plan Checklist, and (Third) the Configuration Management Plan.
Document authors are required to complete the two columns indicated as “AUTHOR X-REFERENCE Page #/Section #” and “AUTHOR COMMENTS” before the submission. Do NOT complete the last two columns marked as “COMPLY” and “REVIEWER COMMENTS” since these are for the designated reviewers.
Document reviewers will consult the HUD SDM and the SDM templates when reviewing the documents and completing the reviewer’s portions of this checklist.
|AUTHOR REFERENCE (Project Identifier): |
|Designated Reviewers: |Start Date: |Completed Date: |Area Reviewed: |Comments: |
|1: | | | | |
|2: | | | | |
|3: | | | | |
|4: | | | | |
|Summary Reviewer: | | | | |
|Configuration Management (CM) is the ongoing process of identifying and managing changes to deliverables and other work products. |
TABLE OF CONTENTS
| | |
|1.0 General Information |3.0 Change Control Process |
|1.1 Purpose |3.1 Change Classifications |
|1.2 Scope |3.2 Change Control Forms |
|1.3 System Overview |3.3 Problem Resolution Tracking |
|1.4 Project References |3.4 Measurements |
|1.5 Acronyms and Abbreviations |3.5 Configuration Status Accounting (CSA) |
|1.6 Points of Contact |3.6 Configuration Management Libraries |
|1.6.1 Information |3.7 Release Management |
|1.6.2 Coordination |3.8 Configuration Audits |
|2.0 Configuration Control |3.8.1 Functional Configuration Audit |
|2.1 Change Control Board (CCB) |3.8.2 Physical Configuration Audit |
|2.2 Configuration Items |3.9 Tools |
|2.3 Baseline Identification |4.0 Training |
|2.3.1 Functional Baseline |4.1 Training Approach |
|2.3.2 Design Baseline | |
|2.3.3 Development Baseline | |
|2.3.4 Product Baseline | |
|Roles and Responsibilities | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| |To be completed by Author |To be completed by Reviewer |
|REQUIREMENT |AUTHOR X-REFERENCE Page |AUTHOR COMMENTS |COMPLY |REVIEWER COMMENTS |
| |#/Section # | | | |
| | | |Y |N | |
|1.0 GENERAL INFORMATION | | | | | |
|1.1 |Purpose: Describe the purpose of the Configuration Management Plan. |
| |1.6.1 Information: Provide a list of the points of | |
| |organizational contact that may be needed by the document user for | |
| |informational and troubleshooting purposes. | |
|REQUIREMENT |AUTHOR X-REFERENCE Page |AUTHOR COMMENTS |COMPLY |REVIEWER COMMENTS |
| |#/Section # | | | |
| | | |Y |N | |
|2.0 CONFIGURATION CONTROL | | | |
|2.1 |Change Control Board: Describe the project CCB, its roles and | |
| |responsibilities and the membership. | |
|REQUIREMENT |AUTHOR X-REFERENCE Page |AUTHOR COMMENTS |COMPLY |REVIEWER COMMENTS |
| |#/Section # | | | |
| | | |Y |N | |
|3.0 CHANGE CONTROL PROCESS | | | |
|3.1 |Change Classifications: Describe how change classifications will be | |
| |determined and assigned in terms of the level of severity of their | |
| |impact. | |
|REQUIREMENT |AUTHOR X-REFERENCE Page |AUTHOR COMMENTS |COMPLY |REVIEWER COMMENTS |
| |#/Section # | | | |
| | | |Y |N | |
|3.8 |Configurat| | |
| |ion | | |
| |Audits: | | |
| |Specify | | |
| |the type | | |
| |and number| | |
| |of audits | | |
| |to be | | |
| |conducted,| | |
| |which will| | |
| |be | | |
| |determined| | |
| |by the | | |
| |size and | | |
| |complexity| | |
| |of the | | |
| |project | | |
| |being | | |
| |undertaken| | |
| |. | | |
4.1Training Approach: Provide information regarding the content and scheduling of CM training to be conducted for all personnel supporting the project.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- version description document
- software configuration management plan template
- sample configuration management plan
- software and hardware configuration management
- software development tool validation template
- software requirements specification srs template
- configuration management plan checklist
- installation and deployment guide
- system design document template cms
- interface control document icd template
Related searches
- dod configuration management plan
- dod configuration management policy
- configuration management plan template
- navy configuration management plan
- dau configuration management plan
- configuration management best practices pdf
- software configuration management pdf
- configuration management sop
- eia 649c configuration management pdf
- configuration management plan document
- software configuration management example
- configuration management plan pdf