CMMI

CMMI 1.3

Before…..Think about relation between:• ISO 25000• ISO 9126• ISO 15504

• RUP• Scrum, XP, AUP, …

• CMMI???

Before

The Activity Theory:Human activity is performed by: Agents (subject) motivated towards solving ofA problem or purpose (goal or motive) mediated byTools (artifacts) within a transformation process giving Result (output).

Tool

Subject Goal

TransformationProcess

Result

The activity theory(Vygotsky and Soviet school)The main interest is to understand and analyzethe socio-cultural effectsof human thought

Activity Theory (C. Schalles, 2012)Leontjev (1978) proposes that an activity has ahierarchical structure with three distinct levels:• The activity level,• The action level and• The operation level.Activities consist of actions, which consist ofoperations. Actions are basic components ofactivities. Different actions may be undertaken tomeet the same goal. Operations are ways ofexecuting actions, and represent the concreteconditions required to achieve goals.

Activity Theory (C. Schalles, 2012)

• Activity Theory emphasizes that human activityis mediated by artefacts.

• The mediating artifact can be external (e.g.modeling tool) or internal (e.g. motivation,modeling experience).

BeforeProcedures and methods defining the relationship of

tasks

Tools and equipment

People with skills, training, and motivation

A

B

CD

PROCESS

The SEI dimensions that an organization must focus on to improve its business. Source: CMMI Dev Intro

CMMI• CMMI consists of best practices that address

product development and maintenance.• It addresses practices that cover the product's life

cycle from conception through delivery andmaintenance.

• There is an emphasis on both systemsengineering and software engineering and theintegration necessary to build and maintain thetotal product.

CMMI• Reference model used by organizations that wantimprove their development processes andmaintenance of products and services

• Born in the Software Institute Engenieering (SEI) -Carnegie Mellon University

CMMI• This model is based on a set of practices thatorganizations can take to implement moreproductive processes• It is a model of maturity because it proposes toadopt this practices in a phased manner: It was putinto practice areas of process belonging to a certainlevel and then on this basis to introduce the nextlevel

Evolution of CMMIThe CMM Integration project was formed to sort out the problem of

using multiple CMMs. The CMMI Product Team's mission was tocombine three source models:

1. The Capability Maturity Model for Software (SW-CMM) v2.0draft C

2. The Systems Engineering Capability Model [1](SECM) [1] TheSystems Engineering Capability Model is also known asElectronic Industries Alliance 731 (EIA 731) [EIA 98]

3. The Integrated Product Development Capability Maturity Model(IPD-CMM) v 0.98

Evolution of CMMIThe combination of these models into a single improvement

framework was intended for use by organizations in theirpursuit of enterprise-wide process improvement

These three source models were selected because of theirwidespread adoption in the software and systemsengineering communities and because of their differentapproaches to improving processes in an organization

Coverage of the Bodies of Knowledge

• Systems engineering

• Software engineering

• Integrated product and process development

In CMMI, these disciplines are keyed to a series of ProcessAreas that contain the recommended practices that make themodel work.

Systems Engineering

Systems engineering covers the development of total

systems, which may or may not include software. Systems

engineers focus on transforming customers' needs,

expectations, and constraints into products and supporting

these products throughout their life.

Software Engineering

Software engineering covers the development of software

systems. Software engineers focus on applying systematic,

disciplined, and quantifiable approaches to the development,

operation, and maintenance of software

Integrated Product and Process Development

Integrated product and process development (IPPD) is a

systematic approach that achieves a timely collaboration of

relevant stakeholders throughout the life of the product to

satisfy customers' needs, expectations, and requirements.

The processes to support an IPPD approach are integrated

with the other processes in the organization.

Process Areas (CMMI v 1.3)Causal Analysis and Resolution CARConfiguration Management CMDecision Analysis and Resolution DARIntegrated Project Management IPMMeasurement and Analysis MAOrganizational Performance Management OPMOrganizational Process Definition OPDOrganizational Process Focus OPFOrganizational Process Performance OPPOrganizational Training OTProduct Integration PI

Fuctional Categories• Engineering• Project Management• Process Management• Support

Process Areas by Functional Category(1.3)

Project ManagementPMCPP

IPMQPMRSKMSAM

REQM

Engineering

TSVALVER

PIRD

SupportPPQA

CMMADARCAR

Process ManagementOPMOPDOPFOPPOT

