CMM Level 3
Lecture # 11A
1
CMM Capability Maturity Model
•
•
•
•
•
Initial
Repeatable
Defined
Managed
Optimizing
2
The Defined Level
C
MM
Moving from
Level 2 to Level 3
• At level 2, the focus is on projects
• At level 3, the emphasis shifts to the organization
– best practices are gathered across the organization
– processes are tailored as appropriate
• organization supports the project by establishing
– common processes, common measurements and training
Moving from
Level 2 to Level 3
• Organizations have mastered a development
process that can often lead to successful
large systems
• Over and above the project management
and technical approaches found in Level 2
organizations, the Level 3 groups have a
welldefined development process that can
handle all sizes and kinds of projects
5
Following slide to be inserted
Level 3 KPAs
6
C
MM
•
•
•
•
•
•
•
KPA’s Level 3
Organization Process Focus
Organization Process Definition
Training Program
Integrated Software Management
Software Product Engineering
Intergroup Coordination
Peer Reviews
Organization Process Focus
C
MM
Purpose
• Purpose is to establish the organizational responsibility for
software process activities that improve the organization’s
overall process capability
• Involves
– developing and maintaining an understanding of organization’s and
projects software processes
– coordinating the activities to assess, develop, maintain, and improve
these processes
C
MM
Dedicating People to Process
• A dedicated group of people is responsible for the organization’s
software process activities; e.g.,
– appraisals
– software process improvement plans
• Includes maintaining the organization’s software process
database and providing training about the organization’s
software process
C
MM
Dedicated Groups
May Vary
• A software engineering process group (SEPG) is the typical means of
providing a process focus for the organization.
• Other ways of focusing on process are possible:
–
–
–
–
process review boards
quality circles
process steering committees
software quality assurance
• These mechanisms may work in conjunction with, or in place of, an
SEPG.
C
MM
•
•
•
•
•
•
Responsibilities of SEPGs
Establish process standards
Maintain the process database
Serve as the focal point for technology transition
Provide process education
Provide project consultation
Make periodic assessment and status reports
Organization Process Definition
C
MM
Purpose
• Purpose is to develop and maintain a useable set of software
process assets that improve process performance and provide a
basis for cumulative, and long term benefits.
• Involves
– developing and maintaining the organization’s standard software
process and related process assets
C
MM
Software Process Assets
• A Collection of entities, maintained by an organization for use by
projects in developing, tailoring, maintaining and implementing
their software practices.
• Software process assets include
– The organization’s standard software process
– Descriptions of software life cycles approved for use
– Guidelines and criteria for tailoring the organization’s standard software
process
– The organization’s software process database
– A library of software process related documentation
Following slide to be inserted
Context for Software Process Assets
in an Organization
16
C
MM
Context for Software Process Assets in
an Organization
Software Policy
Constrained by
Software product
standards
standard sw process
Standard
software
life cycles
Tailoring
guidelines
and criteria
Ordered by
Software Process
Architecture
Organized by
Software Process
Model
Tailored by
Software engineering
environment and tools
Implemented by
Software Project
Teams
Supported by
Training
C
MM
Process Building Blocks
• The organization’s standard software process includes
process elements for activities such as
–
–
–
–
–
software estimating
design
coding
peer review
Process elements as described in terms of standards, procedures,
templates, abstractions, etc., which can be “hooked together” to
form a process.
C
MM
Relating Process Elements
• Process elements have
– an order in which they can be connected (perhaps more than
one)
– interfaces
– interdependencies
• These relationships are sometimes referred to as a software
process architecture.
• Many different software processes can be built using the
architecture of the organization’s standard software process.
C
MM
Software Life Cycles
• The organization may support several software
life cycles models such as
–
–
–
–
–
–
–
waterfall
spiral
incremental
combination
prototype
rational unified process
agile processes
C
MM
Tailoring Guidelines:
• Guidelines for tailoring the organization’s standard
software process are available to individual projects.
• What can be tailored out? What cannot?
• How much can a process element be modified?
• What part of a process element should be considered for
tailoring?
C
MM
Organizations software Process
Database: Measuring Data
A central repository for organization measurement data.
• Contains
– actual measurement data (the numbers) from individual projects
– The related information needed to understand the measurement data and
apply it to the new projects
This is where the planning and replanning data for the organization
as a whole are kept
C
MM
Library of software process related
documentation
• The library where best documents used on past projects
are kept
• Also contains lessons learnt, reports, example documents
and document fragments
• In general contains any document that can be used as
model or example for future projects
C Relation to Organization Process
Definition
MM
• Organization Process Focus and Organization Process
Definition are tightly coupled
• Organizational Process Focus focuses on the who (roles
and people).
• Organization Process Definition focuses on the what.
Training Program