User:Edmondsksung/sandbox

您好吗 ? Configuration Management
 * SG 1
 * SG 2
 * SG 3

Specific Goal 1
– Establish Baselines –Baselines of identified work products are established and maintained

SP 1.1 Identify Configuration Items– Identify the configuration items, components, and related work products that will be placed under configuration management

Exploratory Questions(s)

1.	Would you please describe the configuration items, components, and related work products you place under configuration management? Who is doing it? How is it being done? Rationale

Listen Fors: •	Products that are delivered to the customer •	Products that are designated as internal work products •	Acquired products •	Tools (compilers, operating systems, system configuration files) •	Items that are used in creating and describing these work products •	Sample life-cycle work products include: -	Requirements Specification -	Interface Descriptions -	Project Development Plan -	Project Quality Plan -	Configuration Management Plan -	Architecture Specification -	Design Specifications -	Code -	Test Plans -	Test Procedures -	Documentation -	Development Procedures -	Standards -	Script files

2.	Would you please describe how you uniquely identify each configuration item that is placed under configuration management?

Listen Fors: •	Configuration items are assigned unique identifiers according to organizational guidelines

SP 1.2 Establish a Configuration Management System – Establish and maintain a configuration management system and change management system for controlling work products

Exploratory Questions(s)

3.	Would you please describe the Configuration Management System (Storage Media, procedures and tools) that is used to support your project’s configuration management needs?

Listen Fors: •	Storage media •	Procedures •	Tools for accessing the Configuration Management System •	Tools for recording and accessing change requests

4.	Would you please describe the Configuration Management System services that are provided?

Listen Fors: •	Managing multiple control levels of configuration management -	Author’s workspace (Controlled by the author) -	Project or Developmental Control (lower level CCB control) -	Product Line Control (For distinct product lines within an organization) -	Systems or Organizational Control (Higher level CCB control with involvement with the customer) •	Storage and retrieval of configuration items •	Sharing and transferring of configuration items between the different control levels •	Storage and recovery of archived versions of configuration items •	Storage, update, and retrieval of configuration management records •	Creation and dissemination of configuration management status reports •	Supporting configuration audits to preserve the integrity of the system

5.	Would you please describe the how the contents of the Configuration Management System are protected and maintained?

Listen Fors: •	Backups and restoration of configuration management files •	Archiving of configuration management files •	Recovery from configuration management errors •	Supports disaster recovery

SP 1.3 Create or Release Baselines – Create or release baselines for internal use and for delivery to the customer

Exploratory Questions(s)

6.	Would you please describe what baselines are established for internal use and for release on your project?

Listen Fors: •	A baseline is a set of specifications or work products that have been formally reviewed and agreed upon •	Baselines serve as the basis for further development •	Baselines can only be changed through change control procedures •	Developmental Baselines are controlled by the Project (possibly with help from CM – Architecture, Design, Code, Test) •	Organizational Baselines are controlled at the organizational level (Requirements, Interfaces) •	Baselines of configuration items are created or released from the Configuration Management System only with authorization from the CCB

SG 2
– Track and Control Changes – Changes to the work products under configuration management are tracked and controlled

SP 2.1 Track Changes – Track change requests for the configuration items

Exploratory Questions(s)

7.	Would you please describe how change requests are processed for new or changed requirements, failures, and defects in the work products?

Change Requests address not only or changed requirements, but also failures and defects in the work products

Listen Fors: •	Change requests are analyzed to determine the impact that the change will have on the work product, related work products, schedule and cost 	This Implies Bi-Directional Traceability (See Glossary) •	Changes are evaluated to ensure that they are consistent with the technical and project requirements •	Changes are evaluated for their impact in other project, product lines, or applications •	Change requests are reviewed and agreed upon by all relevant stakeholders •	Change requests are tracked to closure •	Change requests are approved by the proper level of CCB (Organizational, Project)

