3. Before
The Activity Theory:
Human activity is performed by:
Agents (subject) motivated towards solving of
A problem or purpose (goal or motive) mediated by
Tools (artifacts) within a transformation process giving
Result (output).
Tool
Subject Goal
Transformation
Process
Result
The activity theory
(Vygotsky and Soviet
school)
The main interest is to
understand and analyze
the socio-cultural effects
of human thought
4. Activity Theory (C. Schalles, 2012)
Leontjev (1978) proposes that an activity has a
hierarchical structure with three distinct levels:
• The activity level,
• The action level and
• The operation level.
Activities consist of actions, which consist of
operations. Actions are basic components of
activities. Different actions may be undertaken to
meet the same goal. Operations are ways of
executing actions, and represent the concrete
conditions required to achieve goals.
5. Activity Theory (C. Schalles, 2012)
• Activity Theory emphasizes that human activity
is mediated by artefacts.
• The mediating artifact can be external (e.g.
modeling tool) or internal (e.g. motivation,
modeling experience).
6. Before
Procedures and methods
defining the relationship of
tasks
Tools and
equipment
People
with skills,
training, and
motivation
A
B
C
D
PROCESS
The SEI dimensions that an organization must focus on to improve its business.
Source: CMMI Dev Intro
7. 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 and
maintenance.
• There is an emphasis on both systems
engineering and software engineering and the
integration necessary to build and maintain the
total product.
8. CMMI
• Reference model used by organizations that want
improve their development processes and
maintenance of products and services
• Born in the Software Institute Engenieering (SEI) -
Carnegie Mellon University
9. CMMI
• This model is based on a set of practices that
organizations can take to implement more
productive processes
• It is a model of maturity because it proposes to
adopt this practices in a phased manner: It was put
into practice areas of process belonging to a certain
level and then on this basis to introduce the next
level
10. Evolution of CMMI
The CMM Integration project was formed to sort out the problem of
using multiple CMMs. The CMMI Product Team's mission was to
combine three source models:
1. The Capability Maturity Model for Software (SW-CMM) v2.0
draft C
2. The Systems Engineering Capability Model [1](SECM) [1] The
Systems Engineering Capability Model is also known as
Electronic Industries Alliance 731 (EIA 731) [EIA 98]
3. The Integrated Product Development Capability Maturity Model
(IPD-CMM) v 0.98
11. Evolution of CMMI
The combination of these models into a single improvement
framework was intended for use by organizations in their
pursuit of enterprise-wide process improvement
These three source models were selected because of their
widespread adoption in the software and systems
engineering communities and because of their different
approaches to improving processes in an organization
12. 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 Process
Areas that contain the recommended practices that make the
model work.
13. 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.
14. 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
15. 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.
16. Process Areas (CMMI v 1.3)
Causal Analysis and Resolution CAR
Configuration Management CM
Decision Analysis and Resolution DAR
Integrated Project Management IPM
Measurement and Analysis MA
Organizational Performance Management OPM
Organizational Process Definition OPD
Organizational Process Focus OPF
Organizational Process Performance OPP
Organizational Training OT
Product Integration PI
18. Process Areas by Functional Category
(1.3)
Project Management
PMC
PP
IPM
QPM
RSKM
SAM
REQM
Engineering
TS
VAL
VER
PI
RD
Support
PPQA
CM
MA
DAR
CAR
Process Management
OPM
OPD
OPF
OPP
OT
19. A process area is a cluster of related practices in an area
that, when implemented collectively, satisfies a set of
goals considered important for making significant
improvement in that area
As a general rule, each Process Area can be
implemented on its own, independent of the others.
Many of the Process Areas in CMMI are related to each
other, add strength to each other, and build upon each
other.
20.
21. Project Management
What to build
What 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 Control
PP = Project Planning
SAM = Supplier Agreement Management
REQM = Requirements Management
PP
Product and
product component
requirements
Product and
product
component
requirements
23. 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 Integration
RD = Requirements Development
TS = Technical Solution
VAL = Validation
VER = Verification
Project Management
process areas
Requirements
25. Tying it All Together: levels
Levels are used in CMMI to describe an evolutionary path
recommended for an organization that wants to improve the
processes it uses to develop and maintain its products and
services (Software).
CMMI supports two improvement paths. One path enables
organizations to incrementally improve processes corresponding
to an individual process area (or process areas) selected by the
organization. The other path enables organizations to improve a
set of related processes by incrementally addressing successive
sets of process areas.
26. Fuente: Bill Curtis. Software Quality in Healthcare Systems. MBSE in HealthCare Summit, Boston MA. June 2014
27.
28.
29.
30.
31. 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
32. Levels
• Regardless of which representation is selected, the concept of levels is
the same. Levels characterize improvement from an ill-defined state to
a state that uses quantitative information to determine and manage
improvements that are needed to meet an organization’s business
objectives.
• To reach a particular level, an organization must satisfy all of the
appropriate goals of the process area or set of process areas that are
targeted for improvement, regardless of whether it is a capability or a
maturity level.
• Both representations also provide ways to implement process
improvement to achieve business objectives. Both representations
provide the same essential content and use the same model
components.
33. 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 development
organizations that want to improve their ability to develop products
and services.
• CMMI for Services V1.3: designed for service provider
organizations that want to improve their ability to establish,
manage, and deliver services.
34. More Info
• CMMI Dev
http://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/
35. 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 Dev
http://cmmiinstitute.com/cmmi-solutions/cmmi-for-development/cmmi-dev-comparisons/
• Traducciones (No RECOMENDADO)
• http://cmmiinstitute.com/cmmi-solutions/translations/
