Configuration management
One support process of maturity level 2
purpose
The purpose of configuration management (cm) is to establish and maintain work products use configuration recognition, configuration control, configuration status clearing, configure auditing integrity.
Introduction
The configuration management process area includes:
l Identify the configuration of the selected work product to form a baseline in a particular point.
l Collect changes in configuration items
l Establish or provide specifications from the configuration management system to create work products
l Keep the integrity of baseline
l Provide the developers, end users, and customers with the correct status and current configuration data
Work products stored in configuration management include released to customers, internal work products, have obtained products, tools, and other items used to create and describe these work products. (See "Configuration Management" in the definition of the glossary)
For supplier source vendors and projects, you may need to be placed under configuration management. The establishment of the operation of configuration management should obtain the supplier's consent. The method of ensuring the integrity and consistency of data should be established and maintained.
Examples of work products that may be placed under configuration management are as follows: l Procedure Description L Demand L Design Data L Chart L Product Specifications, Manual L Code L Compiler L Product Data Files L Product Technical Publications
The configuration management of the work product may be executed in multiple levels. The configuration item can be decomposed into a configuration component and a configuration unit. Only "Configuration Item" is used in this process area. However, "Configuration Item" in these practices may be interpreted as "configurable components" or may be interpreted as "configurable units". (See "Configuration Item" defined in the glossary)
The baseline provides a stable basis for further development of the configuration item.
An example of a baseline is an approved product description including internal versions of the needs, demand tracking matrices, design, special disciplines, and end user documents.
When the baseline is set to the configuration management system. The publication of the baseline changes and work products from the configuration management system are systematic control and supervision through configuration control, change management, and configuration audit feature.
This process area is not only used in the project configuration management, but also applies to the configuration management of work products, for example, standard, procedures, and reusable libraries.
Configuration management focus is the technical aspects of management of strict control and work products, including systems that have been delivered.
This process area contains practices for performing configuration management functions and can be applied to all work products under configuration management.
Practice - Target Relation
Continuous
Graded
SG1 establishes baseline SG1 to establish baseline SP1.1-1 identification configuration item
SP1.1-1 identification configuration item
SP1.2-1 Establish configuration management system
SP1.2-1 Establish configuration management system
SP1.3-1 generation or distribution baseline
SP1.3-1 generation or distribution baseline
SG2 tracking and controlling changes
SG2 tracking and controlling changes
SP2.1-1 Tracking Change Requirements
SP2.1-1 Tracking Change Requirements
SP2.2-1 Control Configuration Item SP2.2-1 Control Configuration Item SG3 Establish Integrity SG3 Establish Integrity SP3.1-1 Establishing Configuration Management Record SP3.1-1 Establishing Configuration Management Record SP3.2-1 Execution Configuration Review SP3.2-1 Execute Configuration Audit GG1 to achieve a specific goal
GP1.1 completed basic practice
GG2 institutionalization a managed process GG2 institutionalization a managed process
GP2.1 establishes an organization's policy
GP2.1 establishes an organization's policy
GP2.2 planning process
GP2.2 planning process
GP2.3 provides resources GP2.3 Provide resources GP2.4 Assigning Responsibilities GP2.4 Assigning Responsibilities GP2.5 Trainers GP2.5 Trainers GP2.6 Management Configuration GP2.6 Management Configuration GP2.7 Identification and include related risk assumers GP2.7 identification and related risk bearers GP2.8 supervision and control This process GP2.8 supervision and control This process GP2.9 objective evaluation persists GP2.9 Objective evaluation persists GP2.10 with higher Level Management Review Status GP2.10 Institutionalization The defined process GP3.1 establishes a defined process GP3.1 to establish a defined process C / ML3-5 GP3.2 collection with a higher level management review status GG3. Improve information GP3.2 Collection Improvement Information
GG4 institutionalization of a quantitative management process
GP4.1 quantitative goal
The implementation of the GP4.2 stabilization sub-process
GG5 institutionalization of an optimization process
GP5.1 guarantees continuous process improvement
GP5.2 correcting the root of the problem
Related process domain
For more information on the development of planning and work decomposition structures, please refer to the project planning process.
For more information on methods for analyzing the impact of changes in change, see Cause Analysis and Decision Process Area.
For more information on performing analysis and corrective activities, see Project Supervision and Control Process Area.
Key practice of achieving goals
SG1 establishes baseline
The baseline of the designated work product has been established.
The key practice of establishing baseline includes this key goal. Key Practice Used to keep baselines under tracking and controlling changes in this key target. The special goal of the key practice of establishing integrity is to record and audit the integrity of the baseline.
SP1.1-1 identification configuration item
Identify configuration items, components, and related work products you need in configuration management.
Configuration recognition is to choose, create and detail below:
l Released products to customers
l Designed internal work products
l Products obtained
l tool
l Other projects used to create and describe these work products
The project under configuration management will include details and interactive documents that define product requirements. Other documents such as test results will also be included, whether or not they contain critical levels to define the product.
A "configuration item" is a configuration management entity that may consist of multiple related work products from a baseline. This logical group provides convenient for identification and control.
The choice of work products for configuring management should be based on standards established during the plan.
For system engineering
In a system containing hardware and software, the software only accounts for a small part of the system, and all software may be designed as a separate configuration item. On the other hand, the software may also be combined into a variety of configuration items.
The configuration item can be combined into the configuration component and configuration unit. There is only the term "configuration item" in this process. In these practices, the Configuration Items may be understood as "configuration components", or it may be understood as "configuration unit". For example, the configuration item of the demand management domain can vary from each individual to a set of requirements.
Typical work product
1. Identified configuration item
Child practice
1. Select configuration items and work products, combine them based on documentation standards.
The standard example for selecting the appropriate work product level selection configuration item is as follows: l Work product L used by two or more groups of work product L is desired for the work product L for the desired change because of the error or demand change Mutual dependent work products that cause changes in other product changes are critical work products for projects.
An example of a work product that may be part of the configuration item is as follows: l Process Description L Demand L Design L Test Plan and Program L Test Results L Interface Description
For software engineering
Software work products may become a part of the configuration items as follows: l Code / model L tool (such as compiler)
2. Assign unique identifiers to the configuration item.
3. Inventory of important features of each configuration item.
The features of the configuration items include the author, document, or file type, and programming of software encoding.
4. List of lists when each configuration item is incorporated.
Judging when to incorporate work products into configuration management, as follows:
l stage of the project life cycle
l When working product preparation test
l Control grade for work products
l L limited cost and time
l customer needs
5. Identify the responsibility of each configuration item owner.
SP1.2-1 Establish configuration management system
Establish and maintain the configuration management and configuration change management system for controlling work products.
A configuration management system includes a tool for storage media, programs, and access to configured systems.
A configuration change management system includes tools that store media, programs, and records and access to change.
Typical work product
1. Configuration management system that contains the controlled work product
2. Configure the management system access control program
3. Change Requirements Database
Child practice
1. Establish a variety of control levels for mechanism management configuration management.
Examples of various levels of controlling control have occurred as follows:
l Need different levels of control at different times of the project life cycle (for example, more stringent control when product maturity)
l Different types of systems require different control levels (for example, pure software systems and systems including hardware and software)
l Configuration items require different levels of control over confidentiality and security
2. Storage and refresh configuration items in the configuration management system
The configuration management system is as follows:
l Dynamic (or Developing) systems include components that are often created and modified. They are all controlled by developers and are controlled by developers. The configuration items in the dynamic system are in version control.
l Control (or controlled) systems include current baselines and modifications to baselines. The configuration items in the control system accept full configuration management, just as the domain description of this process.
l The static system includes a variety of published baselines, and the static system accepts full configuration management, just as described in this process.
3. Share and transfer configuration items between different control levels in the configuration management system.
4. Store and recover the version already archived.
5. Storage, update, and refresh configuration management records.
6. Generate a configuration management report from the configuration management system.
7. Save the contents of the configuration management system.
The save function of the configuration management system is as follows:
l Backup and recovery configuration management files
l Archive configuration management file
l Recover from configuration management errors
8. Modify the configuration management structure when necessary.
SP1.3-1 generation or distribution baseline
Generate or distribute baselines for internal use and distribute to customers.
The baseline is a set of specifications or work products that are officially reviewed and approved, and baseline is served as a basis for further development in the future. And baseline can only be changed by the control process. The baseline assigns an identifier for each configuration item and its related entity.
For system engineering
The distribution of baseline includes approved configuration data from the consent configuration item from the configuration management system and the market for future development. In the development cycle of the product, there may be a variety of baseline definition of a development product. It usually includes system-level requirements, system unit-level design requirements, and product definitions in the previous period / later product definition, which are called "function baseline", "local baseline" and "product baseline".
For software engineering
A required requirement, design, source program file, and related executable code, compilation file, and user documentation (related entities) can be considered a baseline. Baseline distribution is taken out from the configuration management system and generates an executable. The baseline delivered to the customer is a typical baseline called "release". The baseline used inside is "constructed".
Typical work product
Baseline
2. Description of baseline
Child practice
1. Get the authorization of CCB before creating and publishing the baseline of the configuration item. 2. Create and issue baseline only in the configuration items of the configuration management system.
For system engineering
Make sure the configuration item is established to be correct.
3. Proof the configuration item included in the baseline.
4. Make the current baseline available.
SG2 tracking and controlling changes
Changes to work products in configuration management have been tracked and controlled.
The key practice under this special goal is serviced to keep the baseline under the special goal of the baseline is established.
SP2.1-1 tracking change requirements
Track the requirements for configuring project changes.
Change requirements are not only in new or changing needs, but also in the fault and defects of work products.
Analyze changes requirements to determine the impact of changes in work products, related work products, and planning and costs.
Typical work product
1. Change requirements
Child practice
1. Start and record the change requirements in the change demand database.
2. Analytical changes and changes mentioned in the changes in the changes.
Changes by activity assessment to ensure that these changes are consistent in all techniques and project requirements.
Evaluation changes the impact on direct products and contractual needs, in a variety of products, changes to one of the projects may result in issues in other applications.
3. Review with those that will be changed, will be in the next baseline change requirements and agree.
Guide the appropriate participants to review the change requirements. Record the deployment of each variation and the basic principles of the resolution, including success standards, and there is an active plan outline if appropriate, and changes that meet or not satisfy. Activity must be performed under this deployment and report the result to the relevant risk bearer.
4. Track the status of changed requirements until it is closed.
Changes to the system need to be controlled in a timely manner in a valid. Once a change requires, it is urgent to shut down the requirements with appropriate and approved activities. The event has left more results than the required status list, which in turn leads to an increase in cost and confusion.
SP2.2-1 Control Configuration Item
Control the changes to the configuration item.
Control is continuous in the configuration of the working product baseline. This control includes tracking the configuration of each configuration item, requiring a new configuration as needed, and updating the baseline.
Typical work product
1. Revision history of the configuration item
2. Baseline archive
Child practice
1. Control the change of the configuration item in the life cycle of the product.
2. Get appropriate authorization before the configuration item is included in the configuration management system.
For example, authorization may come from CCB, project management or customers.
3. When combined with changes, check and check the configuration items from the configuration management system with a habit of maintaining the correctness and integrity of the configuration item.
Procedures for check in and detects, for example,: l Confirm the revision authorized L Update Configuration Item L Archive Baseline and Refresh New Baseline
4. Execute reviews to ensure that the changes have not caused an unexpected influence of the baseline (for example, ensure that the change does not have a crisis to the system security and / or confidentiality).
5. Record the change of the configuration item and the reason why the appropriate changes are changed.
If a proposed change is adopted for a work product, a schedule is determined to make the change in combination into work products and other affected areas.
The configuration control mechanism can be cut according to the category of the change, such as component changes that do not affect other components, can not require very strictly approved.
The changed configuration item is released after the approval of the configuration change and the review, and it will become official.
SG3 establishes integrity
The integrity of the baseline has been established.
The integrity of the baseline is established by the process of establishing a baseline special objective, and is maintained by the process of tracking and controlling a special target, provided by key practices under this special goal.
SP3.1-1 Establishing Configuration Management Record
Establish and maintain a record of configuration items.
Typical work product
1. Revision history of the configuration item
2. Change log
3. Backup required by change
4. Configure the item structure
5. Different part of the baseline
1. Sufficient detailed record configuration management activity, you can know the contents and status of each configuration item and can restore the previous version.
2. Ensure that the relevant risk bearers can access and understand the configuration status of the configuration item.
Configuration status communication activity is as follows: l Provides access to authorized end users to actively provide baseline backup to authorized end users
3. Collect the latest version of the baseline in the list.
4. Identify the version of the configuration item, thereby form a specified baseline.
5. Describe the difference between the continuous baseline.
6. Revise the status and history of each configuration item if necessary (that is, change and other activities).
SP3.2-1 performing configuration review
Perform a configuration review to keep the integrity of the baseline.
Review configuration management activities and try to confirm that the results of the baseline and the file are correct, and the appropriate record results are recorded.
Typical work product
1. Configure the audit results
2. Event item
Child practice
1. Evaluate the integrity of baseline.
2. Verify that the configuration record correctly identifies the configuration of the configuration item.
3. Review the structure and integrity of the configuration items in the configuration management system.
4. Confirm the completeness and correctness of the configuration items in the configuration management system.
The integrity and correctness of the content is based on the needs specified in the plan and the deployment of the recognized changes.
5. Confirm the availability of configuration management standards and programs.
6. Track activity items from review to off.
General practice of goals
GG1 Completes a specific goal
By transitioning identifiable input work products into identifiable output work products, process support and can make specific targets for process domains.
GP1.1 performing basic practice
Performing the Basic Practice of Cause Analysis and Decision Process Develop Work Products and provides services to special goals to meet process areas.
Just suitable for continuous
GG2 institutionalization a managed process
The process is subjected to a managed process.
Guarantee
GP2.1 establishes an organization's policy
Establish and maintain an organizational policy for planning and implementing configuration management processes.
Detailed detail
This policy establishes a hierarchical expectation for establishing and maintaining baseline, tracking, and controlling work products (under configuration management) and establishing and maintaining baseline integrity.
Ability to perform
GP2.2 planning process
Establish and maintain a plan for performing configuration management processes.
Detailed detail
It is representative and executing the configuration management process is part of the project plan described in the project plan process.
GP2.3 provides resources
Provide sufficient resources for performing configuration management processes, developing work products, and services for providing processes.
Detailed detail
The resources provided include the following tools: l Configuration Management Tools L Data Management Tools L Archive and Reproduction Tools L Database
GP2.4 allocation responsibilities
Assign the execution process, develop work products, and provide the responsibility of the configuration management process service.
GP2.5 Trainer
People who must be trained and support the configuration management process must be trained.
Detailed detail
Training topics are as follows: l Configure management criteria, responsibilities, and rights L Configuration Management Standard, Process and Method L Configure Library System
Guide (process)
GP2.6 management configuration
Place the work product specified during the configuration management process under the appropriate configuration management level.
Detailed detail
An example of a work product stored under configuration management:
l Access List L Status Report L Change Requirements Database L CCB Conference Record L Archive Baseline
GP2.7 identifies and contains related risk bearers
Control plan, identify and include related risks of configuration management processes.
Detailed detail
An activity of the risk bearer is now as follows:
l Establishing a baseline L Reviewing the configuration management system report and decomposes the problem L Evaluation Change The impact on the configuration item L executes the results of the Audit L Reviewing the results of the configuration management audit GP2.8 supervision and control process
The process and appropriate corrective activities are performed based on the program supervision and control configuration management process.
Detailed detail
An example of a metric method for monitoring and control is,
l Configure the number of changes to the number L Configure the number of audit behaviors
Verification (process)
GP2.9 objective evaluation persistence
The description, rules, procedures, and objective assessment of the control process, and deal with relevant matters that are not implemented.
Detailed detail
Reviewing the event is as follows:
l Establish a baseline L tracking and control change L, establish and maintain the integrity of baseline
Examples of work products are as follows:
l Baseline archive L change claims database
GP2.10 with higher level management review status
Use a higher level to review the activities, status, and results in the configuration management process, and solve the problem.
Editor Press: GG3 and its practices are not applied to the maturity level 2 stage, but applied to the 3 and more stages.
Just suitable for hierarchical
GG3 institutionalization a defined process
The process is institutional as a defined process.
Ability to perform
GP3.1 establishes a defined process
Establish and maintain a description of a defined configuration management process.
Guide (process)
GP3.2 Collection Improvement Information
Collect work products, metrics, metrics, and improve information from planning and implementation management processes, enhance future use and improvements in the organization process and process.
Continuous / maturity 3-5
GG4 institutionalization an integrated management process
The process is institutionalized as an integrated process.
GP4.1 establishes integration targets for the process
To configure and maintain integration targets to clarify quality and process execution based on customer needs and business goals.
GP4.2 stabilization sub-process execution
Stabilize the execution of one or more sub-processes to determine the ability to configure the management process to achieve the established quality and process implementation goals.
GG5 institutionalization a optimized process
The process is institutionalized as an optimized process.
GP5.1 ensures continuous process improvement
Ensure the continuous configuration management process improvement during the relevant business goals of the organization.
GP4.2 Correcting Root Reason
Identify and correct the root causes of defects and other problems during configuration management.
Just suitable for continuous