SP 2.2 Control Configuration Items – Control changes to the content of configuration items

Exploratory Question(s)

8.	Would you please describe how changes to the content of the configuration items are controlled?

Listen Fors: •	Change control involves tracking each configuration item, approving a configuration, and updating the baseline •	Check-in, Check-out procedures are used to maintain the correctness and integrity of the configuration management system •	Reviews and regression testing are performed to ensure that changes have not caused unintended side effects on the baselines •	Authorization from the proper level of Configuration Control Board is obtained before changed configuration items are entered into the configuration management system •	All changes and the reasons for the changes are recorded in sufficient detail to provide change history and support configuration management status accounting

SG 3
– Establish Integrity – Integrity of baselines is established and maintained

SP 3.1 Establish Configuration Management Records – Establish and maintain records describing configuration items

Exploratory Question(s)

9.	Would you please describe what information is recorded when changes are made to configuration items.

Listen Fors: •	Configuration management actions are recorded in sufficient detail so the content and status of each configuration items is known •	The difference between successive baselines is able to be clearly described •	All relevant stakeholders have access to and knowledge of the configuration management system AND CAN USE IT OR COUNT ON SUPPORT •	Reports are detailed enough to support each project’s project management needs

SP 3.2 Perform Configuration Audits – Perform configuration audits to maintain the integrity of the configuration baselines

Exploratory Question(s)

10.	Would you please describe the configuration audits that you conduct during the product lifecycle and before the product is produced?

Listen Fors: •	Completeness and correctness of the changed configuration items in the Configuration Management System from approved change requests is verified through reviews, testing, and content comparisons •	Baseline audits are conducted throughout the lifecycle at least after phase end •	Functional Configuration Audits are conducted to ensure that the system that is to be delivered matches the requirements and approved requirements change requests and nothing more AND the documentation that will be used for maintenance activities and operational use matches the baselined system that will be released

•	Physical Configuration Audits are conducted to verify that the as-built system conforms to the technical specification that defines it (Number and description of components, both hardware and software match what is packaged and delivered)

Generic Goal 2 – Institutionalize a Managed Process – The process is institutionalized as a managed process

Generic Practice 2.1 – Establish an Organizational Policy – Establish and maintain an organizational policy for planning and performing the configuration management process

Exploratory Question(s)

11.	Would you please describe your organization's policy on configuration management?

Listen Fors: •	Baselines of identified work products are established and maintained •	Changes are controlled and tracked •	Integrity of baselines is maintained •	The status and change activity of the work products under configuration management is communicated •	The resulting baselines and configuration items are audited to ensure completeness, correctness, and the integrity of the library

Generic Practice 2.2 – Plan the Process – Establish and maintain the requirements and objectives, and plans for performing the configuration management process

Exploratory Question(s)

12.	Would you please describe what you have to consider to implement the configuration management processes for use on your project to satisfy your project’s goals and constraints?

Generic Practice 2.3 – Provide Resources – Provide adequate resources for performing the configuration management process, developing the work products, and providing the services of the process.

Exploratory Question(s)

13.	Would you please describe the resources that you require to effectively carry out the configuration management processes selected for your project?

Listen Fors: •	Examples of tools used in performing the activities of CM include: -	Configuration Management Tools (Clearcase, Synergy (Continuous), Serena (PVCS), Visual Source Safe, In-House)) -	Data management tools -	Archiving and reproduction tools -	Database programs

Generic Practice 2.4 – Assign Responsibility – Assign responsibility and authority for performing the process, developing the work products, and providing the services of the configuration management process

Exploratory Question (s)

14.	Would you please describe who is responsible for ensuring that the defined configuration management functions are effectively executed for your project throughout the project lifecycle?

