Process Assets by SW-CMM® KPA Archive

The SW-CMM® has been replaced by CMMI®.  SW-CMM® process assets will be retained as an archive, but will not be maintained after December 31, 2003.  This page has been replaced by the Process Assets by CMMI® PA page.

Maturity Level Characteristic

KPA1

SW-CMM®  Key Process Area1

CMMI® Process Area2

5 - Optimizing Continuous process capability improvement DP
TCM
PCM 		Defect Prevention
Technology Change Management
Process Change Management 		CAR
OID
OID
4 - Managed Product quality planning; tracking of measured software process QPM
SQM 		Quantitative Process Management
Software Quality Management 		OPP
QPM
3 - Defined Software process defined and institutionalized to provide product quality control OPF
 OPD
TP
ISM
SPE
IC
PR 		Organization Process Focus
 Organization Process Definition
Training Program
Integrated Software Management
Software Product Engineering
Intergroup Coordination
Peer Reviews 		OPF
OPD
OT
IPM,RSKM
TS,PI,VER,VAL,RD
IPM
VER
2 - Repeatable Management oversight and tracking project; stable planning and product baselines RM
SPP
SPTO
SSM
SQA
SCM 		Requirements Management
Software Project Planning
Software Project Tracking and Oversight
Software Subcontract Management
Software Quality Assurance
Software Configuration Management 		REQM
PP
PMC
SAM
PPQA
CM
1 - Initial Ad hoc (success depends on heroes)   "People"  

Supporting Information

Notes

  1. Click on a Key Process Area (KPA) link to go to that section.

  2. CMMI® PA corresponding to this SW-CMM® KPA.

  3. Link to the Software Engineering Institute  Web site, from which you can download a PDF version of this document.

  4. ® Capability Maturity Model, SW-CMM, and CMMI are registered in the U.S. Patent and Trademark Office by Carnegie Mellon University.

 

Level 2 (Repeatable) Key Process Areas

                                            Requirements Management (RM)                                      Top of Page

Policy

Processes

  • Requirements Management Process (Expert Mode)

Tools

Notes

  1. This is an edited version of the Requirements Management Guidebook from the Naval Air Warfare Development Center.

  2. For additional information see Requirements Management Guidebook1 and INCOSE Requirements Management Tools Survey.

 

                                            Software Project Planning (SPP)                                      Top of Page

Policy

Plans

Software Transition Plan (STrP) Template

Processes

Training

Tools

Instructions for Using the Schedule Templates

  1. Download & save schedule-estimation template.

  2. Open file using MS Project 98 (or higher).

  3. Change project information (e.g., project start date, project name, etc).

  4. Edit the resource sheet using the real names of project team members.

  5. Review work/requirements to be done; enter task durations, resource names, and units accordingly.

  6. Review / adjust as required (to ensure a reasonable schedule).

  7. Review / adjust  resource allocations and project durations with project team and sponsor as required.

For further information and/or assistance with the schedule template please contact SEPO.

SEPO Library

  • Computer Resources Life Cycle Management Plan (CRLCMP) SECNAVINST 5000.21
    Computer Resources Life Cycle Management Plan (CRLCMP) SPAWARINST 5200.22M
    Guide for Developing Computer Resources Life Cycle Management Plan (CRLCMP)

Notes

  1. For additional information see:

                             Software Project Tracking and Oversight (SPTO)                               Top of Page

Policy

Processes

Procedures

Tools

Notes

  1. For additional information see:

 

                                Software Subcontract Management (SSM)                                    Top of Page

Policy

Processes

Notes

  1. These documents are courtesy of the NAVAIR TEAM Software Subcontractor Management Working Group.

  2. COTS process and COTS related links.  The same link appears under SPP, SSM, and SPE since COTS information may be needed during planning, contracting, or engineering activities.

  3. For additional information see:

 

                                    Software Quality Assurance (SQA)                                              Top of Page

Policy

Processes

Tools

SEPO Library

  • AN/SQQ-89(V) Tactical Decision Support Subsystem Phase I SQPP

Notes

  1. Contains testing process, test forms, and checklists.

  2. For additional information see:

 

 

                                Software Configuration Management (SCM)                                     Top of Page