A process area is a cluster of related practices in an areathat, when implemented collectively, satisfies a set ofgoals considered important for making significantimprovement in that area

As a general rule, each Process Area can beimplemented on its own, independent of the others.Many of the Process Areas in CMMI are related to eachother, add strength to each other, and build upon eachother.

Project Management

What to buildWhat to do

SAM

What to monitor

Replan

Plans

Status, issues, and results of reviews and monitoring

Product component requirements, technical issues, completed product components, and acceptance reviews and tests

Engineering and Support process areas

Measurement needs

Supplier agreement

Corrective action

Commitments

Corrective action

Status, issues, and results of process and product evaluations; measures and analyses

REQM

PMC

Supplier

PMC = Project Monitoring and ControlPP = Project Planning

SAM = Supplier Agreement ManagementREQM = Requirements Management

PP

Product and

product component

requirements

Product and product component requirements

Process Management

Engineering

RD PI

VAL

TS

VER

Requirements

Customer needs

Product and product component requirements

Requirements, Product components, work products, verification and validation reports

Product components

Alternative solutions Product

Customer

PI = Product IntegrationRD = Requirements DevelopmentTS = Technical SolutionVAL = ValidationVER = Verification

Project Management process areas

Requirements

Support

Tying it All Together: levelsLevels are used in CMMI to describe an evolutionary pathrecommended for an organization that wants to improve theprocesses it uses to develop and maintain its products andservices (Software).CMMI supports two improvement paths. One path enablesorganizations to incrementally improve processes correspondingto an individual process area (or process areas) selected by theorganization. The other path enables organizations to improve aset of related processes by incrementally addressing successivesets of process areas.

Fuente: Bill Curtis. Software Quality in Healthcare Systems. MBSE in HealthCare Summit, Boston MA. June 2014

OPM

Organizational Performance Management

CAR

Causal Analysis and Resolution

OPP

Organizational Process Perfomance

QPM

Quantitative Project Management

RD TS PI VER VAL RSKM

IPM DAR OPD OPF OT

REQM PP PMC SAM MA PPQA

Requirements Development

Technical Solution Product Integration Verification Validation Risk Management

Integrated Project Management

Decision, Analysis and Resolution

Organizational Process Definition

Organizational Process Focus

Organizational Training

CM

Requirements Management

Project Palnning Project Monitoring and

control

Supplier Agreement

Management

Measurement anf Analysis

Process and Produc Quality

Assurance

Configuration Management

ML5

ML4

ML3

ML2

CMMI DEV 1.3

Levels• Regardless of which representation is selected, the concept of levels is

the same. Levels characterize improvement from an ill-defined state toa state that uses quantitative information to determine and manageimprovements that are needed to meet an organization’s businessobjectives.

• To reach a particular level, an organization must satisfy all of theappropriate goals of the process area or set of process areas that aretargeted for improvement, regardless of whether it is a capability or amaturity level.

• Both representations also provide ways to implement processimprovement to achieve business objectives. Both representationsprovide the same essential content and use the same modelcomponents.

CMMI Models• CMMI for Acquisition V1.3: designed for acquisition organizations

that want to improve their ability to acquire products and services.

• CMMI for Development V1.3: designed for developmentorganizations that want to improve their ability to develop productsand services.

• CMMI for Services V1.3: designed for service providerorganizations that want to improve their ability to establish,manage, and deliver services.

More Info• CMMI Devhttp://cmmiinstitute.com/resource/cmmi-for-development-version-1-3/

• CMMI for Acquisition

http://cmmiinstitute.com/cmmi-solutions/cmmi-for-acquisition/

• CMMI for Services

http://cmmiinstitute.com/cmmi-solutions/cmmi-for-services/

• People CMM

http://cmmiinstitute.com/cmmi-solutions/people-cmm/

• Data Management Maturity Model

http://cmmiinstitute.com/cmmi-solutions/dmm/

More Info• Start CMMI

http://cmmiinstitute.com/cmmi-getting-started/

• CMMI Compatibility with other process

http://cmmiinstitute.com/cmmi-getting-started/cmmi-compatibility/

• Comparaciones CMMI Devhttp://cmmiinstitute.com/cmmi-solutions/cmmi-for-development/cmmi-dev-comparisons/

• Traducciones (No RECOMENDADO)

• http://cmmiinstitute.com/cmmi-solutions/translations/

Source:http://plays-in-business.com/wp-content/uploads/2011/03/cmmi-constellations.jpg

Questions?

Thanks!