Listen Fors: •	Project Configuration Management Coordinator that looks after the CM function needs of the project •	Managers and supports of the Configuration Management System •	Responsibles for configuration audits •	CCB at the organization or product line level including: ­	Program Management ­	Software engineering representative ­	Hardware engineering representative ­	System engineering representative ­	Quality Assurance ­	Configuration Management ­	Documentation ­	System Test ­	CCB authorizes the establishment of product baselines, reviews and authorizes changes to them, and authorizes the creation of baseline products

Generic Practice 2.5 – Train People – Train the people performing or supporting the configuration management process as needed

15.	Would you please describe the types of configuration management training that is provided and what groups or individuals receive this training?

Listen Fors: •	Roles, responsibilities, and authority of the configuration management staff •	Configuration management standards, procedures, and methods •	Configuration Management System •	Configuration Management Tool •	Configuration Auditing

Generic Practice 2.6 – Manage Configurations – Place designated work products of the configuration management process under appropriate levels of control.

16.	Would you please describe what configuration management work products are placed under control? What level or levels of configuration management are used?

Listen Fors: •	Requirements Change Requests and their status •	Change history of individual configuration items •	Configuration Audit reports •	Status Accounting Reports •	Configuration Control Board meeting minutes •	Descriptions of archived baselines

Generic Practice 2.7 – Identify and Involve Relevant Stakeholders – Identify and involve the relevant stakeholders of the configuration management process as planned

17.	Would you please describe the stakeholder involvement activities for configuration management?

Listen Fors: •	When baselines are established •	When CMS reports are reviewed and issues need to be resolved •	When the impact of change requests is assessed •	When configuration audits are performed

Generic Practice 2.8 – Monitor and Control the Process – Monitor and control the configuration management process against the plan and take appropriate corrective actions

18.	Would you please describe how the configuration management process is monitored and controlled?

Listen Fors: •	Measurements to determine how well the configuration management process is working include: -	Number of Problem Fixes that "Came Back" and had to be fixed again -	Number of violations of the CM procedures (getting around the process to make changes to code or life-cycle work products) -	Number of outstanding trouble reports, compared with the rate at which they are being fixed -	Number of times a version of a module or other life-cycle work product is lost -	Number of times a developer’s changes are negatively affected by some other developer’s changes -	Number of times variants are inaccurately merged back into the mainstream baselined system

Generic Practice 2.9 – Objectively Evaluate Adherence– Objectively evaluate adherence of the configuration management process against its process description, standards, and procedures, and address noncompliance.

19.	Would you please describe how the configuration management process used on the project is objectively evaluated?

Listen Fors: •	Establishing and maintaining the baselines •	Tracking and controlling changes •	Establishing and maintaining the integrity of the baselines

Generic Practice 2.10 – Review States with Higher-Level Management – Review the activities, status and results of the configuration management process with higher-level management and resolve issues

20.	Would you please describe how often the configuration management processes and results are reviewed with higher-level management and what is discussed?

Listen Fors: •	Frequency of CM reports delivered to Higher-Level Management •	Number of change requests of a specific category (critical, intermediate, nice to have) •	Number of change requests against a certain product (critical, intermediate, nice to have) •	Results of configuration audits

Generic Goal 3 – Institutionalize a Defined Process – The process is institutionalized as a defined process

Generic Practice 3.1 – Establish a Defined Process – Establish and maintain the description of a defined configuration management process

21.	Would you please describe how each project establishes its project’s configuration management defined process that is a tailored from the organization’s set of standard processes?

Listen Fors: •	Tailoring guidelines show how to scale processes up as well as down to make them effective for a specific project’s needs. •	Tailoring guidelines are documented, trained, objectively evaluated, and applied is an auditable manner.

Generic Practice 3.2 – Collect Improvement Information – Collect work products, measures, measurement results, and improvement information derived from planning and performing the configuration management process to support the future use and improvement of the organization’s processes and process assets.

22.	Would you please describe the process that is followed on each project to collect information and artifacts derived from planning and performing the process?

Listen Fors:

•	Trends in the status of configuration items •	Configuration audit results •	Change request aging reports