Process Improvement -CMMI. Xin Feng

Transcription

1 Process Improvement -CMMI Xin Feng

2 Objectives History CMMI Why CMMI CMMI representations 4/11/2011 Software Engineering 2

3 Process Improvement Achieve both qualityand productivity ( 生 产 力 ) It is not necessary to change. Survival is not mandatory W.E.Deming 4/11/2011 Software Engineering 3

4 CMM Capability Maturity Model ( 能 力 成 熟 度 模 型 ) Software Engineering Institute (SEI), MITRE Corporation Started in 1986 First version was published in 1991 Version 1.1 released in 1993 Objectives Assess the capabilities ( 能 力 )of software contractors ( 承 包 商 ) Improve the maturity ( 成 熟 )of software development 4/11/2011 Software Engineering 4

5 CMM CMM was successful and widely adopted ( 采 用 ) Imitations ( 模 仿 )came SE-CMM (Software Engineering CMM) People CMM IPD-CMM (The Integrated Product Development CMM) EIA 731 System Security Engineering CMM ISO/IEC /11/2011 Software Engineering 5

6 CMM CMM was successful and widely adopted Conflicts came Process improvement goals Techniques Training Choices of models 4/11/2011 Software Engineering 6

7 Confused?

8 New Changes? Environment More and more complex More people, distributed assignments Work mode Cross-discipline teams Concurrent engineering Multinational ( 跨 国 )standards 4/11/2011 Software Engineering 8

9 CMMI Capability Maturity Model Integration SEI, government, industry Started in 1998 Released in people Several hundreds of pages Objectives Codify the tenets of model-bases process improvement Provide a single, integrated ( 集 成 )framework for improving engineering processes that span( 跨 越 )several disciplines. 4/11/2011 Software Engineering 9

10 CMMI Three source models SW-CMM (Software) EIA/IS 731 (System Engineering) IPD-CMM (Integrated Product and Process Development) Two representations Staged CMMI model Continuous CMMI model 4/11/2011 Software Engineering 10

11 CMMI Benefits Provide users with a choice of single or integrated disciplines Provide a choice of a staged or continuous representation Contain clear goalsand extensive guidance on the best practices Provide flexibility and extension into new disciplines. 4/11/2011 Software Engineering 11

12 CMMI More benefits Reduce costs 4/11/2011 Software Engineering 12

13 CMMI Content Essential to the model Essential to understand what to do and how to demonstrate E.g. a goal May not fully essential May not present Can play a central role in process improvement E.g. a practice Required items Expected items Informative items CMMI items These items constitute the majority of the model Provide useful guidance for process improvement Some clarifications E.g., a reference 4/11/2011 Software Engineering 13

14 Specific Practice 1 Specific Practice 2 Specific Practice m Specific goal Specific goal CMMI Content Specific goal Specific goal Process area 2 Generic Practice 2 Generic Practice 1 Process area 1 Generic goals Specific goal CMMI Model Process area n 4/11/2011 Software Engineering 14

15 Process Areas A process area is a group of important topics related to the process improvement It contains goals and practices Totally there are 25 process areas for CMMI 4/11/2011 Software Engineering 15

16 Goals and Practices Agoal represents a desirable state. If it is achieved, it means that the process control has reached a certain degree Specific goal Only for a single process area A process area has 1 to 4 specific goals Generic goal Apply to all the areas E.g., Requirements are managed and inconsistencies with project plans and work products are identified is a specific goal in the process area Requirements Management E.g., The process is institutionalized as a managed process is a generic goal 4/11/2011 Software Engineering 16

17 Practices A practice represents the expected means of achieving a goal Specific practice Unique( 独 一 无 二 )to a single process area Generic ( 共 有 的 )practice Apply across all process areas 4/11/2011 Software Engineering 17

18 Two Representations Staged representation Maturity levels Continuous representation Capability levels 4/11/2011 Software Engineering 18

19 Two Representations Staged representation Maturity levels Continuous representation Capability levels 4/11/2011 Software Engineering 19

20 Staged Representation Road map: maturity levels Optimizing Managed Defined Repeatable Continual measurement Quantitative measurement Establish effective process managements Basic management 1 Initial No concerns about process 4/11/2011 Software Engineering 20

21 Two Representations Staged representation Maturity levels Continuous representation Capability levels 4/11/2011 Software Engineering 21

22 Continuous Representation Capability Level 5 (Continuously improved) Capability Level 4 (Quatitatively) Capability Level 3 (Defined) Capability Level 2 (Managed) Capability Level 1 (Performed) Capability Level 0 (Incomplete) Process area 1 Process area 2 Process area n 4/11/2011 Software Engineering 22

23 Process Areas cont d Category Process Area Maturity Process Management Project Management Organizational Process Definition 3 Organizational Process Focus 3 Organizational Training 3 Organizational Process Performance 4 Organizational Innovation and Deployment 5 Project Planning 2 Project Monitoring and Control 2 Supplier Agreement Management 2 Integrated Project Management for IPPD 3 Risk Management 3 Integrated Teaming 3 Integrated Supplier Management 3 Quantitative Project Management 4

24 Process Areas Category Process area Maturity level Engineering Requirement management 2 Requirement development 3 Technical solution 3 Product integration 3 Verification 3 Validation 3 Support Configuration management 2 Process and product 2 quality assurance Measurement and analysis 2 Decision analysis and resolution 3 Organizational environment for integration 3 Casual analysis and resolution 5

25 Picking a Presentation Benefits of staged representation Manage processes across the organization Good communications about process among employees Improve accuracy if project estimates Improve cost and quality control Use quantitative data to guide problem analysis and improvement efforts Benefits of continuous representation Focus on risks that are specific to individual process areas The structure is more compatible with ISO/IEC New process areas can be easily added with minimal effects. 4/11/2011 Software Engineering 25

26 Picking a Presentation 4/11/2011 Software Engineering 26

27 Picking a Presentation Training time Which one needs less training Business environment What kind of staging is better Management What information is needed 4/11/2011 Software Engineering 27

28 Summary CMMI Two presentations Process areas, goals, practices 4/11/2011 Software Engineering 28