SUP.8 Configuration Management
- Purpose
The purpose of the Configuration Management Process is to establish and maintain the integrity of all work products of a process or project and make them available to affected parties.
Ref
- Ref.1 ASPICE V3.1
1. Record
1.1 Process Outcomes
As a result of successful implementation of this process
- A configuration management strategy is developed
- All configuration items generated by a process or project are identified, defined and established according to the configuratoin management strategy.
- Modification and releases of the configuration items are controlled
- Modification and releases are made available to affected parties
- The status of the configuration items and modifications is recorded and reported
- The Completeness and consistency of the baselines is ensured
- Storage of the configuration items is controlled.
1.2 Base Practices
- BP1 Develop CM strategy
- BP2 Identify the Configuration items
- BP3 Establish a configuration management system
- BP4 Establish branch management
- BP5 Control modifications and releases
- BP6. Establishe baselines
- BP7. Report configuration status.
- BP8. Verfiy the information about configured items
- BP9. Manage the storage of configuration items and baselines.
1.3 Output work products
- 06-02 Handling and storage guide
- 08-04 Configuration managment plan
- 08-14 Recovery plan
- 13-08 Baseline
- 13-10 Configuraiton management record
- 14-01 Change history
- 16-03 Configuraiton management system
2. Reflect
2.1 Q&A
-
Q1. 配置管理是什么?
配置管理过程, 在ASPICE 中属于支持(SUP)域,用于管理所有与项目开发的文档,文件等内容,以支持整个项目的开发过程。
部署此过程中,项目中人员可以方便的了解整个项目开发周期,各个阶段各个文档的状态,及相应内容。 -
Q2. Why to Configuration Managment?
你在项目开发过程中,有遇到以下问题吗?- 和客户澄清好的需求,怎么保存?需求又又变更了,锁定后,怎么再次保存?变了这么多次版本的需求,如何保存?
- 怎么看上一次交样时的软件?
- 怎么看上述交样的测试报告,其覆盖的需要是什么,需求覆盖度是多少,是否符合质量目标?
- 怎么看上次交样时的测试工具的工程?
为什么要进行配置管理?
就是要让某个过程或者项目的工作输出,使所有相关团队都方便查阅,可用。可以一下子跳到这个项目的文档池子里面,了解这个项目的所有信息,而不是东找人发文档,西找人更新版本,浪费宝贵的沟通时间。
- Q3. 配置管理,管理什么呢 ?
Establish and maintain the integrity of all work products of a process or project.
即某个过程或者项目所有输入/输出文档(代码)的完整性。
完整性作何理解?
即管理的对象不止某个具体工作输出文档或代码;而是该工作输出的整个生命周期,从草稿版本,发布版本到下一次更新,发布版本,整个项目周期的版本都要受控。
-
Q4. Who are related to this process ?
- Role
- CM Engineer
- Role
-
Q5. What’s the configuration management strategy ?
- 人/职责
- 工具/仓库/访问权限
- 配置管理项及相应准则
- 命名约定
- branch及Merge策略
- baseline准则
-
Q6. What’s the integrity of all work products ?
- Work products
- status
- baselines
- revision history
- modification
- releases
-
Q7. What’s criteria for configuration items ?
A: Naming coventions of file, folder strucuture, tools, third-party software.
2.2 Review
Goal
* Establish and maintain the intergrity of all work products
* To make them available to affected parties.
配置管理过程的主旨:
- 建立和维护过程,或者项目相关输入及工作输出的完整性,并且使所有相关团队都可见。
配置管理过程思路:
- 开发配置管理策略
- 按照既定策略,识别被管理项
- 按照既定策略,建立配置管理系统
- 按照既定策略,创建分支
- 按照既定策略,控制变更及发布
- 按照既定策略,建立基线
- 按照既定策略,报告各配置管理项的状态
- 按照既定策略,确认配置管理项的信息
- 按照既定策略,管理配置管理项的存储
总体思路是策略->行动->报告信息->确认信息->存储。
2.2.1 Key words
配置管理过程的核心目的在于建立和维护项目或者过程中的工作产品的完整性,完整性包括
- 配置管理项的识别与定义
- 控制配置管理项的变更与发布
- 报告配置项的信息
- 确认配置项的信息
- 确认配置项和baseline的存储信息
- Integrity
- configuration items
- Work products
- Modifications
- Releases
- Status
- baselines
- completeness
- consistency
- storage
- Establish & Maintain
- Strategy
- tools
- branch
- Controlled
- verify
- Manage
- available