| |
In 1993 Carnegie-Mellon University
published Key Practices of the Capability
Maturity Model. Since then it has become a standard
by which software developers measure themselves. |
|
| |
|
|
| |
The first assumption of this document is that
the goal of every developer should be to deliver reliable
software . . . on time and . . . within budget.
If this is not the goal of the software developer it
surely is the desire of the customer of such development. The
customer has every right to expect excellent work. |
|
| |
|
|
| |
The Capability Maturity Model identifies
five (5) levels of maturity. Each level, except the first, has
key process areas that the developer organization must attain
to be considered mature at that level. The break down is as
follows: |
|
| |
|
|
| |
|
Level |
Key Process Areas |
|
| |
|
|
|
|
| |
1 |
Initial |
(none) |
|
| |
|
|
|
|
| |
2 |
Repeatable |
Requirements Management
Software Project Planning
Software Project Tracking and Oversight
Software SubContract Management
Quality Assurance
Software Configuration Management
|
|
| |
|
|
|
|
| |
3 |
Defined |
Origanization Process Focus
Organization Process Definition
Training Program
Integrated Software Management
Software Product Engineering
Intergroup Coordination
Peer Reviews |
|
| |
|
|
|
|
| |
4 |
Managed |
Quantitative Process Management
Software Quality Management |
|
| |
|
|
|
|
| |
5 |
Optimizing |
Defect Prevention
Technology Change Management
Process
Change Management |
|
| |
|
|
|
|
| |
Are you mature? Developing Methods can help. Get
equipped and mature with PRACTICUM process training. |
|