Software Development: Software Development: Tools and Processes - - PowerPoint PPT Presentation
Software Development: Software Development: Tools and Processes Tools and Processes Lecture - - 4: Introduction to CMMI Framework 4: Introduction to CMMI Framework Lecture 1 1 Process Improvement Framework What do we understand by
1 1
Lecture Lecture -
4: Introduction to CMMI Framework
Process Improvement Framework
What do we understand by Framework? What is the advantage of using a framework?
3 3
4 4
5 5
6 6
7 7
1987 1991 1995 1997 2000 2002
First CMM Published Model Refined and Published as SW-CMM v1.0 SW-CMM v1.1 Published
1993
Software Acquisition (SA-CMM), Systems Engineering (SE-CMM), Integrated Product Development (IPD-CMM), Organizational Workforce Capability Development (People CMM) Developed CMMI Initiative Launched CMMI-SE/SW Version 1.0 Published CMMI-SE/SW/IPPD/A Version 1.1 Published
8 8
CMMI Models
Different disciplines
Different representations
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.
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
Why Is a Model Important?
A model provides
a place to start the benefit of a community’s prior
experiences
a common language and a shared vision a framework for prioritizing actions
More about Processes ….
Having processes is only side of the story Maturity of the processes is also very important
About Capability Maturity Models
Capability Maturity Models (CMM) are used for several
Guide process improvement efforts and help organizations
establish and achieve improvement goals.
Provide a common language for cross-organizational
communication and benchmarking.
Provide an integrating, organizing framework for organizational
endeavours.
Help an organization understand what specific practices to perform,
how to improve its capability in performing those practices, and what process areas to focus on next.
14 14
15 15
16 16
17 17
Each level of CMMI increases the visibility into the software process software process
Level 1: black box – – only in & out
– 90 90-
90 rule
Level 2: Project tracking at mile stones – – management reacts to problems management reacts to problems
Level 3: Activities of phases are visible – – proactive proactive approach to risks approach to risks
Level 4: Controlled quantitatively – – progress is progress is measured measured – – objective decision making
Level 5: New ways of construction – – in efficient in efficient processes are replaced with new ones processes are replaced with new ones
18 18
19
Software Engineering Process Office
8/17/99 p 11
Process Maturity Benefits
Initial Repeatable Defined Managed Optimizing Process is informal and ad-hoc; performance is unpredictable Project management System in place; performance is repeatable Software engineering and management processes defined and integrated Product and process are quantitatively controlled Process improvement is institutionalized Level Process Characteristics
5
Probability Time / $ Target Probability Time / $ Target
4
Probability Target
3
Time / $ Probability Time / $ Target
2
Probability Time / $ Target
1
Predicted Performance
20 20
Improving the Predictability
Improving the control
Improving the effectiveness
21
22 22
What is the difference between Skill and knowledge and knowledge
What do we understand by knowledge management? knowledge management?
23 23
Knowledge Mastery Competency Skills