Agenda • Project History
• CMMI Structure
• Comparisons with SW-CMM v1.1, SE-CMM, and EIA/IS 731_
• Assessment Methodology
• Training
• Transition Timelines and Strategies
What is a CMM?
• Capability Maturity Model:
A reference model of mature practices in a specified discipline, used to assess a group’s 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
Commonly Used CMMs
What is the Problem?
• Different structures, formats, terms, ways of measuring maturity
• Causes confusion, especially when using more than one CMM
• Hard to integrate them in a combined improvement program
• Hard to use multiple models in supplier selection
The CMMI Project
• DoD sponsored collaboration
between industry, Government, academia • Over 100 people involved
•
• Federal Aviation Administration
• National Security Agency
• Software Engineering Institute
• ADP, Inc.
• AT&T Labs
• BAE
• Boeing
• Computer Sciences Corporation
• EER Systems
• Ericsson
• Ernst and Young
• General Dynamics
• Harris Corporation
• Honeywell
• KPMG
• Litton
• Lockheed Martin
• Motorola
• Northrop Grumman
• Pacific
• Q-Labs
• Raytheon
• Rockwell Collins
• Sverdrup Corporation
• Thomson CSF
• TRW
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)
• Combined System Engineering / Software Engineering model
– IPPD version being developed
• Can be applied to:
– Just the software engineering projects in an organization
– Just the system engineering project in an organization
– Both
CMMI Process Areas - Staged Representation
Common Features For Each Process Area
• Commitment to Perform includes practices that ensure the process is established and will endure.
– Establishing organizational policies and leadership.
• Ability to Perform includes practices that establish the necessary conditions for implementing the process completely.
– Resources, organizational structures, and training.
• Activities Performed includes practices that directly implement a process area.
– Developing plans and procedures, performing work, tracking work, and taking corrective actions as necessary.
• Directing Implementation includes measurement practices that are necessary to collect and analyze data related to the process.
– Insight into the performance of the process.
• Verification includes practices that ensure compliance with the process that has been established.
– Reviews and audits.
CMMI - Continuous Representation
Which Representation Should We Use?
• The staged and continuous representations are equivalent but expressed in different ways
– Equivalent staging defined
• Staged
– Specific Process Areas for each Maturity Level
– Guides incremental improvement by focusing attention on the next level’s Process Areas
• Continuous
– Each Process Area has Capability Levels
– Organizations must decide your own improvement path
» What level of capability is appropriate for each Process Area based on their business needs
• Generally, you should keep the representation you started with
– SW-CMM: staged; EIA 731: continuous
CMMI Model Components
• CMMI Models contain institutionalization (Generic) and implementation (Specific) parts:
• Front matter
• Process Areas that contain:
– Generic and Specific Goals
– Generic and Specific Practices
(in Common Features in staged representation) – Subpractices
– Notes
– Discipline-specific amplifications
• Glossary and model scoping guidelines
SW-CMM v1.1 vs. CMMI
Process Areas
SW-CMM v1.1 vs. CMMI
Common Features Common Features - Engineering CMMI Assessment Requirements (CAR)
• Similar to the current CMM Appraisal
Framework (CAF) V1.0 – A guide to assessment method developers
• Specifies the requirements for classes of
assessment methods – Class A: Full, comprehensive assessment methods
– Class B: Initial, incremental, self-assessments
– Class C: Quick-look
• Method developers can declare which class their method fits
• Method buyers will understand the implications of the method proposed
Standard CMMI Assessment Method for Process Improvement (SCAMPI)
• A Class A Method
• Similar to CBA IPI method
– Led by authorized Lead Assessor
– Tailorable to organization and
model scope – SEI will continue to compile results
• Rules of evidence have been expanded
• Products:
– SCAMPI Method Description
• In work
– Maturity questionnaire, work aids, templates
– Incorporation of SECM appraisal methods
– Reducing the cost of assessments
CMMI Lead Assessor Program
• Similar to existing SEI Lead Assessor
and Lead Evaluator programs – To be administered by SEI
• Will transition current SW & SE Lead Assessors
– Specific requirements, steps under discussion
• Lead Assessor requirements:
– Introduction to CMMI Training
– Assessment team experience
– Advanced CMMI Training
– SCAMPI Lead Assessor Training or
Upgrade Training (for current Lead Assessors) Expectations
• We have simplified the method, but…
– CMMI models have more process
areas and more practices than each of the individual source models • Our goal:
– Assuming an organization
of 3-6 projects, 6-9 team members, experienced Lead Assessor – SCAMPI assessment of all process areas through Levels 2-5 in 2-3 weeks
– SCAMPI assessment of process areas through Levels 3 in 1-2 weeks
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 and software managers
– Practitioners of disciplines that support systems and software
– Government and industry acquirers of software-intensive systems
• Other courses in development
CMMI Transition Plan
How Do I Transition My Organization?
• Decide whether the staged or continuous representation is more appropriate
• Decide the scope of the improvement effort
– Software projects only
– Systems engineering projects only
– All projects
• Perform an gap analysis of your current practices against the model changes from SW-CMM and/or EIA 731
– New Process Areas
– New Common Features
– New/different practices
– Do you need a new infrastructure to cover a new discipline?
– Do you want a comprehensive assessment? Informal/formal?
• Set goals, develop a plan, implement the plan, assess progress
Summary
Organizations that are currently using SW-CMM v1.1 or EIA/IS 731 should be able to smoothly transition
http://www.sei.cmu.edu/cmmi/
• CMMI Model, SCAMPI Method Description
• IPPD Model (when available)
• CMMI news, presentations, articles, correspondence
• FAQs (Frequently Asked Questions)
• CMMI Plans and Schedules
• CMMI Transition Plan |
'UP! > Software Engineering' 카테고리의 다른 글
공급망관리 (0) | 2008.08.21 |
---|---|
시스템구현 (0) | 2008.08.21 |
객체지향 분석과 설계 (0) | 2008.08.21 |
문서화 (0) | 2008.08.21 |
CASE (0) | 2008.08.21 |