Policy

Plans

Processes

Procedures

Training

Tools

SEPO Library

  • COMPASS SCMP
  • STAFS Project PCA and FCA Procedures

Notes

  1. For additional information see:

Level 3 (Defined) Key Process Areas

                                    Organization Process Focus (OPF)                                              Top of Page

Policy

Plans

 

                                    Organization Process Definition (OPD)                                         Top of Page

Policy

Processes

Procedures

Tools

SEPO Library

  • Costs and Benefits of Software Process Improvement

Notes

  1. This document contains a description of the SSC Pacific software process assets, standard software process, process tailoring guidelines, and approved life cycles.

  2. Projects are encouraged to incorporate their process improvement plans and tasking into their project plans (e.g. SDP, PMP).  SPI plans and tasking should not be treated separately from other project tasking.

  3. For additional information see Standard Process Assets Architecture Definition (SPAA Volume 1)1.

 

                                              Training Program (TP)                                                      Top of Page

Policy

Plans

  • Space & Naval Warfare Systems Center San Diego Software Engineering Training Plan (an updated version will be available later)

Processes

Tools

Notes

  1. For additional information see:

 

                               Integrated Software Management (ISM)                                    Top of Page

Policy

Plans

Organizational Program Management Plan

The following document is presented as a generic model of an Organizational Program Management Plan (OPMP), addressing topics required to achieve Level 3 on the SW-CMM®.  The objective is to assist organizations in documenting "a compliant management structure, the assignment of management responsibility, management processes, and establishing the software engineering disciplines needed to support the various projects under their cognizance."

Users should first review the model OPMP to ensure an understanding of its scope, management functions, relationships, and responsibilities for the positions within the model organization. It is important to understand that the OPMP's sample organization and management processes do not fit all organizations. Rather, the model OPMP serves as a representative means of defining an organization. Therefore, it is understood that this model will require tailoring to meet specific organizational needs.

Tools

 

                                    Software Product Engineering (SPE)                                         Top of Page              

Policy

Processes

Tools

SEPO Library

  • Reuse Adoption Guidebook
  • Software IV&V AFSC/AFLC Pamphlet 800-5 5/20/88
  • IEEE Guide for Software V&V Plans 1059-1993

Notes

  1. COTS process and COTS related links.  The same link appears under SPP, SSM, and SPE since COTS information may be needed during planning, contracting, or engineering activities.

  2. For additional information see:

                                         Intergroup Coordination (IC)                                                Top of Page

Policy

Processes

Training

Guidelines for Successful Teams Workshop     Attachments     Team Evaluation

Notes

  1. Additional information on Intergroup Coordination can be found in the example Organization Project Management Plan, which can be found in the ISM KPA.

  2. Tips on conducting a successful meeting can be found in the Keys to a Successful Review/Meeting Brief, which can be found in the SPTO KPA.

 

                                              Peer Reviews (PR)                                                        Top of Page

Policy

Processes

Procedures

Tools

Notes

  1. "Analysis of 148 Formal Inspections revealed that each person will spend 19 minutes per page finding an error every 2.8 pages. So a team of 5 inspectors working on a 50 page document will yield 89 errors while using 16 hours per person."

  2. The Formal Inspection Process has been incorporated into, and combined with, the Peer Review Process.  The standalone Formal Inspection Process V 2.2 is obsolete.

  3. This form can be used with any form of peer review and is similar to the Peer Review Defect Log (Form 2), but in MS Excel format.

  4. For additional information see:

 

Level 4 (Managed) Key Process Areas

                                   Quantitative Process Management (QPM)                                    Top of Page

Policy

Notes

  1. For additional information see the Organizational Measurement Guide.

 

                                        Software Quality Management (SQM)                                     Top of Page

Policy

Level 5 (Optimizing) Key Process Areas

                                            Defect Prevention (DP)                                                    Top of Page

Policy

 

                                Technology Change Management (TCM)                                     Top of Page

Policy

 

                                    Process Change Management (PCM)                                      Top of Page

Policy

 

Last Update: October 28, 2009