216
CMMI Tutorial Apr 22, 2003 CMMI V1.1 Tutorial Mike Phillips, CMMI Program Manager Sponsored by the U.S. Department of Defense © 2003 by Carnegie Mellon University Pittsburgh, PA 15213-3890

CMMI Tutorial Apr 22, 2003 CMMI V1.1 Tutorial Mike Phillips, CMMI Program Manager Sponsored by the U.S. Department of Defense © 2003 by Carnegie Mellon

  • View
    232

  • Download
    0

Embed Size (px)

Citation preview

  • Slide 1
  • CMMI Tutorial Apr 22, 2003 CMMI V1.1 Tutorial Mike Phillips, CMMI Program Manager Sponsored by the U.S. Department of Defense 2003 by Carnegie Mellon University Pittsburgh, PA 15213-3890
  • Slide 2
  • CMMI Tutorial Apr 22, 2003 2 Agenda Why focus on Process? Background Why use a Model? CMMI Structure Comparisons with SW-CMM v1.1, SE-CMM, and EIA/IS 731_ Process Areas Overview Appraisal Methodology Training
  • Slide 3
  • CMMI Tutorial Apr 22, 2003 3 Everyone realizes the importance of having a motivated, quality work force but......even our finest people cant perform at their best when the process is not understood or operating at its best. PEOPLE PROCESS TECHNOLOGY Quality Leverage Points Major determinants of product cost, schedule, and quality
  • Slide 4
  • CMMI Tutorial Apr 22, 2003 4 What Is Process? How do you define process?
  • Slide 5
  • CMMI Tutorial Apr 22, 2003 5 General Definition of Process A process is a set of practices performed to achieve a given purpose; it may include tools, methods, materials, and/or people. While process is often described as a leg of the process-people-technology triad, it may also be considered the glue that unifies the other aspects. How do you define process?
  • Slide 6
  • CMMI Tutorial Apr 22, 2003 6 Why Focus on Process? Process provides a constructive, high-leverage focus... as opposed to a focus on people Your work force, on the average, is as good as it is trained to be. Working harder is not the answer. Working smarter, through process, is the answer. as opposed to a focus on technology Technology applied without a suitable roadmap will not result in significant payoff. Technology provides the most benefit in the context of an appropriate process roadmap.
  • Slide 7
  • CMMI Tutorial Apr 22, 2003 7 Underlying Premise of Process Improvement The quality of a product is largely determined by the quality of the process that is used to develop and maintain it. Based on TQM principles as taught by Shewhart, Juran, Deming and Humphrey.
  • Slide 8
  • CMMI Tutorial Apr 22, 2003 8 Early Process Improvement The theories of process management are a synthesis of the concepts of Deming, Crosby, Juran, and others. Over the past 30 years, these theories have been used to address problems common to many organizations. Solutions have been discovered, but a gap existed between the state of the practice and the state of the art. Many of these concepts have been used to build process-improvement models.
  • Slide 9
  • CMMI Tutorial Apr 22, 2003 9 What Is a Process Model? A model is a structured collection of elements that describe characteristics of effective processes. Processes included are those proven by experience to be effective.
  • Slide 10
  • CMMI Tutorial Apr 22, 2003 10 How Is a Model Used? A model is used to help set process improvement objectives and priorities, improve processes, and provide guidance for ensuring stable, capable, and mature processes as a guide for improvement of organizational processes
  • Slide 11
  • CMMI Tutorial Apr 22, 2003 11 Why Is a Model Important? A model provides a place to start the benefit of a communitys prior experiences a common language and a shared vision a framework for prioritizing actions
  • Slide 12
  • CMMI Tutorial Apr 22, 2003 12 Models All models are wrong, but some are useful. George Box Simplified approximations of reality that provide insight.
  • Slide 13
  • CMMI Tutorial Apr 22, 2003 13 What Model do I use? Historically: Depends on the discipline that you want to model. Software Engineering Systems Engineering Software Acquisition Systems Security etc.
  • Slide 14
  • CMMI Tutorial Apr 22, 2003 14 What is a CMM? Capability Maturity Model: A reference model of mature practices in a specified discipline, used to assess a groups capability to perform that discipline CMMs differ by Discipline (software, systems, acquisition, etc.) Structure (staged versus continuous) How Maturity is Defined (process improvement path) How Capability is Defined (institutionalization) Capability Maturity Model and CMM are used by the Software Engineering Institute (SEI) to denote a particular class of maturity models Capability Maturity Model, CMM, CMM Integration, and CMMI are service marks and registered trademarks of Carnegie Mellon University
  • Slide 15
  • CMMI Tutorial Apr 22, 2003 15 Commonly Used CMMs Software CMMstagedsoftware development System Engineering CMMcontinuoussystem engineering System Engineering Capability Modelcontinuoussystem engineering Software Acquisition CMMstagedsoftware acquisition System Security Engineering CMMcontinuoussecurity engineering Personal Software Processstagedindividual software development FAA-iCMMcontinuoussoftware engineering, systems engineering, and acquisition IPD-CMMhybridintegrated product development People CMMstagedworkforce SPICE Modelcontinuoussoftware development
  • Slide 16
  • CMMI Tutorial Apr 22, 2003 16 The Problem Systems and software disciplines have traditionally not been well integrated The importance of software in systems has increased dramatically Example: % of requirements allocated to software: * B-2 -- 65% F-22 -- 80% The DOD has emphasized the need to make the systems/software interface more seamless Systems Software * Source: Standish Group Chaos Report
  • Slide 17
  • CMMI Tutorial Apr 22, 2003 17 So Many Models, So Little Time Software CMM Software CMM Systems Security Engr CMM Systems Security Engr CMM Systems Engr CMM Systems Engr CMM People CMM People CMM ZZZ CMM ZZZ CMM FAA iCMM FAA iCMM IPD CMM IPD CMM Software Acq CMM Software Acq CMM EIA 731 Different structures, formats, terms, ways of measuring maturity Causes confusion, especially when using more than one model Hard to integrate them in a combined improvement program Hard to use multiple models in supplier selection
  • Slide 18
  • CMMI Tutorial Apr 22, 2003 18 CMMI to the Rescue! Integrates systems and software disciplines into one process improvement framework. Provides a framework for introducing new disciplines as needs arise.
  • Slide 19
  • CMMI Tutorial Apr 22, 2003 19 Bridging the Divide Systems engineering and software engineering processes are integrated. Integrates systems and software disciplines into one process improvement framework. Provides a framework for introducing new disciplines as needs arise.
  • Slide 20
  • CMMI Tutorial Apr 22, 2003 20 But We Dont Do That... Some organizations see themselves as performing just one discipline Software Systems Acquisition But Software always must be part of some kind of system Systems that dont have software are rare Acquisition can involve both Communication and cooperation with other disciplines, even if they are external to our organization is vital
  • Slide 21
  • CMMI Tutorial Apr 22, 2003 21 The CMMI Project DoD sponsored collaboration between industry, Government, SEI Over 100 people involved U.S. Army, Navy, Air Force Federal Aviation Administration National Security Agency Software Engineering Institute ADP, Inc. AT&T Labs BAE Boeing Computer Sciences Corporation EER Systems Ericsson Canada Ernst and Young General Dynamics Harris Corporation Honeywell KPMG Lockheed Martin Motorola Northrop Grumman Pacific Bell Q-Labs Raytheon Reuters Rockwell Collins SAIC Software Productivity Consortium Sverdrup Corporation TeraQuest Thomson CSF TRW
  • Slide 22
  • CMMI Tutorial Apr 22, 2003 22 CMMI Models Source Models Capability Maturity Model for Software V2, draft C (SW-CMM V2C) EIA Interim Standard 731, System Engineering Capability Model (SECM) Integrated Product Development Capability Maturity Model, draft V0.98 (IPD-CMM) CMMI-SE/SW Staged Representation CMMI-SE/SW Continuous Representation Combined System Engineering / Software Engineering model Can be applied to: Just the software engineering projects in an organization Just the system engineering projects in an organization Both IPPD can be used in either/both
  • Slide 23
  • CMMI Tutorial Apr 22, 2003 23 Staged ML 1 ML2 ML3 ML4 ML5...for an established set of process areas across an organization Continuous...for a single process area or a set of process areas PA Process Area Capability 0 1 2 3 4 5 PA Comparing Model Representations
  • Slide 24
  • CMMI Tutorial Apr 22, 2003 24 Relating Process Area Capability and Organizational Maturity 1 Process area capability and organizational maturity are similar concepts. The difference between them is that process area capability deals with a set of processes relating to a single process area or specific practice, while organizational maturity pertains to a set of process areas across an organization.
  • Slide 25
  • CMMI Tutorial Apr 22, 2003 25 Relating Process Area Capability and Organizational Maturity 2 Although the comparison of ratings and levels is an advanced topic we dont address in this tutorial, in general terms, if a set of organizational processes have been appraised at a particular maturity level, the appraised processes may demonstrate a comparable level of process area capability.
  • Slide 26
  • CMMI Tutorial Apr 22, 2003 26 Remember A model is not a process. The model shows what to do, NOT how to do it or who does it.
  • Slide 27
  • CMMI Tutorial Apr 22, 2003 27 Why Do We Have Two Representations? Source Model Heritage Software CMM--Staged SECM--Continuous IPD CMM--Hybrid Proponents for each type of representation were part of CMMI product development team. Selecting a single representation approach became too hard. A compromise was made to initially support two representations of the model with equivalent content.
  • Slide 28
  • CMMI Tutorial Apr 22, 2003 28 Advantages of the Staged Representation Provides a roadmap for implementing: groups of process areas sequencing of implementation Familiar structure for those transitioning from the SW-CMM
  • Slide 29
  • CMMI Tutorial Apr 22, 2003 29 Advantages of the Continuous Representation Provides maximum flexibility for focusing on specific process areas according to business goals and objectives. Familiar structure for those transitioning from the systems engineering community.
  • Slide 30
  • CMMI Tutorial Apr 22, 2003 30 CMMI Product Suite Models Disciplines Systems Engineering SE Software Engineering SW Integrated Product and Process Development (IPPD) Supplier Sourcing (SS) Representations Staged Continuous Training Model Introduction to CMMI Intermediate Concepts Instructor Training Lead Appraiser Appraisal methods Appraisal Requirements for CMMI (ARC) SCAMPI Method Description Document (MDD)
  • Slide 31
  • CMMI Tutorial Apr 22, 2003 31 CMMI in a Nutshell A CMMI model provides a structured view of process improvement across an organization CMMI can help set process improvement goals and priorities provide guidance for quality processes provide a yardstick for appraising current practices
  • Slide 32
  • CMMI Tutorial Apr 22, 2003 32 The Bottom Line 1 Process improvement should be done to help the business not for its own sake. In God we trust, all others bring data. - W. Edwards Deming
  • Slide 33
  • CMMI Tutorial Apr 22, 2003 33 The Bottom Line 2 Improvement means different things to different organizations: What are your business goals? How do you measure progress? Improvement is a long-term, strategic effort: What is the expected impact on the bottom line? How will impact be measured?
  • Slide 34
  • CMMI Tutorial Apr 22, 2003 34 Categories of Process Improvement Benefits Process improvement benefits fall into one of seven general categories: improved schedule and budget predictability improved cycle time increased productivity improved quality (as measured by defects) increased customer satisfaction improved employee morale increased return on investment decreased cost of quality
  • Slide 35
  • CMMI Tutorial Apr 22, 2003 35 Results: Boeing Effort Estimation. 0 % 140% -140%.................................................................... Without Historical Data With Historical Data Variance between + 20% to - 145% Variance between - 20% to + 20% (Mostly Level 1 & 2) (Level 3) Over/Under Percentage. (Based on 120 projects in Boeing Information Systems)...................................................................... Reference: John D. Vu. Software Process Improvement Journey:From Level 1 to Level 5. 7th SEPG Conference, San Jose, March 1997. Improved Schedule and Budget Predictability
  • Slide 36
  • CMMI Tutorial Apr 22, 2003 36 Source: Software Engineering Div., Hill AFB, Published in Crosstalk May 1999 Improved Cycle Time
  • Slide 37
  • CMMI Tutorial Apr 22, 2003 37 Source: Software Engineering Div., Hill AFB, Published in Crosstalk May 1999 Increased Productivity
  • Slide 38
  • CMMI Tutorial Apr 22, 2003 38 Increased Productivity and Quality
  • Slide 39
  • CMMI Tutorial Apr 22, 2003 39 Topics The structure of the CMMI documents The structure of the CMMI Continuous representation The structure of the CMMI Staged representation Summary
  • Slide 40
  • CMMI Tutorial Apr 22, 2003 40 Organization of Continuous Model -1 Six chapters provide an overview The Introduction Structure of the Model Model Terminology Capability Level and Generic Model components Understanding the Model Using the Model
  • Slide 41
  • CMMI Tutorial Apr 22, 2003 41 Organization of Continuous Model -2 Process areas Process management Project Management Engineering Support Appendixes References Acronyms Glossary Required and expected Model Elements CMMI Project Participants Equivalent Staging
  • Slide 42
  • CMMI Tutorial Apr 22, 2003 42 Organization of Staged Model -1 Six chapters provide an overview The Introduction Structure of the Model Model Terminology Maturity Levels, Common Features, and Generic Practices Understanding the Model Using the Model
  • Slide 43
  • CMMI Tutorial Apr 22, 2003 43 Organization of Staged Model -2 Process areas Maturity Level: 2 Managed Maturity Level: 3 Defined Maturity Level: 4 Quantitatively Managed Maturity Level: 5 Optimizing Appendixes References Acronyms Glossary Required and expected Model Elements CMMI Project Participants
  • Slide 44
  • CMMI Tutorial Apr 22, 2003 44 Model Components Process Areas Specific Goals Specific Practices Generic Goals Generic Practices Typical Work Products Sub-practices Notes Discipline Amplifications Generic Practice Elaborations References
  • Slide 45
  • CMMI Tutorial Apr 22, 2003 45 CMMI Structure One Model, Two Representations Maturity Level 5 OID, CAR Maturity Level 4 OPP, QPM Maturity Level 3 REQD, TS, PI, VER, VAL, OPF, OPD, OT, IPM, RSKM, DAR Overview Introduction Structure of the Model Model Terminology Maturity Levels, Common Features, and Generic Practices Understanding the Model Using the Model Maturity Level 2 REQM, PP, PMC, SAM, MA, PPQA, CM Appendixes Engineering REQM, REQD, TS, PI, VER, VAL Project Management PP, PMC, SAM IPM, RSKM, QPM Process Management OPF, OPD, OT, OPP, OID Process Management PAs - Goals - Practices Support CM, PPQA, MA, CAR, DAR Appendixes CMMI-SE/SW Staged Overview Introduction Structure of the Model Model Terminology Capability Levels and Generic Model Components Understanding the Model Using the Model CMMI-SE/SW Continuous
  • Slide 46
  • CMMI Tutorial Apr 22, 2003 46 Topics Structure of the CMMI documents The structure of the CMMI continuous representation The structure of the CMMI staged representation Summary
  • Slide 47
  • CMMI Tutorial Apr 22, 2003 47 Process Area Capability Profile A process area capability profile may be represented by a set of points in two dimensions. the process dimension What you do the capability dimension How well you do it Capability (How well) Process Area (What you do)
  • Slide 48
  • CMMI Tutorial Apr 22, 2003 48 The Process Dimension The values on this axis describe what processes (described within Process Areas) you perform. Process Area 1 Process Area n Process Area 2 Process Area 3 Capability
  • Slide 49
  • CMMI Tutorial Apr 22, 2003 49 Process Areas Process Areas (PAs) are a cluster of related practices. They are the major building blocks in establishing process capability. Example PA: Requirements Management
  • Slide 50
  • CMMI Tutorial Apr 22, 2003 50 Requirements Management Requirements Development Technical Solution Product Integration Verification Validation Engineering Project Management Project Planning Project Monitoring and Control Supplier Agreement Management Integrated Project Management(IPPD) Integrated Supplier Management (SS) Integrated Teaming (IPPD) Risk Management Quantitative Project Management Organizational Process Focus Organizational Process Definition Organizational Training Organizational Process Performance Organizational Innovation and Deployment Process Management Configuration Management Process and Product Quality Assurance Measurement and Analysis Causal Analysis and Resolution Decision Analysis and Resolution Organizational Environment for Integration (IPPD) Support Continuous Organization of Process Areas Category Process Area
  • Slide 51
  • CMMI Tutorial Apr 22, 2003 51 Decision Analysis and Resolution Requirements Development System Product Deliveries Project Planning Supplier Agreement Management Product Control Products Outcome & Feedback Product Verification Validation Measurement and Analysis Deficiencies Directives, Constraints, Contracting Activity Planning Requirements Definition Budgeting Priority Assessment & Certification Integrated Project Management Project Monitoring and Control Risk Management Technical Solution Product Integration Requirements Management Configuration Management Quality Assurance Program Management Technical Execution Process Focus Process Definition Training Quantitative Mgmt Process Performance Innovation and Deployment Process Maturation Organizational Process Management Mission Area Planning Concurrent Front-End Activities Causal Analysis and Resolution Life Cycle Relationships Mission Shortfalls Integrated Supplier Management Integrated Teaming Environment for Integration
  • Slide 52
  • CMMI Tutorial Apr 22, 2003 52 The Capability Dimension -1 The values on this axis describe how well you perform a process (called Capability Levels). Process not performed Capability Process Area 1 Process Area n Process Area 2 Process Area 3
  • Slide 53
  • CMMI Tutorial Apr 22, 2003 53 The Capability Dimension -2 The values on this axis describe how well you perform a process (called Capability Levels). Capability Process Area 1 Process Area n Process Area 2 Process Area 3 Process performed well and continuously improved Process not performed
  • Slide 54
  • CMMI Tutorial Apr 22, 2003 54 Capability Levels A capability level is a well-defined evolutionary plateau describing the capability of a process area. There are six capability levels. Each level is a layer in the foundation for continuous process improvement. Thus, capability levels are cumulative, i.e., a higher capability level includes the attributes of the lower levels.
  • Slide 55
  • CMMI Tutorial Apr 22, 2003 55 The Capability Levels 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed 1 Performed 0 Incomplete
  • Slide 56
  • CMMI Tutorial Apr 22, 2003 56 Capability Levels are Cumulative Because capability levels build upon one another, there can be no gaps.
  • Slide 57
  • CMMI Tutorial Apr 22, 2003 57 Representing Process Capability The capability of a implemented process can be represented by a bar. Process Capability This point represents a higher level of capability than this point in a specific process area 32103210 Process Area n
  • Slide 58
  • CMMI Tutorial Apr 22, 2003 58 An Example Process Area Capability Profile P r o c e s s A r e a REQM PP PMC etc 543210543210 C a p a b i l i t y
  • Slide 59
  • CMMI Tutorial Apr 22, 2003 59 Realizing These Concepts in the CMMI Continuous Model Goals and Practices are the model elements used to realize the values on both the capability and process dimensions. Goal A high level statement of the outcome to be achieved by effective implementation of a group of practices. Practice A description of an action that is necessary to enact a key element of a process area.
  • Slide 60
  • CMMI Tutorial Apr 22, 2003 60 There Are Two Types of Goals and Practices Specific Goals and Specific Practices realize the process dimension therefore, they apply to a particular Process Area Generic Goals and Generic Practices realize the capability dimension therefore, they apply across all Process Areas
  • Slide 61
  • CMMI Tutorial Apr 22, 2003 61 Example: Specific Goal and Specific Practice Specific Goal (from Requirements Management PA) Requirements are managed and inconsistencies with project plans and work products are identified. Specific Practice (from Requirements Management PA) Maintain bidirectional traceability among the requirements and the project plans and work products.
  • Slide 62
  • CMMI Tutorial Apr 22, 2003 62 Example: Generic Goal and Generic Practice Generic Goal (from Capability Level 1) The process supports and enables achievement of the specific goals of the process area by transforming identifiable input work products to produce identifiable output work products. Generic Practice (from Capability Level 1) Perform the basic activities of the process area to develop work products and provide services to achieve the specific goals of the process area.
  • Slide 63
  • CMMI Tutorial Apr 22, 2003 63 Structure of the CMMI Continuous Representation Generic Goals & Generic Practices Generic Goals & Generic Practices Specific Goals & Practices Specific Goals & Practices
  • Slide 64
  • CMMI Tutorial Apr 22, 2003 64 Critical Distinctions performed vs.managed --the extent to which the process is planned; performance is managed against the plan; corrective actions are taken when needed managedvs.defined --the scope of application of the process descriptions, standards, and procedures (i.e., project vs. organization) defined vs.quantitatively managed --the predictability of process performance quantitatively managedvs.optimizing --the process is continuously improved by addressing common causes of process variation
  • Slide 65
  • CMMI Tutorial Apr 22, 2003 65 Improving a Process Area CL0 Not performed, incomplete No GPs or SPs exist GP1.1 CL1 (base) SPs GP1.1 through GP2.10 CL1 + CL2* SPs GP1.1 through GP3.2 CL1+CL2*+CL3* SPs GP1.1 through GP4.2 CL1+CL2*+CL3* SPs GP1.1 through GP5.2 CL1+CL2*+CL3* SPs CL1 Performed Perform the work CL2 Managed Adhere to policy, follow documented plans and processes, apply adequate resources, assign responsibility and authority, train people, apply CM, monitor, control, and evaluate process, identify and involve stakeholders, review with management CL3 Defined Projects process is tailored from organizations standard processes, understand process qualitatively, process contributes to the organizations assets CL4 Quantitatively Managed Measure process performance, stabilize process, control charts, deal with causes of special variations CL5 Optimizing Defect prevention, proactive improvement, innovative technology insertion and deployment * Advanced practices exist only in the Engineering PAs.
  • Slide 66
  • CMMI Tutorial Apr 22, 2003 66 REQM - Capability Levels 1 & 2 Requirements Management Specific practices (CL1 - base) SP1.1-1: Obtain an Understanding of Requirements SP1.3-1: Manage Requirements Changes SP1.5-1: Identify Inconsistencies Between Project Work and Requirements Generic practices (CL1) GP1.1: Perform Base Practices Specific practices (CL2 - advanced) SP1.2-2: Obtain Commitment to Requirements SP1.4-2: Maintain Bidirectional Traceability of Requirements Generic practices (CL2) GP2.1: Establish an Organizational Policy GP2.2: Plan the Process GP2.3: Provide Resources GP2.4: Assign Responsibility GP2.5: Train People GP2.6: Manage Configurations GP2.7: Identify and Involve Relevant Stakeholders GP2.8: Monitor and Control the Process GP2.9: Objectively Evaluate Adherence GP2.10: Review Status with Higher Level Management
  • Slide 67
  • CMMI Tutorial Apr 22, 2003 67 REQM - Capability Level 3 Requirements Management Specific practices (CL1 & CL2) SP1.1-1: Obtain an Understanding of Requirements SP1.2-2: Obtain Commitment to Requirements SP1.3-1: Manage Requirements Changes SP1.4-2: Maintain Bidirectional Traceability of Requirements SP1.5-1: Identify Inconsistencies Between Project Work and Requirements Generic practices (CL1 & CL2) GP1.1: Perform Base Practices GP2.1: Establish an Organizational Policy GP2.2: Plan the Process GP2.3: Provide Resources GP2.4: Assign Responsibility GP2.5: Train People GP2.6: Manage Configurations GP2.7: Identify and Involve Relevant Stakeholders GP2.8: Monitor and Control the Process GP2.9: Objectively Evaluate Adherence GP2.10: Review Status w/Higher Level Management Specific practices (CL3) All the CL1 & CL2 Specific Practices Generic practices (CL3) All the CL1 & CL2 Generic Practices plus(+): GP3.1: Establish a Defined Process GP3.2: Collect Improvement Information
  • Slide 68
  • CMMI Tutorial Apr 22, 2003 68 REQM - Capability Levels 4 & 5 Requirements Management Specific practices (CL4) All the CL1 & CL2 Specific Practices Generic practices (CL4) All the CL1 & CL2 & CL3 Generic Practices plus(+): GP4.1: Establish Quantitative Objectives for the Process GP4.2: Stabilize Subprocess Performance Specific practices (CL5) All the CL1 & CL2 Specific Practices Generic practices (CL5) All the CL1 & CL2 & CL3 & CL4 Generic Practices plus(+): GP5.1: Ensure Continuous Process Improvement GP5.2: Correct Root Causes of Problems
  • Slide 69
  • CMMI Tutorial Apr 22, 2003 69 Summary CMMI models were developed with broad participation and review. Process Areas identify what you do. Capability Levels identify how well you do it.
  • Slide 70
  • CMMI Tutorial Apr 22, 2003 70 Topics Structure of the CMMI documents The structure of the CMMI Continuous representation document The Structure of the CMMI Staged representation Summary
  • Slide 71
  • CMMI Tutorial Apr 22, 2003 71 Maturity Levels A maturity level is a well-defined evolutionary plateau on the path to becoming a mature organization. There are five maturity levels. Each level is a layer in the foundation for continuous process improvement.
  • Slide 72
  • CMMI Tutorial Apr 22, 2003 72 The Maturity Levels Process unpredictable, poorly controlled and reactive Process characterized for projects and is often reactive Process characterized for the organization and is proactive Process measured and controlled Focus on process improvement Optimizing Quantitatively Managed Defined Performed Managed Optimizing Defined 1 2 3 4 5
  • Slide 73
  • CMMI Tutorial Apr 22, 2003 73 Structure of the CMMI Staged Representation Maturity Level Process Area Generic GoalsSpecific Goals Commitment to Perform Ability to Perform Directing Implementation Verification Common Features Commitment to Perform: creates policies and secures sponsorship for process improvement efforts Ability to Perform: ensures that the project and/or organization has the resources it needs to pursue process improvement Directing Implementation: collects, measures, and analyzes data related to processes Verification: verifies that the projects and/or organizations activities conform to requirements, processes, and procedures Commitment to Perform: creates policies and secures sponsorship for process improvement efforts Ability to Perform: ensures that the project and/or organization has the resources it needs to pursue process improvement Directing Implementation: collects, measures, and analyzes data related to processes Verification: verifies that the projects and/or organizations activities conform to requirements, processes, and procedures Generic Practices Specific Practices
  • Slide 74
  • CMMI Tutorial Apr 22, 2003 74 Maturity Levels Cannot Be Skipped A level provides a necessary foundation for effective implementation of processes at the next level. Higher level processes are easily sacrificed without the discipline provided by lower levels. The effect of innovation is obscured in a noisy process. Higher maturity level processes may be performed by organizations at lower maturity levels, with risk of not being consistently applied in a crisis.
  • Slide 75
  • CMMI Tutorial Apr 22, 2003 75 Process Areas Process Areas (PAs) are clusters of related practices performed collectively to achieve a set of goals. They are the major building blocks in establishing the process capability of an organization. Each process area has been defined to reside at a given maturity level.
  • Slide 76
  • CMMI Tutorial Apr 22, 2003 76 Process Areas by Maturity Level Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous process improvement Quantitative management Process standardization Basic project management Organizational Process Performance Quantitative Project Management Requirements Development Technical Solution Product Integration Verification Validation Organizational Process Focus Organizational Process Definition Organizational Training Integrated Project Management Integrated Supplier Management Risk Management Decision Analysis and Resolution Organizational Environment for Integration Integrated Teaming Requirements Management Project Planning Project Monitoring and Control Supplier Agreement Management Measurement and Analysis Process and Product Quality Assurance Configuration Management 1 Performed Process AreasLevel Focus (IPPD) (SS)
  • Slide 77
  • CMMI Tutorial Apr 22, 2003 77 Example: Specific Goal and Specific Practice Specific Goal (from Requirements Management PA) Requirements are managed and inconsistencies with project plans and work products are identified. Specific Practice (from Requirements Management PA) Maintain bidirectional traceability among the requirements and the project plans and work products.
  • Slide 78
  • CMMI Tutorial Apr 22, 2003 78 Example: Generic Goal and Generic Practice Generic Goal (from Capability Level 1) The process supports and enables achievement of the specific goals of the process area by transforming identifiable input work products to produce identifiable output work products. Generic Practice (from Capability Level 1) Perform the basic activities of the process area to develop work products and provide services to achieve the specific goals of the process area.
  • Slide 79
  • CMMI Tutorial Apr 22, 2003 79 Common Features Common features are a means of categorizing Generic practices. Commitment to perform: establishment of management policies Ability to perform: establishment and maintenance of plans, resources, assigned responsibility and authority, and training Directing implementation: measurement, control, and performance practices Verification: ensure implementation and compliance
  • Slide 80
  • CMMI Tutorial Apr 22, 2003 80 Another way to look at Common Features -1 Common feature categories are very similar across process areas. They are referred to as Institutionalization Common Features because they: ensure the process areas are effective, repeatable and lasting provide needed infrastructure support
  • Slide 81
  • CMMI Tutorial Apr 22, 2003 81 Common Feature Examples -1 from Requirements Management Process Area Commitment to perform: Establish and maintain an organizational policy for planning and performing the requirements management process. Ability to perform: Train the people performing or supporting the requirements management process as needed.
  • Slide 82
  • CMMI Tutorial Apr 22, 2003 82 Common Feature Examples -2 from Requirements Management Process Area Directing implementation: Place designated work products of the requirements management process under appropriate levels of configuration management. Verification: Review the activities, status, and results of the requirements management process with higher level management and resolve issues.
  • Slide 83
  • CMMI Tutorial Apr 22, 2003 83 Summary -1 There is one CMMI Model with two representations, Staged and Continuous. The material in both representations is the same just organized differently. Each representation provides different ways of implementing processes The CMMI model should be applied using intelligence, common sense, and professional judgment.
  • Slide 84
  • CMMI Tutorial Apr 22, 2003 84 Summary -2 Continuous Flexible in its application so the organization can choose which areas to emphasize. Provides equivalent staging to compare to staged representation. Staged Structured for implementation based on proven grouping and ordering of processes.
  • Slide 85
  • CMMI Tutorial Apr 22, 2003 85 CMMI-SE/SW Compared to SW-CMM v1.1
  • Slide 86
  • SW-CMM v1.1 vs. CMMI Process Areas Defect PreventionCausal Analysis and Resolution Technology Change MgmtOrganizational Innovation & Deployment Process Change Management Quantitative Process MgmtOrganizational Process Performance Software Quality MgmtQuantitative Project ManagementOrganization Process Focus Organization Process Definition Training ProgramOrganizational Training Integrated Software MgmtIntegrated Project Management Risk Management Software Product EngrRequirements Development Technical Solution Product Integration Intergroup Coordination Verification Peer Reviews Validation Decision Analysis and ResolutionRequirements Management Software Project PlanningProject Planning Software Project Tracking & OversightProject Monitoring and Control Software Subcontract MgmtSupplier Agreement Management Software Quality AssuranceProduct & Process Quality Assurance Software Configuration MgmtConfiguration Management Measurement and Analysis LEVEL 5 OPTIMIZING LEVEL 4 MANAGED LEVEL 3 DEFINED LEVEL 2 REPEATABLE 86
  • Slide 87
  • CMMI Tutorial Apr 22, 2003 87 CMMI Improvements Over the CMM Emphasis on measurable improvements to achieve business objectives. Process areas have been added to place more emphasis on some important practices: Risk Management Measurement and Analysis Engineering Process Areas Decision Analysis
  • Slide 88
  • CMMI Tutorial Apr 22, 2003 88 CMMI-SE/SW/IPPD Compared to EIA/IS 731 (Systems Engineering Capability Model)
  • Slide 89
  • CMMI Tutorial Apr 22, 2003 89 Background Electronic Industries Alliance Interim Standard (EIA/IS) 731, System Engineering Capability Model (SECM), was created as a merger of the SE-CMM and the INCOSE Systems Engineering Capability Assessment Model (SECAM) Used as a source model for CMMI
  • Slide 90
  • CMMI Tutorial Apr 22, 2003 90 What is the Systems Engineering Capability Model (SECM)? Describes the essential systems engineering and management tasks that any organization must perform Road map for systems engineering & management process improvement Systems engineering and management process measurement tool
  • Slide 91
  • CMMI Tutorial Apr 22, 2003 91 Define & Improve SE Process Manage Risk Manage Risk Manage Technology Define Stkhldr & Sys Level Rqmnts Monitor & Control Monitor & Control Integrate Disciplines Integrate Disciplines Manage Configurations Manage Configurations Manage Competency Environment Management Technical Manage SE Support Environment Coordinate with Suppliers Coordinate with Suppliers Manage Data Manage Data Define Technical Problem Define Solution Assess & Select Integrate System Verify System Validate System Plan & Organize Plan & Organize Ensure Quality SECM Focus Areas
  • Slide 92
  • CMMI Tutorial Apr 22, 2003 92 Comparison of Elements -1 CMMI Engineering PAs SECM Technical Focus Areas Requirements Management Requirements Development Technical Solution Product Integration Verification Validation 1.1 Define Stakeholder & System Level Requirements 1.2 Define Technical Requirements 1.3 Define Solution 1.4 Assess and Select 1.5 Integrate System 1.6 Verify System 1.7 Validate System Support
  • Slide 93
  • CMMI Tutorial Apr 22, 2003 93 Comparison of Elements -2 2.1 Plan and Organize 2.2 Monitor & Control 2.3 Integrate Disciplines 2.4 Coordinate w/ Supp. 2.5 Manage Risk 2.6 Manage Data 2.7 Manage Configurations 2.8 Ensure Quality Project Planning Project Monitor & Control Integrated Project Mgt Supplier Agreement Mgt Risk Management Quantitative Project Mgt Support Process Areas Configuration Mgt Proc & Prod QA Measurement & Analysis Causal Analysis and Resolution Decision Analysis & Resolution SECM Management Focus Areas CMMI Project Management Process Areas 1.4
  • Slide 94
  • CMMI Tutorial Apr 22, 2003 94 Comparison of Elements -3 SECM Environment Focus Areas Organizational Process Focus Organizational Process Definition Organizational Training Organizational Process Performance Organizational Innovation & Deployment 3.1 Define & Improve SE Process 3.2 Manage Competency 3.3 Manage Technology 3.4 Manage SE Support Environment CMMI Process Management Process Areas
  • Slide 95
  • CMMI Tutorial Apr 22, 2003 95 Comparison of Generic Elements CMMI Capability Level 2 SECM Capability Level 2 2.1 Follow recorded & approved plans & processes 2.2 Verify compliance & take action when needed 2.1 Establish org policy 2.2 Plan the process 2.3 Provide resources 2.4 Assign responsibilities 2.5 Train people 2.6 Manage configurations 2.7 Identify & involve relevant stakeholders 2.8 Monitor & control process 2.9 Objectively evaluate adherence 2.10 Review status w/ higher-level mgmt
  • Slide 96
  • CMMI Tutorial Apr 22, 2003 96 CMMI Capability Level 3 SECM Capability Level 3 3.1 Standardize & record a well-defined proc 3.2 Tailor the standard proc using standard guidelines 3.3 Implement & improve the FA activities 3.4 Improve the standard process 3.1 Establish a defined process 3.2 Collect improvement information Comparison of Generic Elements -3
  • Slide 97
  • CMMI Tutorial Apr 22, 2003 97 Comparison of Generic Elements -4 CMMI Capability Level 4 SECM Capability Level 4 4.1 Collect & analyze metrics 4.2 Take appropriate action to align performance & expectations 4.1 Establish quantitative objectives for the process 4.2 Stabilize subprocess performance
  • Slide 98
  • CMMI Tutorial Apr 22, 2003 98 Comparison of Generic Elements -5 CMMI Capability Level 5 SECM Capability Level 5 5.1 Identify FA activities for which it is appropriate to quantify process repeatability 5.2 Establish quantitative goals for improving the standard process 5.3 Improve the std proc based on data & metrics 5.4 Perform causal analysis & eliminate causes of variation by changing the standard process 5.1 Ensure continuous process improvement 5.2 Correct root causes of problems
  • Slide 99
  • CMMI Tutorial Apr 22, 2003 99 Conclusions EIA/IS 731 users should be able to smoothly transition to the CMMI-SE/SW model Continuous representation (+ equivalent staged representation) Some lower-level differences Application of common SE/SW practices to product development community
  • Slide 100
  • CMMI Tutorial Apr 22, 2003 100 Overview of CMMI SM SE/SW/IPPD/SS Model Process Areas
  • Slide 101
  • CMMI Tutorial Apr 22, 2003 101 Requirements Management Requirements Development Technical Solution Product Integration Verification Validation Engineering Project Management Project Planning Project Monitoring and Control Supplier Agreement Management Integrated Project Management(IPPD) Integrated Supplier Management (SS) Integrated Teaming (IPPD) Risk Management Quantitative Project Management Organizational Process Focus Organizational Process Definition Organizational Training Organizational Process Performance Organizational Innovation and Deployment Process Management Configuration Management Process and Product Quality Assurance Measurement and Analysis Causal Analysis and Resolution Decision Analysis and Resolution Organizational Environment for Integration (IPPD) Support Continuous Organization of PAs Category Process Area
  • Slide 102
  • CMMI Tutorial Apr 22, 2003 102 Project Management Process Areas There are eight Project Management Process Areas. Project Planning Project Monitoring and Control Supplier Agreement Management Integrated Project Management Integrated Supplier Management (SS) Risk Management Quantitative Project Management Integrated Teaming (IT) and IPM(IPPD) will be discussed with IPPD.
  • Slide 103
  • CMMI Tutorial Apr 22, 2003 103 Basic Project Management PAs PP What To Build What To Do SAM PMC What To Monitor Replan Plans Status, issues, results of progress and milestone reviews Product component requirements Technical issues Completed product components Acceptance reviews and tests Engineering and Support process areas Status, issues, results of process and product evaluations; measures and analyses Commitments Measurement needs Corrective action Supplier Supplier agreement Corrective action
  • Slide 104
  • CMMI Tutorial Apr 22, 2003 104 Project Planning Purpose: Establish and maintain plans that define project activities.
  • Slide 105
  • CMMI Tutorial Apr 22, 2003 105 Project Planning - Context Planning Data Establish Estimates Obtain Commitment to the Plan Develop a Project Plan Project Plans PMC
  • Slide 106
  • CMMI Tutorial Apr 22, 2003 106 Project Planning - Context Determine Estimates of Effort and Cost Planning Data Establish Estimates Estimate the Scope of the Project Establish Estimates of Work Product and Task Attributes Define Project Life Cycle
  • Slide 107
  • CMMI Tutorial Apr 22, 2003 107 Project Planning - Context Establish the Budget and Schedule Planning Data Develop a Project Plan Plan for Data Management Plan Stakeholder Involvement Plan for Project Resources Project Plans Establish the Project Plan Identify Project Risks Plan for Needed Knowledge and Skills
  • Slide 108
  • CMMI Tutorial Apr 22, 2003 108 Project Planning - Context Obtain Commitment to the Plan Reconcile Work and Resource Levels Project Plans Review Plans that Affect the Project Obtain Plan Commitment
  • Slide 109
  • CMMI Tutorial Apr 22, 2003 109 Project Monitoring and Control Purpose: Provide understanding into the projects progress so that appropriate corrective actions can be taken when the projects performance deviates significantly from the plan.
  • Slide 110
  • CMMI Tutorial Apr 22, 2003 110 Project Monitoring and Control - Context Project Plans Monitor Project Risks Monitor Commitments Analyze Issues Take Corrective Actions Conduct Milestone Reviews Monitor Data Management Monitor Project Planning Parameters Manage Corrective Actions to Closure Monitor Project Against Plans Conduct progress Reviews Monitor Stakeholder Involvement Manage Corrective Actions PP
  • Slide 111
  • CMMI Tutorial Apr 22, 2003 111 Supplier Agreement Management Purpose: Manage the acquisition of products from suppliers for which there exists a formal agreement.
  • Slide 112
  • CMMI Tutorial Apr 22, 2003 112 Supplier Agreement Management Context Product List of Products Establish Supplier Agreements Supplier Agreement Review COTS Products Determine Acquisition Type Transition Products Accept the Acquired Product Select Suppliers Supplier Requirements Execute the Supplier Agreement Establish Supplier Agreements Satisfy Supplier Agreements
  • Slide 113
  • CMMI Tutorial Apr 22, 2003 113 Coordination & collaboration; Shared vision & IT structure subprocesses for quantitative mgmt. Advanced Project Management PAs Process Performance Objectives, Baselines, Models QPM Organizations Std. Processes IPM RSKM Lessons Learned, Performance Data Projects Defined Process Statistical Mgmt Data Risk Taxonomies & Parameters, Status, Mitigation, and Corrective Action Process Management process areas Basic Project Management process areas Risk exposure due to unstable processes Identified risks Engineering & Support process areas Coordination, commitments, issues; Product Architecture for Structuring Teams IT IT mgmt for engineering processes; Integrated work environment people & practices
  • Slide 114
  • CMMI Tutorial Apr 22, 2003 114 Integrated Project Management Purpose: Establish and manage the project and the involvement of the relevant stakeholders according to an integrated and defined process that is tailored from the organizations set of standard processes.
  • Slide 115
  • CMMI Tutorial Apr 22, 2003 115 Integrated Project Management - Context Manage Stakeholder Involvement Manage Dependencies Resolve Coordination Issues Coordinate with Relevant Stakeholders Documented Technical Issues Documented Critical Dependencies Agendas and Schedules for Collaborative Activities Use the Projects Defined Process Defined Process Based Project Plan Projects Defined Process Use Org Proc Assets for Planning Project Activities Integrate Plans OPD Estimates and Measures Documentation Lessons Learned Other Project & Org Functions Establish the Projects Defined Process Contribute to Org Process Assets Manage Project Using Integrated Plans
  • Slide 116
  • CMMI Tutorial Apr 22, 2003 116 Integrated Supplier Management Purpose: Proactively identify sources of products that may be used to satisfy the projects requirements and to manage selected suppliers while maintaining a cooperative project-supplier relationship.
  • Slide 117
  • CMMI Tutorial Apr 22, 2003 117 Integrated Supplier Management - Context Monitor Selected Supplier Processes Analyze Potential Sources of Products Revise the Supplier Agreement or Relationship Evaluate and Determine Sources of Products Supplier Processes Evaluate Selected Supplier Work Products Analyze and Select Sources of Products Coordinate Work with Suppliers SAM Supplier Work Products
  • Slide 118
  • CMMI Tutorial Apr 22, 2003 118 Risk Management Purpose: Identify potential problems before they occur, so that risk handling activities may be planned and invoked as needed across the life of the product or project to mitigate adverse impacts on achieving objectives.
  • Slide 119
  • CMMI Tutorial Apr 22, 2003 119 Risk Management - Context Identify Risks Evaluate, Categorize, and Prioritize Risks Identify and Analyze Risks From Project Planning and Project Monitoring and Control Develop Risk Mitigation Plans Implement Risk Mitigation Plans Mitigate Risks DAR Risk Repository Determine Risk Sources and Categories Define Risk Parameters Prepare for Risk Management Establish a Risk Management Strategy
  • Slide 120
  • CMMI Tutorial Apr 22, 2003 120 Quantitative Project Management Purpose: Quantitatively manage the projects defined process to achieve the projects established quality and process-performance objectives.
  • Slide 121
  • CMMI Tutorial Apr 22, 2003 121 Quantitative Project Management - Context Definitions of Measures; Derived Objectives Subprocesse Capability Measure Statistically Manage Subprocess Performance Record Statistical Management Data Monitor Performance of Selected Subprocesses Apply Statistical Methods to Understand Variation Select Measures and Analytic Techniques Stable Sub- processes Selected Subprocesses OPP Predictions of Quality and Process Performance Organization Measurement Repository Establish Projects Objectives Compose the Defined Process Quality and Process Performance Objectives Remedial Actions Select the Subprocesses that will be Statistically Managed Quantitatively Manage the Project Manage Project Performance Projects Defined Process
  • Slide 122
  • CMMI Tutorial Apr 22, 2003 122 Summary Project Planning Project Monitoring and Control Supplier Agreement Management Risk Management Integrated Project Management Integrated Supplier Management (SS) Quantitative Project Management Special Note: Integrated Teaming (IT) and IPM(IPPD) will be discussed with IPPD.
  • Slide 123
  • CMMI Tutorial Apr 22, 2003 123 Support Process Areas There are six Support Process Areas: Configuration Management Process and Product Quality Assurance Measurement and Analysis Causal Analysis and Resolution Decision Analysis and Resolution Organizational Environment for Integration will be discussed with IPPD.
  • Slide 124
  • CMMI Tutorial Apr 22, 2003 124 Understanding Support Processes Support process areas cover the practices that support product development, maintenance, and acquisition. They provide essential processes used by all the CMMI process areas, and are typically used in the context of performing other processes.
  • Slide 125
  • CMMI Tutorial Apr 22, 2003 125 Basic Support Process Areas PPQA MA CM All process areas Measurements, analyses Information needs Configuration items; change requests Baselines; audit reports Processes and work products; standards and procedures Quality and noncompliance issues
  • Slide 126
  • CMMI Tutorial Apr 22, 2003 126 Configuration Management Purpose: Establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.
  • Slide 127
  • CMMI Tutorial Apr 22, 2003 127 Configuration Management - Context Establish Config Mgmt Records Perform Configuration Audits Action Items Audit Results Status Establish Integrity Change Request Database Configuration Management System Change Requests Create or Release Baselines Establish a Config. Management System Identify Configuration Items Establish Baselines Control Configuration Items Track Change Requests Track and Control Changes
  • Slide 128
  • CMMI Tutorial Apr 22, 2003 128 Process and Product Quality Assurance Purpose: Provide staff and management with objective insight into processes and associated work products.
  • Slide 129
  • CMMI Tutorial Apr 22, 2003 129 Process and Product Quality Assurance - Context Work Products Reports and Records Objectively Evaluate Processes Objectively Evaluate Work Products & Services Objectively Evaluate Processes and Work Products Establish Records Communicate and Ensure Resolution of Non-compliance Issues Provide Objective Insight
  • Slide 130
  • CMMI Tutorial Apr 22, 2003 130 Measurement and Analysis Purpose: Develop and sustain a measurement capability that is used to support management information needs.
  • Slide 131
  • CMMI Tutorial Apr 22, 2003 131 Measurement & Analysis - Context Measurement Indicators Collect Measurement Data Communicate Results Store Data & Results Analyze Measurement Data Provide Measurement Results Measurement Personnel Measurement Repository Measurement Objectives Procedures, Tools Specify Measures Establish Measurement Objectives Specify Analysis Procedures Specify Data Collection and Storage Procedures Align Measurement Analysis Activities
  • Slide 132
  • Advanced Support Process Areas DAR All process areas CAR Defects & other problems Selected issues; Process improvement proposals; Structured decisions OEI Process Management PAs Project Management PAs Ability to develop & deploy IPPD processes & supporting assets; IPPD knowledge & skill needs Integrated work environment & people practices Organization IPPD Infrastructure
  • Slide 133
  • CMMI Tutorial Apr 22, 2003 133 Causal Analysis and Resolution Purpose: Identify causes of defects and other problems and take action to prevent them from occurring in the future.
  • Slide 134
  • CMMI Tutorial Apr 22, 2003 134 Causal Analysis and Resolution - Context Select Data for Analysis Analyze Causes Defect & Problem Data Determine Causes of Defects Implement Action Proposals Evaluate Effect of Changes Record Data Action Proposal Action Plans CAR Records Performance Measures Address Causes of Defects
  • Slide 135
  • CMMI Tutorial Apr 22, 2003 135 Decision Analysis and Resolution Purpose: Analyze possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria.
  • Slide 136
  • CMMI Tutorial Apr 22, 2003 136 Decision Analysis and Resolution Applicability: The project should document guidelines for when a structured decision analysis process is to be used. DAR should be applied where significant technical, cost, or schedule risks evolve.
  • Slide 137
  • CMMI Tutorial Apr 22, 2003 137 Decision Analysis and Resolution -Context Establish Guidelines for Decision Analysis Guidelines Evaluate Alternatives Select Evaluation Methods Methods Criteria Establish Evaluation Criteria Select Solutions Identify Alternative Solutions Proposed Alternatives Evaluate Alternatives Other PAs
  • Slide 138
  • CMMI Tutorial Apr 22, 2003 138 Engineering Process Areas There are six Engineering Process Areas. Requirements Management Requirements Development Technical Solution Product Integration Verification Validation
  • Slide 139
  • CMMI Tutorial Apr 22, 2003 139 Engineering Process Areas RD PI Val Customer TS Ver REQM Requirements Customer needs Product & product component requirements Product components, work products, verification and validation reports Product components Alternative solutions Require- ments Product
  • Slide 140
  • CMMI Tutorial Apr 22, 2003 140 Requirements Management Purpose: Manage the requirements of the projects product and product components and identify inconsistencies between those requirements and the projects plans and work products.
  • Slide 141
  • CMMI Tutorial Apr 22, 2003 141 Requirements Management Context Requirements Obtain an Understanding of Requirements CL2 Obtain Commitment to Requirements Identify Inconsistencies between Project Work and Reqmts Traceability Hierarchy CL2 Maintain Bi-directional Requirements Traceability Manage Requirements Manage Requirements Changes
  • Slide 142
  • CMMI Tutorial Apr 22, 2003 142 Requirements Development Purpose: Produce and analyze customer, product, and product component requirements.
  • Slide 143
  • CMMI Tutorial Apr 22, 2003 143 Requirements Development - Context Develop Customer Requirements Product Requirements Develop Product Requirements Analyze and Validate Requirements Validated Requirements
  • Slide 144
  • CMMI Tutorial Apr 22, 2003 144 Develop the Customer Requirements Requirements Development Context Customer Requirements Develop Customer Requirements Collect Stakeholder Needs CL2 Elicit Needs
  • Slide 145
  • CMMI Tutorial Apr 22, 2003 145 Establish Product & Product Component Requirements Product Requirements Develop Product Requirements Allocate Product and Product- Component Requirements Identify Interface Requirements Customer Requirements Requirements Development Context
  • Slide 146
  • CMMI Tutorial Apr 22, 2003 146 Establish Operational Concepts & Scenarios Establish a Definition of Required Functionality CL3 Analyze Requirements to Achieve Balance Analyze Requirements Product Requirements Validated Requirements Analyze and Validate Requirements Validate Requirements CL2 Validate Requirements with Comprehensive Methods Requirements Development Context
  • Slide 147
  • CMMI Tutorial Apr 22, 2003 147 Technical Solution Purpose: Design, develop, and implement solutions to requirements. Solutions, designs and implementations encompass products, product components, and product related life-cycle processes either singly or in combinations as appropriate.
  • Slide 148
  • CMMI Tutorial Apr 22, 2003 148 Select Product- Component Solutions Technical Solution - Context Validated Requirements Design Detail & Documentation Delivered Product Develop the Design Implement the Product Design Alternative Designs and Evaluation Criteria
  • Slide 149
  • CMMI Tutorial Apr 22, 2003 149 Validated Requirements Develop Alternative Solutions and Selection Criteria Select Product Component Solutions CL 2 Develop Detailed Solutions and Selection Criteria Alternative Solutions Selection Criteria New Technology Evaluations Select Product Component Solutions Selection Decisions Compliance w/ Reqmts DAR CL 2 Evolve Operational Concepts & Scenarios Operational Scenarios Timeline Analysis Use Cases Technical Solution - Context
  • Slide 150
  • CMMI Tutorial Apr 22, 2003 150 Technical Solution - Context Design the Product or Product Component Develop the Design Establish a Tech Data Package Tech Data Package Establish Interface Descriptions CL 3 Design Interfaces Using Criteria I/F Design Documentation I/F Specification I/F Control Documents Perform Make, Buy, or Reuse Analyses Selection Criteria Make/Buy Analysis Design Methods Design Tools Design Processes
  • Slide 151
  • CMMI Tutorial Apr 22, 2003 151 Technical Solution - Context Parts Fabricated Software Coded Data Documented Processes Documented Facilities Constructed Implement The Design Implement the Product Design Develop Product Support Documentation Training Manuals Users Manual Operators Manual Maintenance Manual On-line Help
  • Slide 152
  • CMMI Tutorial Apr 22, 2003 152 Product Integration Purpose: Assemble the product from the product components, ensure the product, as integrated, functions properly and deliver the product.
  • Slide 153
  • CMMI Tutorial Apr 22, 2003 153 Product Integration - Context Assemble Product Components and Deliver the Product Integration Plan Prepare for Product Integration Technical Solution DAR Ensure Interface Compatibility Assemblies Sub- assemblies
  • Slide 154
  • CMMI Tutorial Apr 22, 2003 154 Integration Plan - Integration Resources - Integration Procedures - Interface Data Prepare for Product Integration Decision Analysis & Resolution Technical Solution Determine Integration Sequence CL3 Establish Product Integration Procedures and Criteria CL2 Establish the Product Integration Environment Product Integration - Context
  • Slide 155
  • CMMI Tutorial Apr 22, 2003 155 Integration Plan - Integration Resources - Integration Procedures - Interface Data Ensure Interface Compatibility Technical Solution Review Interface Descriptions for Completeness Manage Interfaces Product Integration - Context
  • Slide 156
  • CMMI Tutorial Apr 22, 2003 156 Assemble Product Components and Deliver Product Technical Solution Confirm Readiness of Components for Integration Assemble Product Components Evaluate Assembled Product Components Package And Deliver the Product or Product Component Integration Plan - Integration Resources - Integration Procedures - Interface Data Product Integration - Context
  • Slide 157
  • CMMI Tutorial Apr 22, 2003 157 Verification versus Validation Verification Did you build the product right? That is, did you meet the requirements specification? Validation Did you build the right product? That is, did you meet the operational need?
  • Slide 158
  • CMMI Tutorial Apr 22, 2003 158 Verification Purpose: Ensure that selected work products meet their specified requirements.
  • Slide 159
  • CMMI Tutorial Apr 22, 2003 159 Verification - Context Verification Plan Prepare for Verification Corrective Actions Verify Selected Work Products Perform Peer Reviews
  • Slide 160
  • CMMI Tutorial Apr 22, 2003 160 Verification - Context Select Work Products for Verification Requirements, Methods, Processes, Evaluation Criteria Prepare for Verification CL2 Establish the Verification Environment Verification Plan - Verification Resources - Verification Procedures Technical Solution CL3 Establish Verification Procedures and Criteria
  • Slide 161
  • CMMI Tutorial Apr 22, 2003 161 Verification - Context Prepare For Peer Reviews Requirement for Data Collection Entry and Exit Criteria Peer Review Plan Review Results Review Issues Review Data Action Items Conduct Peer Reviews Perform Peer Reviews CL 2 Analyze Peer Review Data
  • Slide 162
  • CMMI Tutorial Apr 22, 2003 162 Verification - Context Verification Results Deficiencies Verification Data Corrective Actions Verify Selected Work Products Perform Verification CL2 Analyze Verification Results and Identify Corrective Actions
  • Slide 163
  • CMMI Tutorial Apr 22, 2003 163 Validation Purpose: Demonstrate that a product or product component fulfills its intended use when placed in its intended environment.
  • Slide 164
  • CMMI Tutorial Apr 22, 2003 164 Validation - Context - Customer Requirements - Product Requirements - Products - Validation Requirements Prepare for Validation - Requirements Validation Plan - Product Validation Plan - Process and Support Needs Validate Product or Product Components - Conformance - Deficiencies
  • Slide 165
  • CMMI Tutorial Apr 22, 2003 165 Validation - Context Select Products For Validation - Validation Plan - Support Needs - Environment Needs - Resources - Test Case Scenario - Validation Procedures Prepare for Validation CL3 Establish Validation Procedures and Criteria CL2 Establish the Validation Environment Requirements
  • Slide 166
  • CMMI Tutorial Apr 22, 2003 166 Validation - Context Validate Product or Product Components Perform Validation Validation Reports Validation Results Cross Reference Matrix As run procedures log Operational Demonstrations Analyze Validation Results Validation Deficiency Reports Validation Issues Procedure Change Request
  • Slide 167
  • CMMI Tutorial Apr 22, 2003 167 Process Management Process Areas There are six Process Management Process Areas: Organizational Process Focus Organizational Process Definition Organizational Training Organizational Process Performance Organizational Innovation and Deployment Organizational Environment for Integration will be covered with IPPD
  • Slide 168
  • CMMI Tutorial Apr 22, 2003 168 Understanding Process Management Process Areas The process management PAs apply across the organization as a whole and provide details that support the Capability Level 3 Generic Goal. For selected PAs, the organization has standard processes, which individual projects tailor to their needs.
  • Slide 169
  • CMMI Tutorial Apr 22, 2003 169 Process Management PAs can capitalize on project level stability provided by PAs that are institutionalized at CL 2. (i.e., policy, planning, resources, responsibility, training, performing the process, managing configurations, monitoring and controlling, objective verification, management review) Understanding Process Management Process Areas
  • Slide 170
  • CMMI Tutorial Apr 22, 2003 170 Basic Process Management PAs OPF OPD Resources and Coordination OT Std Process and Other Assets Training for Projects and Support Groups in Std Process and Assets Organizations process needs and objectives Std Process and Other Assets Senior Management Organizations business objectives Project Management, Support, and Engineering process areas Training needs Improvement information (e.g., lessons learned, data, artifacts) Process Improvement Proposals; Participation in defining, assessing, and deploying processes
  • Slide 171
  • CMMI Tutorial Apr 22, 2003 171 Organizational Process Focus Purpose: Plan and implement organizational process improvement based on a thorough understanding of the current strengths and weaknesses of the organizations processes and process assets.
  • Slide 172
  • CMMI Tutorial Apr 22, 2003 172 Selected Improvements Improvement Initiatives Pilots, Action Teams Organizational Process Focus - Context Findings & Ratings Appraise Orgs Processes Identify Org.s Process Improve- ments Establish Organizational Process Needs Process Needs and Objectives Determine Process Improvement Opportunities Establish Process Action Plans Implement Process Action Plans Process Action plans Deployable Process Assets (Revised) Process Assets Incorporate Process- Related Experiences Process Experiences Deploy Organizational Process Assets Plan and Implement Process Improve- ment Activities
  • Slide 173
  • CMMI Tutorial Apr 22, 2003 173 Purpose: Establish and maintain a usable set of organizational process assets. Organizational Process Definition
  • Slide 174
  • CMMI Tutorial Apr 22, 2003 174 Establish the Organizations Measurement Repository Establish the Organizations Process Asset Library Organizational Process Definition - Context Process Implementers Establish Tailoring Criteria and Guidelines Establish Life-Cycle Model Descriptions Establish Standard Processes Establish Organizational Process Assets Life Cycle Models Organizational Standard Processes Organizational Library of Process Documentation Organizational Measurement Repository Improvements OPF Deploy- ment Tailoring Guidelines
  • Slide 175
  • CMMI Tutorial Apr 22, 2003 175 Organizational Training Purpose: Develop the skills and knowledge of people so they can perform their roles effectively and efficiently.
  • Slide 176
  • CMMI Tutorial Apr 22, 2003 176 Organizational Training - Context Deliver Training Materials Records Change Requests Assess Training Effectiveness Establish Training Records Surveys Records Provide Necessary Training Establish the Strategic Training Needs Analysis Needs Strategy Reqmts Determine which Training Needs are the Responsibility of the Org. Materials Training Repository Establish an Organizational Training Capability Establish Training Capability Establish an Organizational Training Tactical Plan
  • Slide 177
  • CMMI Tutorial Apr 22, 2003 177 Senior Management OPP Progress toward achieving business objectives OID Quality and process performance objectives, measures, baselines, models Cost and benefit data from piloted improvements Quality and process performance objectives, measures, baselines, models Process performance and capability data Basic Set of Process Management Process Areas Project Management, Support, and Engineering process areas Ability to develop and deploy process and supporting assets Organization Improvements Common measures Advanced Process Management Process Areas
  • Slide 178
  • CMMI Tutorial Apr 22, 2003 178 Organizational Process Performance Purpose: Establish and maintain a quantitative understanding of the performance of the organizations set of standard processes in support of quality and process-performance objectives, and to provide the process performance data, baselines, and models to quantitatively manage the organizations projects.
  • Slide 179
  • CMMI Tutorial Apr 22, 2003 179 Organizational Process Performance - Context Establish Quality and Process Performance Measures Organizational Process Performance Baselines Process Performance Models Organizations Standard Processes Project Process Measurements Select Processes Selected Subprocesses from Org. Std. Processes Business Objectives Organizational Process Performance Objectives Establish Process Performance Models Establish Process Performance Objectives Establish Process Performance Baselines Org set of measures QPM Business Objectives Establish Performance Baselines and Models MA
  • Slide 180
  • CMMI Tutorial Apr 22, 2003 180 Organizational Innovation and Deployment Purpose: Select and deploy incremental and innovative improvements that measurably improve the organizations processes and technologies. The improvements support the organizations quality and process-performance objectives as derived from the organizations business objectives.
  • Slide 181
  • CMMI Tutorial Apr 22, 2003 181 Manage the Deployment Measure Improvements Effects Plan the Deployment Deploy Improvements Organizational Innovation and Deployment - Context Collect and Analyze Improvement Proposals Measurement Results Pilot Improvements Improvement Proposals and Analysis Select Improvements for Deployment Improvements Select Improvements Identify and Analyze Innovations
  • Slide 182
  • CMMI Tutorial Apr 22, 2003 182 Overview of Integrated Product and Process Development IPPD
  • Slide 183
  • CMMI Tutorial Apr 22, 2003 183 About IPPD IPPD affects all process areas. IPPD is not a discipline like SE or SW. Rather, it is a way of doing business. IPPD is employed in conjunction with the CMMI disciplines (software and systems engineering). Implementation of IPPD shapes how you perform the work in these disciplines.
  • Slide 184
  • CMMI Tutorial Apr 22, 2003 184 IPPD - Definition IPPD provides a systematic approach to product development that achieves a timely collaboration of relevant stakeholders throughout the product life cycle to better satisfy customer needs.
  • Slide 185
  • CMMI Tutorial Apr 22, 2003 185 IPPD - Definition -2 Integration of the development of product- related processes (e.g., manufacturing, support, training, disposal) during product development is embedded in SE/SW specific practices by involving relevant stakeholders from all life cycle phases and by the concept of work product.
  • Slide 186
  • CMMI Tutorial Apr 22, 2003 186 Stakeholder Involvement Stakeholder Involvement is guided and assured by three constructs in CMMI- SE/SW/IPPD: GP 2.7 Identify and involve the relevant stakeholders of the process as planned. PP SP 2.6-1 Plan the involvement of identified stakeholders. IPM SG 2 Collaborate and coordinate with relevant stakeholders.
  • Slide 187
  • CMMI Tutorial Apr 22, 2003 187 CMMI Work Product - Definition Any artifact produced by a process. This may include files, documents, parts of the product, services, processes, specifications, and invoices. Examples of processes as work product include a manufacturing process, a training process, and a disposal process. A key distinction between a work product and a product component is that a work product need not be engineered (although it may be).
  • Slide 188
  • CMMI Tutorial Apr 22, 2003 188 IPPD in CMMI Models Then, what makes IPPD different from pure SE/SW implementations? IPPD relies on integrated teams to develop the product and processes. IPPD provides an integrated work environment and the management of people to incentivize teamwork. Processes are tailored to be used by integrated teams.
  • Slide 189
  • CMMI Tutorial Apr 22, 2003 189 CMMI Integrated Team Definition An integrated team is comprised of people with complementary skills and expertise appropriate skills and advocacy fully empowered to represent stakeholders from all phases of the work products life cycle These people are committed to and are collectively responsible for delivering specified work products through timely collaboration
  • Slide 190
  • CMMI Tutorial Apr 22, 2003 190 Scope of IPPD CMMI SE/SW/IPPD adds to CMMI-SE/SW: Two new process areas Organizational Environment for Integration Integrated Teaming A revised Integrated Project Management (IPPD) process area IPPD amplifications and references New glossary definitions and acronyms Overview material
  • Slide 191
  • CMMI Tutorial Apr 22, 2003 191 Organizational Environment for Integration (OEI) Purpose: To provide an Integrated Product and Process Development (IPPD) infrastructure and manage people for integration.
  • Slide 192
  • CMMI Tutorial Apr 22, 2003 192 Provide IPPD Infrastructure IPPD-Enabled People and Work Environments Manage People for Integration Mechanisms and Incentives to Support Integration and Collaboration Organizational Environment for Integration (OEI)- Context
  • Slide 193
  • CMMI Tutorial Apr 22, 2003 193 Organizational Environment for Integration Context Guidelines for Leadership, Decision-making Context Manage People for Integration Establish Leadership Mechanisms Establish Incentives for Integration Establish Mechanisms to Balance Responsi- bilities Guidelines for Empowerment Process for Issue Resolution Team & Individual Rewards Organizational Guidelines Joint Performance Review Process Organizations Shared Vision Establish an Integrated Work Environ- ment Establish the Organizations Shared Vision Provide IPPD Infrastructure Integrated Work Environment Identify IPPD-Unique Skill Require- ments Guidelines for Shared Vision Building IPPD Tactical & Strategic Training Needs OPD OT
  • Slide 194
  • CMMI Tutorial Apr 22, 2003 194 Integrated Project Management For IPPD Purpose: Establish and manage the project and the involvement of the relevant stakeholders according to an integrated and defined process that is tailored from the organizations set of standard processes. For Integrated Product and Process Development, Integrated Project Management also covers the establishment of a a shared vision for the project and an integrated team structure that will carry out the objectives of the project.
  • Slide 195
  • CMMI Tutorial Apr 22, 2003 195 Integrated Project Management (IPPD) - Context Use the Projects Defined Process Coordinate and Collaborate with Relevant Stakeholders Product Requirements Defined Process Based Project Plan Contributions to Organizations Process Assets Use the Projects Shared Vision for IPPD Projects Shared Vision Stakeholders Project Planning Organize Integrated Teams for IPPD Integrated Teams Organizational Environment for Integration
  • Slide 196
  • CMMI Tutorial Apr 22, 2003 196 Work Breakdown Structure Integrated Teams Integrated Project Management (IPPD) Responsibility & Requirements Allocation Info on Org/Project Situation Organize Integrated Teams for IPPD Use the Projects Shared Vision for IPPD Define the Projects Shared Vision Context Establish the Projects Shared Vision OEI Projects Shared Vision Determine Team Structure Develop a Preliminary Distribution of Requirements Establish Integrated Teams Team Structure Member Aspirations List of Teams Integrated Teaming
  • Slide 197
  • CMMI Tutorial Apr 22, 2003 197 Integrated Teaming Purpose: To form and sustain an integrated team for the development of work products.
  • Slide 198
  • CMMI Tutorial Apr 22, 2003 198 Integrated Teaming - Context Establish Team Composition Govern Team Operation Relevant Stakeholders Sponsors Objectives Assigned Product Requirements Integrated Team Project Planning Plans and Commitments Organizational Environment for Integration (IPPD) OEI PP IPM
  • Slide 199
  • CMMI Tutorial Apr 22, 2003 199 Identify Team Tasks Establish Team Composition Results Lists Identify Knowledge and Skills Functions, Skills, & Expertise Lists Assign Appropriate Team Members Integrated Team Stakeholders Assigned Product Requirements Govern Team Operation Establish a Shared Vision Team Charter Establish a Team Charter Assignments, & Respon- sibilities Define Roles & Respon- sibilities Ground Rules and Procedures Establish Operating Procedures Collaborate among Interfacing Teams Plans and Commitments Teams Shared Vision Sponsors Objectives Integrated Teaming - Context Task Descriptions
  • Slide 200
  • CMMI Tutorial Apr 22, 2003 Training and Appraisals
  • Slide 201
  • CMMI Tutorial Apr 22, 2003 201 Introduction to the CMMI Course, Staged & Continuous (Separate Courses) Introduction course will enable the participant to Understand the importance of defined processes Understand the rationale for process improvement Comprehend the CMMI model Identify ways of applying the CMMI model for process improvement Broad audience Systems and software developers Systems, Program and software managers Practitioners of disciplines that support systems and software Government and industry acquirers of software-intensive systems Assumes one year of experience in systems and software No process improvement or Capability Maturity Model (CMM ) experience assumed
  • Slide 202
  • CMMI Tutorial Apr 22, 2003 202 Intermediate Concepts of CMMI Models Course Provides a deeper understanding of the CMMI and its fundamental concepts. PAs in more detail Linking the PAs together Interpreting the CMMI for appraisals Application of CMMI for process improvement Required as a prerequisite to SCAMPI Lead Appraiser training and train the trainer course.
  • Slide 203
  • CMMI Tutorial Apr 22, 2003 203 Similar to the current CMM Appraisal Framework (CAF) V1.0 A guide to appraisal method developers Specifies the requirements for classes of appraisal methods Class A: Full, comprehensive appraisal methods Class B: Initial, incremental, self-appraisals Class C: Quick-look Method developers can declare which class their method fits Implications of the desired class of appraisal Appraisal Requirements for CMMI (ARC) v1.1
  • Slide 204
  • CMMI Tutorial Apr 22, 2003 204 Standard CMMI Appraisal Method for Process Improvement (SCAMPI) Similar to CBA IPI method Led by authorized Lead Appraiser Tailorable to organization and model scope Source selection appraisals or process monitoring are tailoring options of SCAMPI SCAMPI Method Definition Document V1.1
  • Slide 205
  • CMMI Tutorial Apr 22, 2003 205 Similar to existing SEI Lead Assessor and Lead Evaluator programs To be administered by SEI Will transition current SW & SE Lead Assessors or Evaluators, as well as new candidates Lead Appraiser requirements: Introduction to CMMI Training Appraisal team experience Intermediate CMMI Training SCAMPI Lead Appraiser Training CMMI Lead Appraiser Program
  • Slide 206
  • CMMI Tutorial Apr 22, 2003 206 Expectations The method has been simplified, but CMMI models have more process areas and more practices than the individual SE and SW models More of the organization may be covered The achievable goal: Assuming an organization of 3-6 projects, 6-9 team members, experienced Lead Appraiser SCAMPI appraisals of process areas through Levels 3 in 100 hours or less
  • Slide 207
  • CMMI Tutorial Apr 22, 2003 207 Pilot Results Six SCAMPIs performed against V1.02 models: 2 government, 4 industry All explored continuous representation Each appraisal was characterized by: 6-12 assessment team members 2-4 projects 15-21 interviews Total on-site hours ranged from 85-137 hours All went beyond SE/SW Equivalent hours: 77-120; median 92
  • Slide 208
  • CMMI Tutorial Apr 22, 2003 208 Discoveries in Use - 1 Appraisal time shows an excellent learning curve 40% reduction in appraisal time over five Australian assessments Shadow appraisals show ease of transition High maturity CBA IPI at Litton PRC TSP based Level 4 CBA IPI at China Lake Mappings and gap analyses confirm evolutionary expansion from predecessor models Government and contractors agree on CMMIs improved engineering coverage in contract monitoring
  • Slide 209
  • CMMI Tutorial Apr 22, 2003 Wrap-Up
  • Slide 210
  • CMMI Tutorial Apr 22, 2003 210 CMMI Transition Plan Development Phase Development of CMMI products Verification and validation of CMMI products Transition Phase Approval of initial CMMI products for public release Evidence of sufficient use Transition planning to help organizations use CMMI products Sustainment Phase Upkeep and continuous improvement of the product suite Additional evidence of adoption and use V1.0 Aug 2000 V1.1 Dec 2001 SW-CMM, EIA 731 phased out Dec 2003 V0.2 Aug 1999 Pilots
  • Slide 211
  • CMMI Tutorial Apr 22, 2003 211 DoD Expectations for CMMI CMMI will improve the maturity for the software intensive systems development and maintenance Integration of systems and software emphasis will focus programs on the essential engineering processes Gains already made in software will migrate to systems engineering CMMI will become the logical integrated successor for the SW-CMM for software engineering and EIA/IS 731 for systems engineering Simplifies the process of viewing the two disciplines Major companies have migration plans in place Support for pilot assessments across Government and Industry Transition Partners are being trained as CMMI Lead Appraisers Comments of Dr. Jack Ferguson, Director, Software Intensive Systems (OUSD (AT&L)) At STC, 2001
  • Slide 212
  • CMMI Tutorial Apr 22, 2003 212 DoD Expectations for CMMI (continued) CMMI will become the approved means of judging engineering maturity for procurements within two years Integrated appraisal method should minimize the impact on industry and Government during procurement evaluations OSD policy update to reference CMMI being considered New techniques for minimizing costs and schedule impacts during appraisals related to procurements will be considered and adopted Government participation in internal assessments Comments of Dr. Jack Ferguson, Director, Software Intensive Systems (OUSD (AT&L)) At STC, 2001
  • Slide 213
  • CMMI Tutorial Apr 22, 2003 213 CMMI Schedule Available now CMMI-SE/SW, V1.1 CMMI-SE/SW/IPPD, V1.1 CMMI-SE/SW/IPPD/SS, V1.1 SCAMPI Method Definition Document. V1.1 V1.1 model and method training December 2003 Sunset period for SW-CMM, EIA/IS 731 completed (no more public courses, new lead assessors) December 2005 SW-CMM Transition Partner licenses end
  • Slide 214
  • CMMI Tutorial Apr 22, 2003 214 CMMI What is coming next? Emphasis through 2003 is on CMMI adoption and transition from legacy models Quarterly transition workshops will complement an annual User Workshop and SEPG Conference Communities of Practice will be encouraged Course Instructors CMMI Appraisers Transition Teams Technical Notes and Special Reports will complement V1.1: Mapping CMMI with other standards and models Managing COTS integration Making attribute tradeoffs in design Allowing prototypical coverage for specific interests (e.g., safety, security, modeling and simulation)
  • Slide 215
  • CMMI Tutorial Apr 22, 2003 215 CMMI...Re-cap... Is not so different from the models with which we are familiar... Has 2 representations in a single model: Staged Continuous... Contains specific and generic goals that must be satisfied... Is directly related to our work: Not everything we do is just software engineering There is a lot of systems engineering and other
  • Slide 216
  • CMMI Tutorial Apr 22, 2003 216 For More Information About CMMI Go to CMMI Website http://sei.cmu.edu/cmmihttp://sei.cmu.edu/cmmi http://seir.sei.cmu.edu/seir/http://seir.sei.cmu.edu/seir/ http://jo.sei.cmu.edu/pub/english.cgi/0/323123http://jo.sei.cmu.edu/pub/english.cgi/0/323123 http://dtic.mil/ndia (first and second annual CMMI Conferences)http://dtic.mil/ndia http://www.faa.gov/aiohttp://www.faa.gov/aio Assistance for government organizations: SW-CMM v1.1 to CMMI v1.1 Mappings Software Technology Support Center OO-ALC/TI-3 7278 4 th Ave Hill AFB, UT 84056-5705 http://www.stsc.hill.af.mil