发新话题
打印

[原创] 配置项控制等级分类定义( 此文章被查看:1986次,被回复:8篇!! )

配置项控制等级分类定义

Control Level
There are some situations leading to multiple levels of control include the following:
        Differences in the levels of control needed at different times in the project life cycle
        Differences in the levels of control needed for different types of systems
        Differences in the levels of control needed to satisfy privacy and security requirement for the configuration items
CM should design a suitable control system according to the characteristics of projects. Generally, there are three levels of CM defined as follows:
Level 1: The CIs need not undergo a rigorous version control and change control.
Level 2: The CIs need to be under manage and control
Level 3: The CIs need to be under Configuration Management Control
The examples stated under each control level are a suggest list and may be modified as per the specific needs.
The level of configuration management to be followed by a project or P&Q or training group would be identified and documented in the respective document.

1        CIs under Level 1 CM
CIs which need to be defined and maintained in a project are identified under Level 1 CM. These CIs need not undergo a rigorous version control and change control. The definition will include the location and access control mechanism for these CIs so as to allow them to be stored and accessed appropriately.  
Typical configuration items for Level 1 CM are:
        Minutes of Meeting
        PMC/Issue/Risk Log
        QA audit reports
        CM Log and Reports
        Peer Review Reports
        Quality Records
        Status Reports
        Status Review Presentation
        Initial Estimation papers
        Correspondence having contractual implications
        P&Q Records
        Training Records
        Risk Repository
        SPI/Training/Skills Database
        Pilot documentation for organizational innovations, records created for DAR, etc.

2         CIs under Level 2 CM (Manage and Control)
CIs for which baseline needs to be established and maintained is identified at manage and control level. The project/group would need to maintain and track different versions of the CIs. Management documents such as plans and metrics can be put under mange and control.
Typical configuration items for Level 2 CM (Manage and Control) are:
        Technical Proposal
        Project Management Plan, Schedule, CM Plan, QA Plan, QPM Plan
        Size Calculation document
        Estimation document
        Requirement Traceability Matrix and Most of the metrics
        Work breakdown Structure
        P&Q Plan, Process Improvement Plan, MA plan and Organizational Training Plan etc.

3        CIs under Level 3 CM (CM Control)
CIs for which baseline needs to be established and maintained are identified under CM Control. The change to these CIs shall follow formal change procedure. Engineering documents and other important documents shall be put under CM control.
Typical configuration items for Level 3 CM (CM Control) are:
        Project Initiation Document
        Requirement Definition Document
        Requirement Analysis Document
        Design Document
        Software Codes
        Test Case
        Test Data
        Test Report
        User Manual
        Postmortem



© 本文为 flyee_cnSCMLife 共同所有,未经同意,请勿转载 ©如该文侵犯了您的版权,请联系管理员

TOP

好文,



© 本文为 yeoh206SCMLife 共同所有,未经同意,请勿转载 ©如该文侵犯了您的版权,请联系管理员

TOP

嗯,很有用
不过想知道这个CM的LEVEL和CMM的level有对应关系吗



© 本文为 youkeSCMLife 共同所有,未经同意,请勿转载 ©如该文侵犯了您的版权,请联系管理员

TOP

没有对应关系,这个level的定义可以和评审的方法以及变更的流程结合到一起。

© 本文为 flyee_cn 所有,未经同意,请勿转载
©如该文侵犯了您的版权,请联系管理员

TOP

真的有严格按照这个来划分CI控制等级的嘛?

© 本文为 polestar 所有,未经同意,请勿转载
©如该文侵犯了您的版权,请联系管理员

TOP

我们就是,做起来很容易

© 本文为 flyee_cn 所有,未经同意,请勿转载
©如该文侵犯了您的版权,请联系管理员

TOP

我以前做配置管理员的时候就这么考虑过,后来嫌放在不同地方麻烦,就都放在一个配置库里,都用版本给管起来了。

© 本文为 yixianhu 所有,未经同意,请勿转载
©如该文侵犯了您的版权,请联系管理员

TOP

先收藏再说,或许某一天有用~~

© 本文为 黄六梅 所有,未经同意,请勿转载
©如该文侵犯了您的版权,请联系管理员

TOP

看来自己要加强英语的学习了!
貌似很多都看不懂,
郁闷。

© 本文为 CMStruggling 所有,未经同意,请勿转载
©如该文侵犯了您的版权,请联系管理员

TOP

发新话题