[工学]软件配置管理2.ppt

Ch2 CM in maturity models A number of maturity models exist for development in general: All the models include requirements for CM; The requirements vary from models to model So does the way in which CM forms part of the maturity assessment methods. 2.1 CMM v1.1 2.2 CMMI 2.3 ISO 15504 2.1 CMM v1.1 CMM is the most widely used model Developed and supported by SEI, CMU, in 1991; Following an initiative from the Department of defense, which has identified a need for an assessment method of their software suppliers. CMM maturity levels Each maturity level has a number of associated KPA ( key process areas) CM is a KPA at level 2 The goals for CM are: Software CM activities are planned; Selected software work products are identified, controlled, and made available; Changes to identified software work products are controlled; Affected groups and individuals are informed of the status and content of software baselines. Definition CM in CMM 1.1: “ The purpose of Software CM is to establish and maintain the integrity of the products of the software project throughout the project’s software life cycle. Software CM is an integral part of most software engineering and management processes ” Activities See table 2-1 CMMI CMMI ( Capability Maturity Model Integration ), based on the following models: CMM 2.0 EIA/IS, SECM IPD-CMM See table 2-2 CMMI process areas Four main groups: Process management Project management Engineering Support Definition CM in CMMI “ The purpose of CM is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, an configuration audits ” Goals Goals for CM in CMMI are: Establish baselines Track and control changes Establish integrity Practice-to-goal relationships The practices for the CM goals are: SG1 SP1.1 –1 Identify configuration items SP1.2 – 1 Establish a CM system SP1.3 - 1 Create or release Baselines SG2 SP2.1 – 1 Track changes SP2.2 – 1