PMP Template
TM-PP-01 v2.0
5/24/05
PROJECT MANAGEMENT PLAN
TEMPLATE
TM-PP-01 V2.0
MAY 24, 2005
Systems Engineering Process Office, Code 20203
Space and Naval Warfare Systems Center
53560 Hull Street
San Diego CA 92152-5001
Approved for public release; distribution is unlimited.
PMP Template
TM-PP-01 v2.0
5/24/05
PREFACE
This template provides the format and content of a Project Management Plan (PMP) for a mid-sized
project (e.g., 5 to 20 staff members). Typically, larger projects will receive explicit direction from the
sponsor on planning documentation requirements. Smaller projects may use a scaled-down version of
this template. The template is considered flexible enough that it may be used for any type of project.
This document is part of a trilogy of sample documents and templates intended to support the guidance
provided by the SSC San Diego Project Management Guide (PMG). Figure A provides an abstract of the
PMG’s project management functions of Initiation, Planning, Control, Execution, and Close Out. As
depicted in Figure A, the Planning Function includes the development of plans to facilitate both the
Control Function and the Execution Function.
Figure A. Project Management Guide Functional Overview
Three documents available from the Space and Naval Warfare (SPAWAR) Systems Center (SSC) San
Diego Process Asset Library (PAL) Web site at http://sepo.spawar.navy.mil/ are recommended for the
implementation of the concepts presented in the PMG. While these documents are not the only means or
document selections that can facilitate this process, they are considered a ‘Best Practice’ and can be
tailored during the Planning Function to guide the Control Function and Execution Function. This trilogy
of documents includes those listed below:
Introduction - ii
PMP Template
TM-PP-01 v2.0
5/24/05
Trilogy Part 1. Project Management Plan (PMP) Template, TM-PP-01 (this document). Control
function planning requires a defined Management Solution, documented in a format such as the IEEE
Standard for Software Management Plans, IEEE Std 1058-1998. The PMP addresses such issues as
budget, budget control, schedule, schedule control, staffing, risk management, configuration
management, quality assurance, and project tracking measurements.
Trilogy Part 2. Product Engineering and Qualification (PE&Q) Process, PR-TS-01. Planning for
the Execution function results in documented engineering and qualification processes needed to
implement a project’s work product(s). The PE&Q Process represents an example of the level of
detail needed for these processes. The PE&Q Process represents one method of defining an
engineering process. Other process definition methods could include, but are not limited to, data flow
diagrams, Entry-Task-Verification &Validation-Exit (ETVX) diagrams, Integrated Computer Aided
Manufacturing Definition (IDEF) 0 or IDEF 3 diagrams for process flow, etc.
Trilogy Part 3. Project Build Plan Template, TM-PP-02. Planning for the functional content of the
project’s work product should result in a document as typified by the Project Build Plan Template.
This document defines the product content in terms of functional requirements to be delivered, the
acceptance criteria, fielding direction, and user training needs. This document could serve as a
contract between the acquirer and the supplier for any given deliverable increment of the product.
Other build plan methodologies could include, but are not limited to, use of the MIL-STD 498 Data
Item Description (DID) for Software Version Description (SVD), or detailed project plans itemizing
the product content.
These three documents are an integral part of the SSC San Diego-approved life cycle strategies as defined
in A Description of the SSC San Diego Standard Process Assets (SPA). These documents are available on
the SSC San Diego PAL Web site along with the SPA itself.
SSC San Diego has assigned the responsibility for this document to the Systems Engineering Process
Office (SEPO). SEPO welcomes and solicits feedback from users of this document so that future
revisions of this document will reflect improvements, based on organizational experience and lessons
learned. Questions or comments regarding this document may be communicated to SEPO via the
Document Change Request form located on the next page or submitted online via the SSC San Diego
PAL. Updates to this document are performed in accordance with the SEPO Configuration Management
Procedure.
Introduction - iii
PMP Template
TM-PP-01 v2.0
5/24/05
DOCUMENT CHANGE REQUEST (DCR)
Document Title: Project Management Plan Template
Tracking Number:
Name of Submitting Organization:
Organization Contact:
Phone:
Mailing Address:
DCR Description:
Date:
Change Location:
(use section #, figure #, table #, etc.)
Proposed change:
Rational for Change:
Note: For the Systems Engineering Process Office (SEPO) to take appropriate action on a change request,
please provide a clear description of the recommended change along with supporting rationale.
Send to: Commanding Officer, Space and Naval Warfare Systems Center, Code 20203, 53560 Hull Street, San
Diego, CA 92152-5001
Fax : (619) 553-6249
Email : sepo@spawar.navy.mil
Submit online: http://sepo.spawar.navy.mil/
DCR Form 11/2004
Introduction - iv
PMP Template
TM-PP-01 v2.0
5/24/05
RECORD OF CHANGES
*A - ADDED M - MODIFIED D – DELETED
VERSION
NUMBER
DATE
1.0
12/16/03
NUMBER OF
FIGURE, TABLE
OR PARAGRAPH
A*
M
D
TITLE OR BRIEF DESCRIPTION
CHANGE
REQUEST
NUMBER
Original. This document
PP-0002
replaces the document of the
same name with a configuration
number of TM-SPP-09. Minor
corrections to references and
several configuration numbers
have been made in this version
2.0
5/24/05
Throughout
A
M
D
Updated per Project
Management Council Peer
Review
2.0
5/24/05
Throughout
A
Added information about using
the DAR Process
PP-0004
2.0
5/24/05
Throughout
A
Multiple changes from DCR
PP-0007
2.0
5/24/05
Section 5.4
A
Expand information on Risk
Management
PP-0008
Introduction - v
PMP Template
TM-PP-01 v2.0
5/24/05
DOCUMENT CONVENTIONS
The outline of this Project Management Plan (PMP) has been tailored from the Institute of Electrical and
Electronics Engineers (IEEE) Standard for Software Project Management Plans, IEEE Std 1058-1998.
While the title implies guidance for software projects, the content, scope, and flexibility of the IEEE
Standard facilitates application to a variety of projects that are typical of the scope found at SSC San
Diego (i.e., systems, software, integration services, R&D, etc.). It is intended that the template and its
content be tailored to define a project's management, technical, and supporting processes in the context of
Standard for Information Technology - Software Life Cycle Processes, IEEE/Electronic Industries
Association (EIA) 12207 Series; Systems Engineering – System Life Cycle Processes, International
Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 15288; or the
Processes for Engineering a System, Electronic Industries Alliance (EIA) Standard 632.
Standard conventions are used within this document to direct the reader to specific sections of the text.
These sections provide instructions and explanations and require users to substitute their own projectspecific information for the generic information provided or to “fill in the blank.” The conventions used
in this document are shown below.
[[text]]
Global changes. Items that appear in regular text and are surrounded by double brackets
represent changes that can be made globally throughout the document.
Italics
Individual changes. Items that appear in bold italics represent items that need to be
changed in that location only. The bold italics are not meant to appear in the completed
version of the document.
Italics
Instructions and explanations. Each section of the template has been annotated with a
guidance box, derived from the IEEE 1058-1998 standard, to assist the reader in drafting
the content. For example:
IEEE Std 1058-1998 Guidance
The guidance box provides instructions and explanations from the IEEE 1058-1998
standard, in italics, as required to assist the user in drafting their own information.
Watermark.
To further assist in drafting the required information, the sections contain a sample of a
hypothetical project. A watermark has been placed diagonally across the page to indicate
that the text is an example of the type of information that should appear in each section.
The samples have been constructed such that if extracted from the template with their
associated paragraph number they would create a good first draft of a PMP. The template
samples are written as a project management plan for a hypothetical project, the
Red/Black Controller (RBC) Project. Combining the IEEE standard derived guidance
with sample content has created a template in the form of an annotated version of a PMP.
Users should first review the generic processes contained in the PMP Template samples to ensure an
understanding of scope, management processes, technical processes, relationships, and responsibilities for
the positions within the model organization. It is important to understand that the sample organization
and processes do not fit all projects but serve as a representative example, requiring tailoring to meet
project specific needs.
It is recommended that the Section 4 organizational diagrams and Table 4-1, addressing roles and
responsibilities, be printed and kept readily available for reference as one reads the individual samples
associated with the guidance information.
Tailoring should follow the directions contained in the SPA document available from the SSC San Diego
PAL.
Introduction - vi
PMP Template
TM-PP-01 v2.0
5/24/05
The PMP Template contains engineering process definitions and references to other key templates for
disciplines such as configuration management and quality assurance. These templates, available from the
SSC San Diego PAL, comprise a suite of process descriptions that can be packaged in a multitude of
formats.
The PMP Template is intended to be tailored at the Department level to serve each Department’s business
domain prior to its deployment to individual projects.
The PMP begins on the next page with a PMP title and approval page. Delete this Document
Conventions page and all preceding pages in the final version of your PMP. Remember to update the
header to reflect the appropriate document configuration identifier for your project’s PMP.
Introduction - vii
PMP Template
TM-PP-01 v2.0
5/24/05
This page intentionally left blank.
Introduction - viii
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
PROJECT MANAGEMENT PLAN
FOR THE
[[RED/BLACK CONTROLLER PROJECT]]
[[DOCUMENT CONFIGURATION IDENTIFIER]]
[[DATE]]
Place project logo here
[[Project Name, Code]]
Space and Naval Warfare Systems Center
53560 Hull Street
San Diego CA 92152-5001
Approved for public release; distribution is unlimited.
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
PROJECT MANAGEMENT PLAN
FOR THE
[[RED/BLACK CONTROLLER PROJECT]]
[[DOCUMENT CONFIGURATION IDENTIFIER]]
[[DATE]]
PMP Approvals:
_____________________________
[[RBC]] Project Manager
____________
Date
_____________________________
Division Head
____________
Date
_____________________________
Program Manager
____________
Date
[[SYSCOM Communications Security Office]]
ii
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
PREFACE
This Project Management Plan (PMP) is intended to provide guidance on the management of the
[[Red/Black Controller (RBC) Project]].
The plan has been tailored from the Space and Naval Warfare (SPAWAR) Systems Center (SSC) San
Diego Project Management Plan Template, TM-PP-01. The template conforms to the Institute of
Electrical and Electronics Engineers (IEEE) Standard for Software Project Management Plans, IEEE Std
1058-1998, for format and content. The template and its standard were selected as they are flexible
enough to be applied to any type of project. The management, technical, and supporting processes
comply with the guidance provided by Standard for Information Technology - Software Life Cycle
Processes, IEEE/Electronic Industries Association (EIA) 12207 Series; Systems Engineering – System
Life Cycle Processes, International Organization for Standardization (ISO)/International Electrotechnical
Commission (IEC) 15288; or the Processes for Engineering a System, Electronic Industries Alliance
(EIA) Standard 632; and the SSC San Diego Systems/Software Engineering Management Policy.
The [[RBC]] Project Manager assumes responsibility for this document and updates it as required to meet
the needs of the [[Systems Command Communications Security Office]]. Updates to this document are
performed in accordance with the [[RBC]] Configuration Management Process, [[RBC CM process
document configuration identifier]].
iii
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
RECORD OF CHANGES
*A - ADDED M - MODIFIED D – DELETED
VERSION
NUMBER
DATE
NUMBER OF
FIGURE, TABLE
OR PARAGRAPH
A*
M
D
iv
TITLE OR BRIEF DESCRIPTION
CHANGE
REQUEST
NUMBER
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
TABLE OF CONTENTS
Section
Page
SECTION 1. OVERVIEW ....................................................................................................................... 1-1
1.1
Project Summary ........................................................................................................................ 1-1
1.1.1
Purpose, Scope, and Objectives ......................................................................................... 1-2
1.1.2
Assumptions and Constraints ............................................................................................. 1-2
1.1.3
Project Deliverables ........................................................................................................... 1-2
1.1.4
Master Schedule and Budget Summary ............................................................................. 1-3
1.2
Evolution of the Plan ................................................................................................................. 1-4
1.3
Document Structure ................................................................................................................... 1-4
SECTION 2. REFERENCES.................................................................................................................... 2-1
2.1
2.2
Standards and Documents .......................................................................................................... 2-1
Deviations and Waivers ............................................................................................................. 2-2
SECTION 3. DEFINITIONS .................................................................................................................... 3-1
SECTION 4. PROJECT ORGANIZATION ............................................................................................ 4-1
4.1
External Interfaces ..................................................................................................................... 4-1
4.2
Internal Structure ....................................................................................................................... 4-3
4.2.1
The Project Manager .......................................................................................................... 4-3
4.3
Project Roles and Responsibilities ............................................................................................. 4-4
SECTION 5. MANAGEMENT PROCESS.............................................................................................. 5-1
5.1
Start-up ....................................................................................................................................... 5-1
5.1.1
Estimation .......................................................................................................................... 5-1
5.1.2
Staffing............................................................................................................................... 5-1
5.1.3
Resource Acquisition ......................................................................................................... 5-2
5.1.4
Staff Training ..................................................................................................................... 5-2
5.2
Work Planning ........................................................................................................................... 5-2
5.2.1
Work Activities .................................................................................................................. 5-2
5.2.2
Schedule Allocation ........................................................................................................... 5-3
5.2.3
Resource Allocation ........................................................................................................... 5-3
5.2.4
Budget Allocation .............................................................................................................. 5-5
5.3
Project Controls ......................................................................................................................... 5-6
5.3.1
Requirements Control ........................................................................................................ 5-7
5.3.2
Schedule Control ................................................................................................................ 5-7
5.3.3
Budget Control ................................................................................................................... 5-8
5.3.4
Quality Control ................................................................................................................ 5-10
5.3.5
Project Reporting and Communication ............................................................................ 5-10
5.3.6
Metrics Collection ............................................................................................................ 5-11
5.4
Risk Management .................................................................................................................... 5-11
5.5
Project Closeout ....................................................................................................................... 5-12
SECTION 6. TECHNICAL PROCESS .................................................................................................... 6-1
6.1
6.2
6.3
Process Model ............................................................................................................................ 6-1
Methods, Tools and Techniques ................................................................................................ 6-2
Project Infrastructure.................................................................................................................. 6-2
v
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
6.4
Product Acceptance ................................................................................................................... 6-2
SECTION 7. SUPPORTING PROCESSES ............................................................................................. 7-1
7.1
Configuration Management ....................................................................................................... 7-1
7.2
Independent Verification and Validation ................................................................................... 7-1
7.3
Documentation ........................................................................................................................... 7-1
7.4
Quality Assurance ...................................................................................................................... 7-3
7.5
Reviews and Audits ................................................................................................................... 7-3
7.6
Problem Resolution .................................................................................................................... 7-3
7.6.1
TRB Membership............................................................................................................... 7-5
7.6.2
TRB Chairperson ............................................................................................................... 7-5
7.7
Contractor Management ............................................................................................................. 7-5
7.7.1
Contracting Process............................................................................................................ 7-6
7.7.2
Contractor Performance Monitoring .................................................................................. 7-6
7.8
Process Improvement ................................................................................................................. 7-6
7.8.1
Systems/Software Process Improvement Lead .................................................................. 7-6
7.8.2
Systems Engineering Process Group ................................................................................. 7-7
SECTION 8. ADDITIONAL PLANS ...................................................................................................... 8-1
8.1
Logistics Engineering ................................................................................................................ 8-1
8.1.1
System Performance .......................................................................................................... 8-2
8.1.2
System Availability ............................................................................................................ 8-2
8.1.3
Process Efficiency .............................................................................................................. 8-2
8.1.4
Technical Effectiveness ..................................................................................................... 8-2
8.1.5
System Effectiveness ......................................................................................................... 8-2
8.1.6
System Ownership Cost ..................................................................................................... 8-2
APPENDIX A. RBC MASTER SCHEDULE (MICROSOFT PROJECT)........................ APPENDICES-2
APPENDIX B. RBC FACILITIES PLAN ......................................................................... APPENDICES-3
APPENDIX C. RBC PROJECT TRAINING PLAN.......................................................... APPENDICES-4
APPENDIX D. RBC MEASUREMENT PLAN ................................................................ APPENDICES-5
APPENDIX E. RBC PRODUCT ENGINEERING AND QUALIFICATION PROCESS APPENDICES-6
APPENDIX F. RBC QUALITY ASSURANCE PLAN ..................................................... APPENDICES-7
APPENDIX G. RBC CONFIGURATION MANAGEMENT PLAN ................................ APPENDICES-8
LIST OF FIGURES
Figure
Figure 1-1.
Figure 1-2.
Figure 4-1.
Figure 4-2.
Figure 5-1.
Figure 6-1.
Figure 8-1.
Page
RBC System Overview .......................................................................................................... 1-1
Master Build Schedule ........................................................................................................... 1-3
RBC Project External Organizational Interfaces.................................................................... 4-1
RBC Project Internal Organizational Structure ...................................................................... 4-3
RBC Project Schedule Allocations ........................................................................................ 5-4
RBC Project Life Cycle Strategy ........................................................................................... 6-1
Components of System Operational Effectiveness ................................................................ 8-1
vi
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
LIST OF TABLES
Table
TABLE 1-1.
TABLE 4-1.
TABLE 4-2.
TABLE 5-1.
TABLE 5-2.
TABLE 5-3.
TABLE 7-1.
Page
RBC Program Budget .......................................................................................................... 1-3
Programmatic Roles and Responsibilies .............................................................................. 4-2
Project Roles and Responsibilities ....................................................................................... 4-4
Staff Resources by Development Phase .............................................................................. 5-4
RBC System Build Budget Allocation ................................................................................ 5-5
Management Control System Elements ............................................................................... 5-6
RBC Project Documentation ............................................................................................... 7-2
vii
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
This page intentionally left blank.
viii
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 1. OVERVIEW
1.1
PROJECT SUMMARY
IEEE Std 1058-1998 Guidance
The IEEE Std 1058-1998 provides no specific guidance on Project Summary (Subclause1.1). This section
may be tailored as needed to provide additional subsections in which a project may be more fully
described. For example, 1.1 Project Summary, 1.1.1 System Overview, 1.1.2 Purpose, Scope, and
Objectives, etc. The following is an example of the recommended content.
The Red/Black Controller (RBC) system provides encryption/decryption services for numerous
applications as part of communications systems, subsystems, and networks. The RBC system can be
applied at either the subscriber level to provide isolation between users of the network at different
clearance levels or differing need-to-know requirements, or at the link level to provide
encryption/decryption of all network control information and secondary encryption/decryption of all user
data. The RBC system does not operate in a stand-alone setting, but as a component in an overall
Command, Control, Communications, Computers, and Intelligence (C4I) system.
The RBC system consists of two interfacing hardware configuration items embedded in the host C4I
system. Figure 1-1 is an overview of the RBC system and its hosted Computer Software Configuration
Items (CSCIs).
Figure 1-1. RBC System Overview
The CSCIs consist of the Red Control CSCI (RCC) and Black Control CSCI (BCC) residing in RED and
BLACK processor components of the host C4I system. The purpose of the BCC is to handle the BLACK
data and BLACK control interfaces, handle the RCC interface, perform BLACK bypass data filtering and
control, and conduct self test. The purpose of the RCC is to handle the RED control interfaces, handle the
BCC interface, control the Cryptographic Module, perform security management, perform Alarm/Alert
processing, perform RED bypass data filtering and control, and conduct self test.
1-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
1.1.1
Purpose, Scope, and Objectives
IEEE Std 1058-1998 Guidance
(Subclause 1.1.1) Purpose, scope, and objectives
This subclause shall define the purpose, scope, and objectives of the project. This shall include a brief
statement of the business or system needs to be satisfied by the project, with a concise summary of the
project objectives, the products to be delivered to satisfy those objectives, and the methods by which
satisfaction will be determined. The project statement of purpose shall describe the relationship of this
project to other projects, and, as appropriate, how this project will be integrated with other projects or
ongoing work processes.
The RBC Project involves the evolutionary development of the RBC system, a multipurpose
cryptographic system hosted in a desktop configuration. The scope of the project consists of both the
hardware and software components delivered as an integrated system to sites specified by the Systems
Command (SYSCOM) Communications Security Office. RBC system provides the requisite
communications security for systems and equipment implementing a wireless communication network.
1.1.2 Assumptions and Constraints
IEEE Std 1058-1998 Guidance
(Subclause 1.1.2) Assumptions and constraints
This subclause shall describe the assumptions on which the project is based and imposed constraints on
project factors such as the schedule, budget, resources, components to be reused, acquirer components to
be incorporated, technology to be employed, and product interfaces to other products.
The RBC project will tailor a suite of standard work processes from the Space and Naval Warfare
(SPAWAR) Systems Center (SSC) San Diego organization standard processes as described in A
Description of the SSC San Diego Standard Process Assets (SPA), reference (a) and available on the SSC
San Diego Process Asset Library (PAL) at http://sepo.spawar.navy.mil. This Project Management Plan
(PMP) will state the general plans for the application of SSC San Diego policies, and processes for the
RBC project. Plans, policies, and processes described herein apply to the RBC project at SSC San Diego,
and its supporting contractors.
1.1.3 Project Deliverables
IEEE Std 1058-1998 Guidance
(Subclause 1.1.3) Project deliverables
This subclause shall list the work products that will be delivered to the acquirer, the delivery dates,
delivery locations, and quantities required to satisfy the terms of the project agreement. In addition, this
subclause shall specify the delivery media and any special instructions for packaging and handling. The
list of project deliverables may be incorporated into the document directly or by reference to an external
document such as a Contract Data Requirements List (CDRL) or a Product Parts List (PPL).
The deliverables for each increment of the RBC system will be documented in build plans. The build
plan for each increment is tailored from the Project Build Plan Template, reference (b), and serves as a
contract between the SYSCOM Communications Security Office and the RBC project on the content and
acceptance criteria for each build of the RBC system.
1-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
1.1.4
Master Schedule and Budget Summary
IEEE Std 1058-1998 Guidance
(Subclause 1.1.4) Schedule and budget summary
This subclause shall provide a summary of the schedule and budget for the project. The level of detail
should be restricted to an itemization of the major work activities and supporting processes as, for
example, those depicted by the top level of the work breakdown structure.
The SYSCOM Communications Security Office has established a Master Build Schedule as depicted in
Figure 1-2. Fiscal year budget allocations are contained in Table 1-1. The supporting Work Breakdown
Structure (WBS), cost, schedule, and staffing requirements for the each increment of the Master Build
Schedule are contained in Section 5.2 and Appendix A.
Figure 1-2. Master Build Schedule
TABLE 1-1. RBC PROGRAM BUDGET
Fiscal Year
1st QTR
2nd QTR
2002
3rd QTR
4th QTR
$0.50M
$0.50M
2003
$0.65M
$0.80M
$0.80M
$0.80M
2004
$0.80M
$0.80M
$0.80M
$0.80M
2005
$1.20M
$1.20M
$1.20M
$1.20M
2006
$1.00M
$1.00M
$1.00M
$1.00M
2007
$0.70M
$0.70M
1-3
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
1.2
EVOLUTION OF THE PLAN
IEEE Std 1058-1998 Guidance
(Subclause 1.2) Evolution of the Plan
This subclause shall specify the plans for producing both scheduled and unscheduled updates to this
planning document. Methods of disseminating the updates shall be specified. This subclause shall also
specify the mechanisms used to place the initial version under configuration management and to control
subsequent changes to the planning document.
The initiation, planning, control, and execution of the RBC project will follow the guidance of the SSC
San Diego Project Management Guide, reference (c). This PMP, implementing the guidance of reference
(c), has been tailored in format and content from the Institute of Electrical and Electronics Engineers
(IEEE) Standard for Software Project Management Plans, IEEE Standard1058-1998, reference (d).
Additional guidance is drawn from the Standard for Information Technology - Software Life Cycle
Processes, IEEE/Electronic Industries Association (EIA) 12207 Series, reference (e); Systems
Engineering – System Life Cycle Processes, International Organization for Standardization
(ISO)/International Electrotechnical Commission (IEC) 15288, reference (f); and Processes for
Engineering a System, Electronic Industries Alliance (EIA) Standard 632, reference (g). To ensure
application of the Systems/Software Engineering Management policy defined in reference (h), the PMP is
maintained in accordance with reference (a), and through the tailoring of the Project Management Plan
Template, reference (i).
The purpose of this PMP is to provide a documented plan for the management and control of the
organizational, developmental, and supporting processes necessary to the successful implementation of
the RBC Project. To that end the PMP is considered to be a living document. As such it is subject to
revision based on programmatic events as typified by a sudden changes in project or product
requirements, the encounter of risk events, or unexpected deviation from the planned course of action.
Revisions to the plan will follow reference (a) and the RBC Configuration Management Plan, Appendix
G.
1.3
DOCUMENT STRUCTURE
General Guidance
This section has been added to the template to help provide the reader of the final planning document an
understanding of the structure and content of the document without having to reference the IEEE Std
1058-1998.
This plan is organized as follows:
a. Section 1, Project Overview. This section provides an overview of the scope and objectives of
the project, the project’s assumptions and constraints, reference to the project deliverables,
schedule and budget, and a description of the evolution of the plan.
b. Section 2, References. This section provides a list of all documents, policies, templates,
processes, and other sources of information referenced in the plan.
c. Section 3, Definitions. This section contains the abbreviations and acronyms required to properly
understand this planning document.
d. Section 4, Project Organization. This section identifies interfaces to organizational entities
external to the project, the project’s internal organizational structure, and defines roles and
responsibilities for the project.
1-4
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
e. Section 5, Management Process. This section describes the planning, measurement, tracking,
reporting, risk control mechanisms needed to provide management control over the technical
processes and product quality, and appropriate project initiation and closeout procedures.
f. Section 6, Technical Process. This section describes the technical solution in terms of a process
model and implementation methods, tools, and techniques to be used to develop the various work
products, plans for establishing and maintaining the project infrastructure, and the product
acceptance.
g. Section 7, Supporting Processes. This section describes processes that are employed to facilitate
and control the technical processes and the state of the product. These include, but are not limited
to, configuration management, verification and validation, documentation, quality assurance,
reviews and audits, problem resolution, and contractor management, and methods to ensure
continuous process improvement.
h. Section 8, Additional Plans. This section addresses the logistic support strategy to be applied to
increase the system’s operational effectiveness.
i. Appendix A. RBC Master Schedule (Microsoft Project)
j. Appendix B. RBC Facilities Plan
k. Appendix C. RBC Project Training Plan
l. Appendix D. RBC Measurement Plan
m. Appendix E. RBC Product Engineering and Qualification Process
n. Appendix F. RBC Quality Assurance Plan
o. Appendix G. RBC Configuration Management Plan
1-5
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
This page intentionally left blank.
1-6
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 2. REFERENCES
IEEE Std 1058-1998 Guidance
(Clause 2) References
This clause shall provide a complete list of all documents and other sources of information referenced in
the document. Each document should be identified by title, report number, date, author, path/name for
electronic access, and publishing organization. Other sources of information, such as electronic files,
shall be identified using unique identifiers such as date and version number. Any deviations from
referenced standards or policies shall be identified and justifications shall be provided.
2.1
STANDARDS AND DOCUMENTS
The standards and documents listed below are referenced in this document:
a. A Description of the SSC San Diego Standard Process Assets (SPA), PR-OPD-35, SSC San
Diego
b. Project Build Plan Template, TM-PP-02, SSC San Diego
c. SSC San Diego Project Management Guide, PR-OPD-29, SSC San Diego
d. Institute of Electrical and Electronics Engineers (IEEE) Standard for Software Project
Management Plans, IEEE Standard 1058-1998, IEEE, December 1998
e. Standard for Information Technology - Software Life Cycle Processes, IEEE/Electronic
Industries Association (EIA) 12207 Series, IEEE/ EIA, March 1998
f. Systems Engineering – System Life Cycle Processes, International Organization for
Standardization (ISO)/International Electrotechnical Commission (IEC) 15288, ISO/IEC
15288:2002(E), Nov 2002
g. Processes for Engineering a System, Electronic Industries Alliance (EIA) Standard 632,
ANSI/EIA-632-1998, January 1999
h. Systems/Software Engineering Management Policy, DC-OPD-09, SSC San Diego
i. Project Management Plan Template, TM-PP-01, SSC San Diego
j. Incremental Life Cycle Schedule Template, TM-SPP-06, SSC San Diego
k. SSC San Diego Training Program Process, PR-OT-01, SSC San Diego
l. Department/Project Training Plan Template, TM-TP-01, SSC San Diego
m. Measurement and Analysis Process (Expert Mode), PRX-MA-01, SSC San Diego
n. Software Measurement Plan Template, TM-SPTO-03, SSC San Diego
o. Requirements Management Guidebook, Naval Air Systems Command, September 1998
p. Risk Management Process, PR-SPP-04, SSC San Diego
q. Product Engineering and Qualification Process, PR-TS-01, SSC San Diego
r. Software Test Planning and Management Guide, PR-SPE-03, SSC San Diego
s. Configuration Management Process, PR-CM-01, SSC San Diego
t. Configuration Management Plan Template, TM-CM-01, SSC San Diego
u. Quality Assurance Process, PR-PPQA-01, SSC San Diego
v. Quality Assurance Plan Template, TM-PPQA-01, SSC San Diego
w. Integrated Software Management/Software Product Engineering/Inter-group Coordination
Implementation Guide, PR-ISM-02, SSC San Diego
2-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
x. Contractor Acquisition and Performance Monitoring Process, PR-SAM-01, SSC San Diego
y. Decision Analysis and Resolution Process (Expert Mode), PRX-DAR-01, SSC San Diego
z. Designing and Assessing Supportability in DoD Weapon Systems – A Guide to Increased
Reliability and Reduced Logistics Footprint, Office of the Secretary of Defense (OSD), May
2003
2.2
DEVIATIONS AND WAIVERS
Deviations and/or waivers from reference (h), or the project’s documented standard processes or
procedures will be defined in the individual build plans as necessary and approved by agreement between
the project manager and the program manager.
2-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 3. DEFINITIONS
IEEE Std 1058-1998 Guidance
(Clause 3) Definitions
This clause shall define, or provide references to, documents containing the definition of all terms and
acronyms required to properly understand this planning document.
The abbreviations and acronyms used throughout this document are listed below:
ACWP
Actual Cost of Work Performed
AD
Architectural Design
BCC
Black Controller CSCI
BCWP
Budgeted Cost of Work Performed
BCWS
Budgeted Cost of Work Scheduled
CDRL
Contract Data Requirements List
CM
Configuration Management
COR
Contracting Officer's Representative
CSCI
Computer Software Configuration Item
CT
Code and Unit Test
C4I
Command, Control, Communications, Computers, and Intelligence
DBDD
DataBase Design Description
DCR
Document Change Request
DD
Detailed Design
DID
Data Item Description
DoN
Department of the Navy
EIA
Electronic Industries Association or Alliance
HWCI
Hardware Configuration Item
IEEE
Institute of Electronics and Electrical Engineers
IPR
In-Process Review
IR
Information Repository
IRS
Interface Requirements Specification
IT
Integration Test
IV&V
Independent Verification and Validation
LCCB
Local Configuration Control Board
MCS
Management Control System
MENS
Mission Element Needs Statement
MIL-STD
Military Standard
OPNAV
Office of the Chief of Naval Operations
OPTEVFOR
Operational Test and Evaluation Force
PAL
Process Asset Library
P/CR
Problem/Change Report
PE&Q
Product Engineering and Qualification
3-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
PM
PMP
PPL
PRP
QA
QT
RBC
RCC
RA
RD
RM
SCCB
SCM
SCR
SDD
SDF
SDL
SEN
SEPG
SEPO
SMP
SOE
SOW
SPA
SPAWAR
SPI
SPP
SPTO
SQA
SQT
SRS
SSC
STD
STP
SYSCOM
T&E
TRB
VPO
WBS
Project Manager
Project Management Plan
Product Parts List
Procurement Requirements Package
Quality Assurance
Qualification Test
Red/Black Controller
Red Controller CSCI
Requirements Analysis
Requirements Definition
Requirements Management
System Configuration Control Board
Software Configuration Management
System Change Request
Software Design Description
Software Development File
Software Development Library
Software Engineering Notebook
Systems Engineering Process Group
Systems Engineering Process Office
Software Measurement Plan
System Operational Effectiveness
Statement of Work
Software Process Assets document
Space and Naval Warfare
Systems Process Improvement
Software Project Planning
Software Project Tracking and Oversight
Software Quality Assurance
System Qualification Test
Software Requirements Specification
SPAWAR Systems Center
Software Test Description
Software Test Plan
Systems Command
Test and Evaluation
Technical Review Board
Virtual Project Office
Work Breakdown Structure
3-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 4. PROJECT ORGANIZATION
4.1
EXTERNAL INTERFACES
IEEE Std 1058-1998 Guidance
(Subclause 4.1) External interfaces
This subclause shall describe the organizational boundaries between the project and external entities.
This should include, but is not limited to, the following: the parent organization, the acquiring
organization, subcontracted organizations, and other organizational entities that interact with the
project. Representations such as organizational charts and diagrams may be used to depict the project’s
external interfaces.
External organizational interfaces and the chain-of-command for the RBC Project are defined in Figure 4-1.
Organizational entities in italics are located within the SSC San Diego complex.
Figure 4-1. RBC Project External Organizational Interfaces
The responsibilities of the organizational entities and key positions shown in Figure 4-1 are defined in
Table 4-1.
4-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
TABLE 4-1. PROGRAMMATIC ROLES AND RESPONSIBILIES
POSITION
ROLES/RESPONSIBILITIES
Sponsor
Office of the Chief of Naval Operations (OPNAV)-level organization
providing Mission Element Need Statement (MENS) and Department of
the Navy (DoN) budget.
Systems Command (SYSCOM)
Communications Security Office
SYSCOM-level organization tasked by OPNAV to perform system
acquisition to meet the MENS for secure communication systems.
Program Manager
SYSCOM-level manager within the Communications Security Office
assigned responsibility to direct total RBC system acquisition
(hardware/software).
System Configuration Control
Board (SCCB)
SYSCOM-level board responsible for the RBC system configuration
(hardware/software).
Operational Test and Evaluation
Force (OPTEVFOR)
OPTEVFOR is the Navy's sole independent agency for operational test
and evaluation. OPTEVFOR is responsible to OPNAV for the evaluation
of a system's ability to meet the MENS.
Independent Verification and
Validation (IV&V) Organization
Program-level organization charged with the responsibility of providing
resources and management for IV&V functions. Organized such that
they report to the Program Manager through a chain of command
separate from SSC San Diego’s.
SSC San Diego Senior Management
A senior manager (i.e., Executive Director, Department Head, or possibly
a Division Head) providing infrastructure resources (e.g., facilities,
admin, contracting, supply) to support an internal entity such as a
development/maintenance organization for the RBC Project.
System Test Organization
Organizational entity charged with system-level acceptance testing.
Reports directly to the SYSCOM Communications Security Office.
System Test Manager
Office within the System Test Organization charged with responsibility
for RBC system testing. Answers directly to the Program Manager.
RBC Project
SSC San Diego organizational entity managing a defined group of
activities with the responsibility to meet one or more specific system
objectives tasked by the Program Manager. The project has its own
funding, accounting, and schedules.
RBC Project Manager
An SSC San Diego ‘manager’ responsible to the Program Manager and to
SSC San Diego Senior Management for specific tasked RBC project
objectives.
Systems Engineering Process Office
(SEPO)
SSC San Diego’s organization responsible for facilitating systems and
software engineering process improvement.
Department Systems Engineering
Process Group (SEPG)
Professional staff providing Systems/Software Process Improvement
(SPI) leadership to the SSC San Diego Department to which the RBC
project is assigned.
Department SPI Agent
Representative from the SSC San Diego department to which the RBC
project is assigned. The agent is responsible for co-ordination with
SEPO for process improvement.
4-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
4.2
INTERNAL STRUCTURE
IEEE Std 1058-1998 Guidance
(Subclause 4.2) Internal structure
This subclause shall describe the internal structure of the project organization to include the interfaces
among the units of the development team. In addition, the organizational interfaces between the project
and organizational entities that provide supporting processes, such as configuration management, quality
assurance, and verification and validation, shall be specified in this subclause. Graphical devices such
as organizational charts or diagrams should be used to depict the lines of authority, responsibility, and
communication within the project.
The RBC Project organizational structure internal to SSC San Diego is defined in Figure 4-2.
Figure 4-2. RBC Project Internal Organizational Structure
4.2.1 The Project Manager
The RBC Project Manager (PM) has full authority and is responsible and accountable for all aspects of
the projects assigned by the SYSCOM Communications Security Office.
4.2.1.1 Scope of Authority. The RBC PM represents SSC San Diego on all issues within the RBC
organization, including contractors, and subcontractors. The RBC PM’s authority extends from initial
planning though all aspects of the performance including technical direction of project personnel. The
RBC PM has full authority over the technical managers and direct access to SSC San Diego senior
management to acquire and commit the necessary resources to meet the requirements of any or all work
assigned. The RBC PM exercises complete and final authority over contract activities in accordance with
SSC San Diego policies and procedures. The RBC PM also has full authority over the contractors and
implements this authority via formal contractual documents maintained by the SSC San Diego’s contract
administrator and the respective Contracting Officer’s Representative (COR).
4.2.1.2 Scope of Responsibility. The RBC PM is accountable to the SYSCOM Communications
Security Office, for the conduct of the assigned projects including contractor efforts. The PM is the
SYSCOM Communications Security Office’s Point-of-Contact for all issues related to the RBC system.
The RBC PM directs the Administrative Office staff in the performance of assigned responsibilities.
4-3
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
4.2.1.3 Internal Responsibilities. The RBC PM is responsible for all technical, quality, cost and
schedule aspects of the tasks assigned in the current SYSCOM Communications Security Office
Statement of Work (SOW). The RBC PM will establish and approve a schedule showing major activities
needed to establish full RBC system capability in accordance with Figure 1-2. General responsibilities
are listed below:
a. Approve all cost and schedule-related planning documents.
b. Approve all organizational work and WBS.
c. Control or delegate control of all organizational resources.
d. Establish organizational budgets.
e. Establish organizational policies.
f. Appoint and evaluate all technical managers.
g. Monitor and report all project performance including the approval of monthly progress reports
and cost summary reports.
h. Evaluate trade-offs prior to major decisions and approve any deviations to approved plans.
i. Assist group managers in choosing alternative courses of action to resolve problems.
j. Identify project issues requiring formally documented decision analysis and resolution,
k. Monitor and assure that all corrective actions are completed in the specified time.
l. Assume the chair for the Local Configuration Control Board (LCCB)
4.2.1.4 External Responsibilities. The RBC PM is the principal point of contact for maintaining liaison
with the SYSCOM Communications Security Office, coordinating and supporting meetings, conducting
program reviews, supporting the COR, approving all deliverables and managing all subcontractor activity.
The RBC PM attends all program meetings and assures the attendance of the required key personnel. The
RBC PM reviews and approves all deliverable work products at critical in-process junctures as well as at
completion.
4.3
PROJECT ROLES AND RESPONSIBILITIES
IEEE Std 1058-1998 Guidance
(Subclause 4.3) Roles and responsibilities
This subclause shall identify and state the nature of each major work activity and supporting process and
identify the organizational units that are responsible for those processes and activities. A matrix of work
activities and supporting processes vs. organizational units may be used to depict project roles and
responsibilities.
The RBC project roles and responsibilities, including, but not limited to, the positions shown in Figure 42, are defined in Table 4-2.
TABLE 4-2. PROJECT ROLES AND RESPONSIBILITIES
POSITION
RBC Project Manager
ROLES/RESPONSIBILITIES
An SSC San Diego ‘manager’ responsible to the Program Manager for
specific tasked system objectives. For the RBC project, the Project Manager
acts as the LCCB chairperson and the Risk Manager. As Risk Manager, the
PM coordinates risk identification, assessments, contingency planning, and
the maintenance of the risk database.
4-4
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
POSITION
ROLES/RESPONSIBILITIES
Local Configuration Control
Board (LCCB)
Project Manager’s project-level configuration control board controlling the
configurations. Interfaces with and is subordinate to the SCCB. The Project
Manager serves as the LCCB Chair.
Project SPI Lead
Project member who facilitates the project’s process improvement effort,
collecting measurements and reporting status of the effort to the Project
Manager and the Dept SPI Agent.
Administrative Office
The Project Manager’s administrative and financial support staff whose
responsibilities include budget tracking, purchasing, and various contract
items.
Contracting Officer’s
Representative (COR)
Office responsible for compliance of RBC contracts to SSC San Diego and
DoN acquisition regulations. Performs contract oversight.
Technical Managers
Collective name for the Project Manager’s technical supervisory team
comprised of the Development Manager, T&E Manager, CM Manager, and
QA Manager.
Technical Review Board (TRB)
A working group chartered to resolve both programmatic and technical
issues and to submit recommendations to the Project Manager.
Development Manager
An organizational technical manager responsible for product development,
who reports to the Project Manager.
Development Group
Collective name of the engineering staff responsible for RBC product
development.
Requirements Team
Staff responsible for the management of the RBC requirements database.
Design Team
Staff responsible for the RBC architecture and design.
Implementation Team
Staff responsible for code, and/or reuse component selection, and unit test.
Test and Evaluation (T&E)
Manager
An organizational technical manager, responsible for CSCI and Integration
T&E, who reports to the Project Manager .
T&E Group
Collective name of the engineering staff responsible for CSCI integration
and testing.
CSCI Test Team
Engineering staff responsible for internal CSCI Testing.
Integration Test Team
Engineering staff responsible for internal CSCI/Hardware Configuration
Item (HWCI) Testing.
Delivery Team
Engineering staff responsible for on-site deliveries, training, and testing.
Configuration Management
(CM) Manager
An organizational technical manager responsible for CM, who reports to the
Project Manager.
CM Group
Collective name of the engineering staff responsible for CM functions.
Librarian
Member of engineering staff who is keeper of document and program
baselines (check in/out)
Quality Assurance (QA)
Manager
An organizational technical manager, responsible for QA functions, that
reports to the Project Manager.
QA Group
Collective name of the engineering staff responsible for QA functions.
4-5
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
This page intentionally left blank.
4-6
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 5. MANAGEMENT PROCESS
5.1
START-UP
IEEE Std 1058-1998 Guidance
(Subclause 5.1) Project start-up plan
This subclause shall specify the estimation plan, staffing plan, resource acquisition plan, and training
plan. Depending on the size and scope of the project, these plans may be incorporated directly or by
reference to other plans.
A SYSCOM Communications Security Office Task containing a build-specific SOW and funding
information initiates project tasking for each incremental build of the RBC system at SSC San Diego.
5.1.1 Estimation
IEEE Std 1058-1998 Guidance
(Subclause 5.1.1) Estimation plan
This subclause shall specify the cost and schedule for conducting the project as well as methods, tools,
and techniques used to estimate project cost, schedule, resource requirements, and associated confidence
levels. In addition, the basis of estimation shall be specified to include techniques such as analogy, rule
of thumb, or local history and the sources of data. This subclause shall also specify the methods, tools,
and techniques that will be used to periodically re-estimate the cost, schedule, and resources needed to
complete the project. Re-estimation may be done on a monthly basis and/or periodically as necessary.
To develop RBC system build schedules, estimates are developed by using the Management Control System
(MCS) cost-estimating tool cited in Section 5.3. The Incremental Life Cycle Schedule Template, reference
(j), is analyzed and tailored based on the estimate results. The staffing requirements for each task are
abstracted from the macro estimate and partitioned to the detailed entries of the Master Schedule, Appendix
A. Start and duration times, together with prerequisite and other timing data, are extracted from the estimate
and input to the Microsoft Project plan to generate schedules. The resulting schedules are then analyzed for
reasonableness to ensure that they fit into a compliant overall schedule. Results that are determined to be
non-compliant are revised and then input back into the estimating process.
5.1.2 Staffing
IEEE Std 1058-1998 Guidance
(Subclause 5.1.2) Staffing plan
This subclause shall specify the number of staff required by skill level, the project phases in which the
numbers of personnel and types of skills are needed, the source of personnel and the duration of need.
Resource Gantt charts, resource histograms, spreadsheets, and tables may be used to depict the staffing
plan by skill level, by project phase, and by aggregations of skill levels and project phases.
Staffing for the RBC project will be comprised of a mix of the civil service personnel currently in place
and contractor personnel acquired through an open competition for a support contract. Overall staffing
requirements and their allocation are defined paragraph 5.2.3.
5-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
5.1.3
Resource Acquisition
IEEE Std 1058-1998 Guidance
(Subclause 5.1.3) Resource acquisition plan
This subclause shall specify the plan for acquiring the resources in addition to personnel needed to
successfully complete the project. The resource acquisition plan should include a description of the
resource acquisition process, including assignment of responsibility for all aspects of resource
acquisition. The plan should include, but not be limited to, acquisition plans for equipment, computer
hardware and software, training, service contracts, transportation, facilities, and administrative and
janitorial services. The plan should specify the points in the project schedule when the various
acquisition activities will be required. Constraints on acquiring the necessary resources shall be
specified.
Non-staff resource requirements and the means of acquisition are defined in the RBC Facilities Plan,
Appendix B.
5.1.4 Staff Training
IEEE Std 1058-1998 Guidance
(Subclause 5.1.4) Project staff training plan
This subclause shall specify the training needed to ensure that necessary skill levels in sufficient numbers
are available to successfully conduct the project. The training schedule shall include the types of
training to be provided, numbers of personnel to be trained, entry and exit criteria for training, and the
training method (e.g., lectures, consultations, mentoring, or computer-assisted training). The training
plan should include training as needed in both technical and managerial skills.
Personnel assigned to the RBC project are required to complete, or waive, technical training to enable
them to carry out their assignments proficiently. In addition, personnel newly assigned to the
organization are required to familiarize themselves with both the project and the common processes used
to support the RBC project. The RBC Project Training Plan, Appendix C, was developed in accordance
with the SSC San Diego Training Program Process, reference (k). The process establishes the
requirement for a Department/Project Training Plan. The Department/Project Training Plan Template,
reference (l), was tailored to develop Appendix C.
5.2
WORK PLANNING
IEEE Std 1058-1998 Guidance
(Subclause 5.2) Work plan
This clause shall specify the work activities, schedule, resources, and budget details for the project.
The following paragraphs provide a working management plan for the acquisition of the RBC system.
5.2.1 Work Activities
IEEE Std 1058-1998 Guidance
(Subclause 5.2.1) Work activities
This subclause shall specify the various work activities to be performed in the project. A work breakdown
structure shall be used to depict the work activities and the relationships among work activities. Work
activities should be decomposed to a level that exposes all project risk factors and allows accurate
estimate of resource requirements and schedule duration for each work activity. Work packages should
be used to specify, for each work activity, factors such as the necessary resources, estimated duration,
work products to be produced, acceptance criteria for the work products, and predecessor and successor
5-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
work activities. The level of decomposition for different work activities in the work breakdown structure
may be different depending on factors such as the quality of the requirements, familiarity of the work, and
novelty of the technology to be used.
The WBS for the RBC Project is contained in Appendix A. The WBS identifies the needed tasks,
resource allocations, and cost estimates in a Microsoft Project format that was tailored from reference (j).
The individual builds have their own supporting Microsoft Project plans that provide roll-up data to the
master Microsoft Project plan in Appendix A. The build plans will be tailored from reference (b). Issues
requiring formally documented decision analysis and resolution are entered as discrete WBS tasks to
ensure tracking. Events requiring formally documented decision analysis include decisions on
architectural design trade-offs, supplier selection, resolution of high risk issues, commercial off-the-shelf
product selection, support tool selection, and make-or-buy decisions. The project manager specifies the
decision analysis and resolution events.
5.2.2 Schedule Allocation
IEEE Std 1058-1998 Guidance
(Subclause 5.2.2) Schedule allocation
This subclause shall provide scheduling relationships among work activities in a manner that depicts the
time-sequencing constraints and illustrates opportunities for concurrent work activities. Any constraints
on scheduling of particular work activities caused by factors external to the project shall be indicated in
the work activity schedule. The schedule should include frequent milestones that can be assessed for
achievement using objective indicators to assess the scope and quality of work products completed at
those milestones. Techniques for depicting schedule relationships may include milestone charts, activity
lists, activity Gantt charts, activity networks, critical path networks, and PERT.
Figure 5-1 allocates development activities within the individual builds identified in Figure 1-2. Each
build will be addressed in more detail in the build plan identifying the individual build’s requirements,
schedule, resources, and acceptance criteria. The development activities included in Figure 5-1 are
Requirements Analysis (RA), Architectural Design (AD), Detailed Design (DD), Code and Unit Test
(CT), Integration Test (IT), and Qualification Test (QT).
Note that RA and AD are conducted during a common schedule phase.
5.2.3 Resource Allocation
IEEE Std 1058-1998 Guidance
(Subclause 5.2.3) Resource allocation
This subclause shall provide a detailed itemization of the resources allocated to each major work activity
in the project work breakdown structure. Resources shall include the numbers and required skill levels of
personnel for each work activity. Resource allocation may include, as appropriate, personnel by skill
level and factors such as computing resources, tools, special testing and simulation facilities, and
administrative support. A separate line item should be provided for each type of resource for each work
activity. A summary of resource requirements for the various work activities should be collected from the
work packages of the work breakdown structure and presented in tabular form.
Required staffing allocations by development phase are defined in Table 5-1. The table provides
guidance for staff allocations for the overall project. Facilities resources, including floor space, lab
configuration, hardware, and tool requirements are defined in the RBC Facilities Plan, Appendix B.
5-3
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
Figure 5-1. RBC Project Schedule Allocations
TABLE 5-1. STAFF RESOURCES BY DEVELOPMENT PHASE
Labor Category
RA & AD
DD
CT
IT & QT
Project Manager
1
1
1
1
Systems Engineer
1
1
1
1
Hardware Engineer
1
1
1
1
Software Engineer
5
7
7
5
CM Specialist
2
2
2
2
QA Specialist
1
1
1
1
Senior Test Engineer
1
1
1
1
Test Engineer
2
2
2
2
Facilities Administrator
1
1
1
1
Hardware installation specialist
1
1
1
1
Subtotals
16
18
18
16
5-4
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
5.2.4
Budget Allocation
IEEE Std 1058-1998 Guidance
(Subclause 5.2.4) Budget allocation
This subclause shall provide a detailed breakdown of necessary resource budgets for each of the major
work activities in the work breakdown structure. The activity budget shall include the estimated cost for
activity personnel and may include, as appropriate, costs for factors such as travel, meetings, computing
resources, tools, special testing and simulation facilities, and administrative support. A separate line
item shall be provided for each type of resource in each activity budget. The work activity budget may be
developed using a spreadsheet and presented in tabular form.
Table 5-2 presents the RBC project budget and allocates the funding to the individual builds and their
development activities.
TABLE 5-2. RBC SYSTEM BUILD BUDGET ALLOCATION
Build
Phase
Budget (K$)
Build 01
RA
$
552
AD
$ 2,016
DD
$
737
CT
$
799
IT and QT
$ 1,106
Total
$ 5,210
$ 5,210
Build 02
RA
$
300
AD
$
209
DD
$ 1,432
CT
$ 1,551
IT and QT
$ 2,148
Total
$ 5,640
$ 5,640
Build 03
RA
$
300
AD
$
233
DD
$ 1,601
CT
$ 1,734
IT and QT
$ 2,401
Total
$ 6,269
$ 6,269
Project Total
$17,119
5-5
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
5.3
PROJECT CONTROLS
IEEE Std 1058-1998 Guidance
(Subclause 5.3) Control plan
This subclause shall specify the metrics, reporting mechanisms, and control procedures necessary to
measure, report, and control the product requirements, the project schedule, budget, and resources, and
the quality of work processes and work products. All elements of the control plan should be consistent
with the organization’s standards, policies, and procedures for project control as well as with any
contractual agreements for project control.
The SYSCOM Communications Security Office provides direction to SSC San Diego through formally
established Plans Of Action and Milestones, memoranda, and SYSCOM Communications Security Office
Tasks. The SSC San Diego RBC Project organization provides current status to the SYSCOM
Communications Security Office through the reviews, audits, reports, and working interchanges established
for the program. The key factors that contribute to the SSC San Diego RBC Project management are the
processes of planning, scheduling, performance measurement, risk mitigation, variance analysis, and
corrective action. Under the direction of the PM, the technical managers develop detailed plans based on
established work assignments for specific projects. The MCS tools are used to document and track the work
against major program milestones and provide work performance measurement against costs incurred. To
ensure the necessary level of tracking and oversight and the application of reference (h), the RBC
Measurement Plan (SMP), Appendix D, was developed in accordance with the Measurement and
Analysis Process (Expert Mode), reference (m), and through the tailoring of the Software Measurement
Plan Template, reference (n). The RBC SMP includes periodic reviews, monthly status reports, and audits.
Periodic reviews are conducted to assess the risks, to initiate risk analysis, and to establish risk mitigation
methods. Quality Assurance's (QA) function is to ensure that these transactions are fully recorded and
traceable though the project life. Deviations from the baseline cost and schedule data are subjected to
variance analysis. Corrective action items are documented for each significant variance. Corrective action
items are established, logged, and tracked until successfully resolved. Directives are issued through the
formal planning, scheduling, and communications media.
The MCS tools, supported by the WBS, permit cost, schedule, performance and quality to be reviewed at
any level. Table 5-3 identifies the primary tools that support program management and are part of the MCS.
TABLE 5-3. MANAGEMENT CONTROL SYSTEM ELEMENTS
Tool
Production
Control
Description
Resource
Mgmt
Cost
Mgmt
Schedule
Mgmt
COSTAR
Cost Estimating
x
x
x
Microsoft Project
Plans/Tracking
x
x
x
Microsoft Excel
Plans/Tracking
x
x
x
Microsoft Powerpoint
Documentation
x
x
x
x
Microsoft Word
Documentation
x
x
x
x
Microsoft Access
P/CR and SCR Tracking
x
Microsoft Outlook
E-Mail
x
x
x
x
Requisite Pro
Requirements Mgmt
x
Risk Radar
Risk Tracking
x
x
x
x
5-6
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
5.3.1
Requirements Control
IEEE Std 1058-1998 Guidance
(Subclause 5.3.1) Requirements control plan
This subclause shall specify the control mechanisms for measuring, reporting, and controlling changes to
the product requirements. This subclause shall also specify the mechanisms to be used in assessing the
impact of requirements changes on product scope and quality, and the impacts of requirements changes
on project schedule, budget, resources, and risk factors. Configuration management mechanisms shall
include change control procedures and a change control board. Techniques that may be used for
requirements control include traceability, prototyping and modeling, impact analysis, and reviews.
The Requirements Team is responsible for the RBC project requirement’s process. The Requirements
Team will develop a Requirements Management (RM) process based on database technology. The team
will establish the overall schema for the requirements database and for providing informal training, as
required. To ensure application of reference (h), the requirements management process will apply
guidance from the Requirements Management Guidebook, reference (o). The Requirements Team will
enter requirements data into the database, and will produce requirements traceability matrices. RA and
subsequent Requirements Definition (RD) is performed in accordance with the requirements process
described in the RBC Product Engineering and Qualification (PE&Q) Process, Appendix E to this
document. The allocation and baselining of requirements to individual builds is the responsibility of the
LCCB.
Each technical manager will ensure the integrity of the requirements data entered and that requirement bidirectional traceability matrices are built for each major document (such as Software Requirements
Specification (SRS), Interface Requirements Specification (IRS), Software Design Description (SDD),
and for the test specifications including the Software Test Plan (STP), the Software Test Descriptions
(STD), etc.). As traceability matrices are produced, the Requirements Team will be able to determine
whether all requirements for each phase of each build have been met.
5.3.2 Schedule Control
IEEE Std 1058-1998 Guidance
(Subclause 5.3.2) Schedule control plan
This subclause shall specify the control mechanisms to be used to measure the progress of work
completed at the major and minor project milestones, to compare actual progress to planned progress,
and to implement corrective action when actual progress does not conform to planned progress. The
schedule control plan shall specify the methods and tools that will be used to measure and control
schedule progress. Achievement of schedule milestones should be assessed using objective criteria to
measure the scope and quality of work products completed at each milestone.
The following paragraphs define the management approach for schedule control of the RBC Project.
5.3.2.1 Schedule Tracking. Progress is charted on a monthly basis. Schedule performance data is
generated at the task level and compared to the proposed schedule. Reports are generated that provide data
on performance-to-date and projected future performance. In addition, deviations of both current and future
milestones from proposed milestone dates are flagged. The actual start dates, completion dates, task
completion percentages based on earned value algorithms, and actual dollar amounts expended on each task
are entered into the Microsoft Project plan for each product component and the project overall.
5.3.2.2 Schedule Performance Reports. Schedule status information is measured against the required
schedule dates, and reports on performance-to-date and projected future milestone dates are made.
Deviations of "to-date" and "future-milestone-dates" from "required-dates" are flagged. Using MS Project
for each product component, the Administrative Office generates variance analysis reports by comparing
5-7
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
Actual Cost of Work Performed (ACWP), Budgeted Cost of Work Scheduled (BCWS), Budgeted Cost of
Work Performed (BCWP), and Estimate at Completion.
5.3.2.3 Schedule Reviews. QA reports and Configuration Management (CM) status accounting reports are
reviewed in relationship with the schedule performance reports at multiple detail levels and timing intervals
to provide management early visibility into potential schedule problems and/or schedule risks.
At each review level, schedule problems and/or risks are identified. If an actual problem (schedule
variance) occurs, a problem resolution analysis is made to include: problem severity, schedule impact
(domino effect), possible resolutions, and risk associated with each alternative.
Depending upon the reviewer's authority level and the nature of the required corrective action, the reviewer
either directs corrective action or recommends corrective action to a higher authority level. This process
applies to all contractor activities as well.
5.3.2.4 Progress Variance Monitoring. Actual progress can differ from the planned progress for many
reasons. The technical managers have the responsibility to identify schedule deviation causes and trends at
the task level and correct the deviations. Deviations that are beyond a technical manager’s capabilities to
resolve are brought to the PM’s attention.
5.3.2.5 Progress Variance Resolution. Once a schedule variance is identified and quantified,
management has several options from which to choose for deviation resolution. Depending on the cause
of the deviation, the action may be resource reallocation, rescheduling the task or set of tasks, or
correcting a performance problem.
5.3.2.6 Follow-Up on Corrective Action. The MCS tools are used to both identify the initial schedule
deviation and to analyze the corrective action results. Corrective action items are closely monitored to
ensure that they are effectively recovering the schedule variance before milestones or the master schedule
are jeopardized.
5.3.3 Budget Control
IEEE Std 1058-1998 Guidance
(Subclause 5.3.3) Budget control plan
This subclause shall specify the control mechanisms to be used to measure the cost of work completed,
compare planned cost to budgeted cost, and implement corrective action when actual cost does not
conform to budgeted cost. The budget control plan shall specify the intervals at which cost reporting will
be done and the methods and tools that will be used to manage the budget. The budget plan should
include frequent milestones that can be assessed for achievement using objective indicators to assess the
scope and quality of work products completed at those milestones. A mechanism such as earned value
tracking should be used to report the budget and schedule plan, schedule progress, and the cost of work
completed.
The following paragraphs define the management approach for budget control of the RBC Project.
5.3.3.1 Cost Management. To ensure that the PM has the control necessary to accomplish the project
objectives, the Administrative Office is assigned total budget tracking responsibility. The PM delegates
specific cost management duties to his Administrative Office staff while retaining review and approval
authority for all cost-related efforts.
The primary building block within the methodology is the WBS as detailed in the project’s Microsoft
Project Plan as derived from the organization’s standard Microsoft Project plan template, reference (j), or
the Enterprise Resource Planning WBS Template. The cost estimating tool of the MCS is used for the cost
estimating process while Microsoft Project is used for tracking the project costs.
Once a valid cost baseline is established, detailed schedules are utilized to provide visibility and to be the
basis for establishing the cost of work performed. This determination is supplied monthly to establish
5-8
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
measurement points for cost and schedule adherence. To ensure immediate and appropriate attention, cost
and schedule variances are automatically triggered for review in the integrated review process.
5.3.3.2 Methods to Ensure Cost Adherence. Management of costs and risks is a focal point of the cost
adherence plan. A comprehensive set of processes, tools, and practices is coupled with contingency
planning to ensure that costs and risks are closely monitored and controlled.
5.3.3.3 Cost Control. Cost management methodology utilizes the MCS tools to track and measure the
cost of work being performed. Deviations are highlighted for immediate management attention. Group
managers employ input in the form of cost and completion percentages via monthly management reports to
develop a BCWP. This is a measure of budget adherence that is used to determine where management
attention must be focused.
5.3.3.4 Contractor Cost Control. Cost management practices for contractors include formal methods for
monitoring and controlling contractor cost performance and minimizing risk. Specific contractor tasks are
identified and are detailed in the appropriate Microsoft Project plan. Enforced flow-down of technical,
schedule, and contractual requirements is incorporated into individual statements of work in each delivery
order. Contract management has been given the dual responsibility of ensuring that 1) lines of
communication remain open for the exchange of information and 2) negotiated agreements are not
compromised.
The RBC Project uses a review and reporting system that requires contractor evaluation and is consistent
with contracting requirements. A monthly contractor’s status report including any variances in cost,
schedule, or technical performance will be included in the monthly program reviews. The same problem
identification and resolution procedures used by the CM Group are extended to the subcontractor, to ensure
management visibility and to guarantee that proper and prompt attention is given to risk management and
reduction on a program-wide basis.
The technical managers manage the contractor costs directly. They are chartered with the responsibility of
monitoring contractor costs and schedules for adherence to budget. They will report directly to the PM and
the COR, thus ensuring that the PM will have immediate insight into all contractor cost control.
5.3.3.5 Cost Variance Measurement. The MCS is the vehicle for tracking cost variances. At the start of
a project, or a baseline revision, WBS levels are entered into a Microsoft Project plan and baselined to form
the framework for cost-variance measurement.
Milestones are monitored, and noted variances reviewed to determine program impact and establish
corrective action items. Corrective action items are tracked to completion. Out-of-tolerance variances are
assessed to the responsible technical manager and reviewed with the PM. Internal cost and schedule
reviews are held for the duration of the effort. Reviews assess cost trends and analyze cost and schedule
variances, with variances determined by comparing elements of BCWP against ACWP and BCWS. If a
variance reaches a predetermined threshold, as defined in the risk management database, it is brought to the
immediate attention of the responsible technical manager for assessment and formulation of corrective
action. Threshold limits are set by the PM and documented in the related risk management database entries
and adjusted, as appropriate, based on trend analysis and risk identification. Variances, either positive or
negative, are automatically triggered and raised for analysis.
5.3.3.6 Cost Variance Corrective Action. Periodically, the PM conducts a formal program review to
communicate costs, schedule, and status. Variances are graphed and utilized to describe specific cost
variances (positive or negative) that are greater than PM’s established thresholds for the task-to-date. For
each variance, the PM either approves the recommended corrective action or directs that further
analysis/planning is to be done and reported on within a week. In this manner, all cost variances are
immediately acted upon before they are allowed to become significant.
Once a variance has been identified and quantified, the PM has a number of options from which he or she
may choose to correct the problem.
5-9
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
In all cases, the PM maintains total control over the resolution of the problem. If either the problem or the
corrective action taken constitutes a program risk, the risk is quantified, minimized as much as possible, and
added to the risk management database along with its contingency actions.
Since it is possible that some cost problems cannot be rectified from within the SSC San Diego RBC Project
resources, the PM may also elect to draw upon the significant resources of other SSC San Diego or sponsor
organizations.
5.3.4 Quality Control
IEEE Std 1058-1998 Guidance
(Subclause 5.3.4) Quality control plan
This subclause shall specify the mechanisms to be used to measure and control the quality of the work
processes and the resulting work products. Quality control mechanisms may include quality assurance of
work processes, verification and validation, joint reviews, audits, and process assessment.
The QA Group under the direction of the QA Manager provides the PM with the assurance that all quality
and production control requirements are being accomplished. The QA Manager also provides oversight for
the conduct of audits (e.g., Functional Configuration Audit/Physical Configuration Audit) and reviews to
assure that all performance and contractual requirements are met and integrated into the deliverable
baseline. In performing these duties, the QA Manager monitors adherence to all applicable policies,
processes, procedures, and plans through the delegation of responsibilities to the QA Group. QA will be
performed in accordance with the RBC Quality Assurance Plan in Appendix F.
5.3.5 Project Reporting and Communication
IEEE Std 1058-1998 Guidance
(Subclause 5.3.5) Reporting plan
This subclause shall specify the reporting mechanisms, report formats, and information flows to be used
in communicating the status of requirements, schedule, budget, quality, and other desired or required
status metrics within the project and to entities external to the project. The methods, tools, and
techniques of communication shall be specified in this subclause. The frequency and detail of
communications related to project measurement and control shall be consistent with the project scope,
criticality, risk, and visibility.
The following paragraphs define the management plan for ensuring the broadest communication of
needed information for project coordination.
5.3.5.1 Electronic Media. RBC project personnel will make appropriate and considerable use of e-mail
and the RBC Virtual Project Office (VPO) site to assist in distribution and review of documents,
memoranda, presentations, schedules, action items, and requests for information. The VPO is for
“internal” use, and is distinct from the RBC Information Repository.
5.3.5.2 Meetings. RBC project meetings will typically be multi-site meetings linked via telephone and
Internet. Conference call capabilities will be provided to allow audio participation, and Internet data link
capabilities will be provided to allow visual presentations.
Net Meeting software will allow any participant to control visual presentations visible to all meeting sites
using the underlying Internet links. The RBC will use the RBC VPO site for presentation material to
permit presentation review before and after the meeting. Meeting minutes will be recorded, and action
items listed and tracked to completion.
5.3.5.3 Information Repository. The RBC Information Repository (IR) maintained at SSC San Diego
provides a single secure location for reference documents, test reports, a reuse library, and related
documentation. It is the formal location for delivery of the RBC products to the end user.
5-10
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
5.3.5.4 Internal Reviews. The RBC project holds In-Progress Reviews (IPRs) at least every third month
for the purpose of monitoring internal progress towards milestones, reviewing problems encountered,
presenting proposed resolutions, presenting near-term plans, reviewing risks and mitigation plans, and
presenting a financial review using Earned Value data from Appendix A.
5.3.5.5 Status Reporting. The RBC project provides monthly progress reports to the Program Manager
summarizing work completed, a financial report, issues, meetings and conferences attended, and
upcoming calendar events.
5.3.6 Metrics Collection
IEEE Std 1058-1998 Guidance
(Subclause 5.3.6) Metrics collection plan
This subclause shall specify the methods, tools, and techniques to be used in collecting and retaining
project metrics. The metrics collection plan shall specify the metrics to be collected, the frequency of
collection, and the methods to be used in validating, analyzing, and reporting the metrics.
To ensure application of reference (h), Appendix D was developed in accordance with reference (m), and
through the tailoring of the reference (n).
The RBC SMP outlines standard measurements to be collected by task areas within the RBC project.
Measurement requirements specific to each build will be defined in the applicable Project Build Plan and
will roll up as overall project’s measurements for analysis.
5.4
RISK MANAGEMENT
IEEE Std 1058-1998 Guidance
(Subclause 5.4) Risk management plan
This subclause shall specify the risk management plan for identifying, analyzing, and prioritizing project
risk factors. This subclause shall also describe the procedures for contingency planning, and the methods
to be used in tracking the various risk factors, evaluating changes in the levels of risk factors, and the
responses to those changes.
Risk factors that should be considered include risks in the acquirer-supplier relationship, contractual
risks, technological risks, risks caused by the size and complexity of the product, risks in the development
and target environments, risks in personnel acquisition, skill levels and retention, risks to schedule and
budget, and risks in achieving acquirer acceptance of the product.
To ensure application of reference (h), the risk management approach for the RBC project follows the
guidance of the Risk Management Process, reference (p). The strategy is to develop a risk management
database to support a continuous risk assessment process following the guidance of reference (p). The
initial taxonomy of risk to be addressed is contained in Appendix A to reference (p). The RBC project
uses the Risk Radar tool for recording risks, their analysis, mitigation and contingency actions. The
database is placed under CM. The RBC PM assumes the collateral duty as the Risk Manager for the
project. The RBC PM, in the role of Risk Manager, maintains the RBC Risk database, analyzes riskrelated measurements, reviews individual database entries as needed at weekly status meetings with the
technical managers, and holds a review of the database on quarterly schedule with the sponsor and other
senior management as defined in Appendix A.
5-11
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
5.5
PROJECT CLOSEOUT
IEEE Std 1058-1998 Guidance
(Subclause 5.5) Project closeout plan
This subclause shall contain the plans necessary to ensure orderly closeout of the project. Items in the
closeout plan should include a staff reassignment plan, a plan for archiving project materials, a plan for
postmortem debriefings of project personnel, and preparation of a final report to include lessons learned
and analysis of project objectives achieved.
At the direction of the SYSCOM Communications Security Office a transition plan with the format and
content to be defined by the SYSCOM Communications Security Office, will be developed to manage
and control transition of the RBC system to the designated Life Cycle Support Activity.
5-12
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 6. TECHNICAL PROCESS
6.1
PROCESS MODEL
IEEE Std 1058-1998 Guidance
(Subclause 6.1) Process model
This subclause shall define the relationships among major project work activities and supporting
processes by specifying the flow of information and work products among activities and functions, the
timing of work products to be generated, reviews to be conducted, major milestones to be achieved,
baselines to be established, project deliverables to be completed, and required approvals that span the
duration of the project. The process model for the project shall include project initiation and project
termination activities. To describe the process model, a combination of graphical and textual notations
may be used. Any tailoring of an organization’s standard process model for a project shall be indicated
in this subclause.
The Incremental Life Cycle Strategy of reference (e) is being tailored to the acquisition of the RBC
system. Figure 6-1 presents the fundamental process model employed by the RBC project to develop the
RBC system.
Figure 6-1. RBC Project Life Cycle Strategy
The flow of information and work products through the Development Process Activities is detailed in
Appendix E. The activities of the Supporting Processes and Organizational Processes are as defined in
this PMP.
6-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
6.2
METHODS, TOOLS AND TECHNIQUES
IEEE Std 1058-1998 Guidance
(Subclause 6.2) Methods, tools, and techniques
This subclause shall specify the development methodologies, programming languages and other
notations, and the tools and techniques to be used to specify, design, build, test, integrate, document,
deliver, modify and maintain the project deliverable and non-deliverable work products. In addition, the
technical standards, policies, and procedures governing development and/or modification of the work
products shall be specified.
The allocation of functional requirements for each build will be negotiated with the SYSCOM
Communications Security Office’s System Configuration Control Board (SCCB) and documented in a
Project Build Plan for each increment. The Project Build Plan will also include build-specific acceptance
criteria and installation/user training requirements. To ensure application of reference (h), Appendix E
was developed by tailoring the organization's Product Engineering and Qualification Process, reference
(q), and applying the guidance of the Software Test Planning and Management Guide, reference (r).
Evidence of results of development activities will be deposited in Software Development Files (SDFs)
and Software Engineering Notebooks (SENs). The SDF and SEN contents and responsibility for their
maintenance is described in the RBC Configuration Management Plan, Appendix G. These artifacts,
along with pertinent project data will be deposited and maintained in a Software Development Library
(SDL) and made available to support management reviews, metrics calculations, quality audits, product
evaluations, and preparation of product deliverables. The SDL is a key component of the IR.
6.3
PROJECT INFRASTRUCTURE
IEEE Std 1058-1998 Guidance
(Subclause 6.3) Infrastructure plan
This subclause shall specify the plan for establishing and maintaining the development environment
(hardware, operating system, network, and software), and the policies, procedures, standards, and
facilities required to conduct the project. These resources may include workstations, local area networks,
tools for analysis, design, implementation, testing, and project management, desks, office space, and
provisions for physical security, administrative personnel, and janitorial services.
Appendix B specifies the plan for establishing and maintaining the development and test environments.
The resources addressed include the office and lab space, included workstations, local area networks,
hardware/software tools, provisions for physical security, facilities management processes, and equipment
maintenance contract data.
6.4
PRODUCT ACCEPTANCE
IEEE Std 1058-1998 Guidance
(Subclause 6.4) Product acceptance plan
This subclause shall specify the plan for acquirer acceptance of the deliverable work products generated
by the project. Objective criteria for determining acceptability of the deliverable work products shall be
specified in this plan and a formal agreement of the acceptance criteria shall be signed by representatives
of the development organization and the acquiring organization. Any technical processes, methods, or
tools required for product acceptance shall be specified in the product acceptance plan. Methods such as
testing, demonstration, analysis, and inspection should be specified in this plan.
6-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
The System Qualification Testing (SQT) is the SYSCOM Communications Security Office’s approved
and witnessed series of tests that demonstrate compliance with the system-level requirements. The SQT
is the acceptance mechanism for the developer’s compliance with the terms of tasking by the SYSCOM
Communications Security Office.
RBC SQT consists of complementary and progressive test phases. A single SQT Test Plan will be
generated by the System Test Organization, under the direction of a System Test Manager, to address the
planning for all levels of SQT. A Test Description will be generated for each product component,
documenting the test procedures to be run to verify each requirement for that component. A crossreference matrix will be provided, using the project-wide requirements traceability database, to document
the test or tests that satisfy each requirement. A system-level Test Report will be generated for each
product component, documenting the results of each product component test. The System Test
Organization is responsible for generating the appropriate test documentation.
6-3
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
This page intentionally left blank.
6-4
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 7. SUPPORTING PROCESSES
7.1
CONFIGURATION MANAGEMENT
IEEE Std 1058-1998 Guidance
(Subclause 7.1) Configuration management plan
This subclause shall contain the configuration management plan for the project, to include the methods
that will be used to provide configuration identification, control, status accounting, evaluation, and
release management. In addition, this subclause shall specify the processes of configuration management
to include procedures for initial baselining of work products, logging and analysis of change requests,
change control board procedures, tracking of changes in progress, and procedures for notifying
concerned parties when baselines are first established or later changed. The configuration management
process should be supported by one or more automated configuration management tools.
Appendix G was developed in accordance with the Configuration Management (CM) Process, reference
(s). The process establishes the requirement for a CM Plan that implements reference (h). The CM Plan
Template, reference (t), was tailored to develop Appendix G.
7.2
INDEPENDENT VERIFICATION AND VALIDATION
IEEE Std 1058-1998 Guidance
(Subclause 7.2) Verification and validation plan
This subclause shall contain the verification and validation plan for the project to include scope, tools,
techniques, and responsibilities for the verification and validation work activities. The organizational
relationships and degrees of independence between development activities and verification and validation
activities shall be specified. Verification planning should result in specification of techniques such as
traceability, milestone reviews, progress reviews, peer reviews, prototyping, simulation, and modeling.
Validation planning should result in specification of techniques such as testing, demonstration, analysis,
and inspection. Automated tools to be used in verification and validation should be specified.
For the RBC example, this section has been tailored to address the relationship between the RBC project
and the sponsor’s Independent Verification and Validation Agent. The RBC project processes supporting
verification and validation activities as addressed in the IEEE Std 1058-1998 would be contained in
Appendix E.
Processes for the Independent Verification and Validation (IV&V) of the RBC system are the
responsibility of the IV&V agent illustrated in Figure 4-1. The RBC PM is responsible for the conduct of
supporting analysis and resolution as required by the IV&V organization and/or the sponsor in response
to issues raised by the IV&V agent.
7.3
DOCUMENTATION
IEEE Std 1058-1998 Guidance
(Subclause 7.3) Documentation plan
This subclause shall contain the documentation plan for the project, to include plans for generating nondeliverable and deliverable work products. Organizational entities responsible for providing input
information, generating, and reviewing the various documents shall be specified in the documentation
plan. The documentation plan should include a list of documents to be prepared, the controlling template
or standard for each document, who will prepare it, who will review it, due dates for review copy and
initial baseline version, and a distribution list for review copies and baseline versions.
7-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
Defining the documentation requirements in terms of associated standards, size, and the required reviews
is important to both planning and clarifying the acquisition process. Documentation is a key deliverable
for the RBC system. Table 7-1 defines the RBC project’s documentation plan. The format standards
listed in Table 7-1 are available on the SSC San Diego PAL at http://sepo.spawar.navy.mil/. Documents
related to the Development Process Activities of Figure 6-1 are referenced in the Appendix E.
TABLE 7-1. RBC PROJECT DOCUMENTATION
Document Type
Format Standard
Estimated
Page Count
Peer Review Type
Project Management Plan
PMP Template
50
Formal Inspection
Configuration Management Plan
SCM Plan Template
50
Formal Inspection
Quality Assurance Plan
SQA Plan Template
40
Formal Inspection
Master Schedule (Microsoft Project)
MS Project Incremental
Life Cycle Schedule
Template
10
Technical Review
Measurement Plan
SMP Template
25
Formal Inspection
Facilities Plan
Project Defined
40
Formal Inspection
Training Plan
Training Plan Template
15
Technical Review
Product Engineering and Qualification
Process
PE&Q Process Template
35
Formal Inspection
Build Plan
(3 required – one per increment)
Project Build Plan
Template
15
Technical Review
Software Requirements Specifications
MIL-STD-498 SRS Data
Item Description (DID)
80
Formal Inspection
Interface Requirements Specifications
MIL-STD-498 IRS DID
70
Formal Inspection
Requirements Traceability Matrix
Project Defined
20
Technical Review
Database Design Description (DBDD)
MIL-STD-498 DBDD
DID
20
Technical Review
Software Design Description
MIL-STD-498 SDD DID
120
Technical Review
Software Development Folders with
code and unit tests
(2 required – one per CSCI)
Project Defined
100
Walkthrough
Software Test Plan
MIL-STD-498 STP DID
20
Formal Inspection
Software Test Descriptions
(2 required – one per CSCI)
MIL-STD-498 STD DID
60
Technical Review
Software Test Procedures
(2 Sets – one per STD)
Project Defined
150
Walkthrough
Integration Test Plan
Project Defined
10
Walkthrough
7-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
7.4
QUALITY ASSURANCE
IEEE Std 1058-1998 Guidance
(Subclause 7.4) Quality assurance plan
This subclause shall provide the plans for assuring that the project fulfills its commitments to the process
and the product as specified in the requirements specification, the document, supporting plans, and any
standards, procedures, or guidelines to which the process or the product must adhere. Quality assurance
procedures may include analysis, inspections, reviews, audits, and assessments. The quality assurance
plan should indicate the relationships among the quality assurance, verification and validation, review,
audit, configuration management, system engineering, and assessment processes.
Appendix F was developed in accordance with the Quality Assurance (QA) Process, reference (u). The
process establishes the requirement for a QA Plan that implements reference (h). The QA Plan Template,
reference (v), was tailored to develop Appendix F.
7.5
REVIEWS AND AUDITS
IEEE Std 1058-1998 Guidance
(Subclause 7.5) Reviews and audits plan
This subclause shall specify the schedule, resources, and methods and procedures to be used in
conducting project reviews and audits. The plan should specify plans for joint acquirer-supplier reviews,
management progress reviews, developer peer reviews, quality assurance audits, and acquirer-conducted
reviews and audits. The plan should list the external agencies that approve or regulate any product of the
project.
Audits will be performed in accordance with Appendix F, on a schedule defined in Appendix A. In
addition, the PM shall plan and participate in management reviews at locations and dates approved by the
SYSCOM Communications Security Office. Persons with authority to make cost and schedule decisions
attend the reviews. The reviews are scheduled quarterly in Appendix A for the RBC project. The reviews
are to keep SYSCOM Communications Security Office informed about project status, directions being
taken, technical agreements reached, and overall status of evolving system products. Activities would
include, but not necessarily be limited to, those listed below:
a. Resolve issues that could not be resolved at IPRs.
b. Arrive at agreed-upon mitigation strategies for near- and long-term risks that could not be
resolved at IPRs.
c. Identify and resolve management-level issues and risks not raised at IPRs.
d. Obtain commitments and acquirer approvals needed for timely accomplishment of the project.
7.6
PROBLEM RESOLUTION
IEEE Std 1058-1998 Guidance
(Subclause 7.6) Problem resolution plan
This subclause shall specify the resources, methods, tools, techniques, and procedures to be used in
reporting, analyzing, prioritizing, and processing problem reports generated during the project. The
problem resolution plan should indicate the roles of development, configuration management, the change
control board, and verification and validation in problem resolution work activities. Effort devoted to
problem reporting, analysis, and resolution should be separately reported so that rework can be tracked
and process improvement accomplished.
7-3
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
The RBC project will use the processes for storing, tracking, and directing correction of Problem/Change
Reports (P/CRs) and System Change Requests (SCRs) as defined in Appendix G. In addition, the PM
will direct that an Action Item database be maintained to track issues raised at all planning, coordination,
and joint management reviews to ensure timely action and closure. When necessary, issues will be
escalated up the chain-of-command, using the process described in Appendix A of the Integrated
Software Management/Software Product Engineering/Inter-group Coordination Guide, reference (w).
To support the resolution of critical issues that may impact the operational readiness of the system, the
RBC project will have an active Technical Review Board (TRB). The TRB, chaired by the PM or an
appointed technical manager, is responsible for addressing the key project issues that impact the system’s
ability to meet specified requirements. The TRB will assist, as directed, in ensuring that planning,
development, and acquisition of computer resources comply with established Navy policy, procedures,
plans and standards. The TRB also provides technical support to the SCCB. Given below is a set of
candidate issues that might be addressed, at the direction of the project manager, by the TRB during the
life of the RBC project:
a. Operational concept review to resolve open issues regarding the operational concept for the
system.
b. System/subsystem requirements reviews, or formally documented decision analysis, to resolve
open issues regarding the specified requirements for a system or subsystem.
c. System/subsystem design reviews, or formally documented decision analysis, to resolve open
issues regarding one or more of the following:
1. The system or subsystem-wide design decisions.
2. The architectural design of a system or subsystem.
d. System requirements reviews, or formally documented decision analysis, to resolve open issues
regarding the specified requirements for a HWCI or CSCI.
e. Software design reviews, or formally documented decision analysis, to resolve open issues
regarding one or more of the following:
1. The HWCI/CSCI-wide design decisions.
2. The architectural design of a HWCI/CSCI.
3. The detailed design of a HWCI/CSCI or portion thereof (such as a database).
f. Test readiness reviews to resolve open issues regarding one or more of the following:
1. The status of the test environment.
2. The test cases and test procedures to be used for product qualification testing or System
Qualification Testing.
3. The status of the hardware and software to be tested.
g. Test results reviews to resolve open issues regarding the results of product qualification testing or
system qualification testing.
h. System usability reviews to resolve open issues regarding one or more of the following:
1. The readiness of the system for installation at user sites.
2. The user and operator manuals.
3. The system version descriptions.
4. The status of installation preparations and activities.
i. System supportability reviews to resolve open issues regarding one or more of the following:
1. The readiness of the system for transition to the support agency.
2. The system product specifications.
7-4
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
3. The system support manuals.
4. The system version descriptions.
5. The status of transition preparations and activities, including transition of the system
development environment, if applicable.
j. Critical requirement reviews, or formally documented decision analysis, to resolve open issues
regarding the handling of critical requirements, such as those for safety, security, and privacy.
7.6.1 TRB Membership
The Development Group, CM, QA, and the Test and Evaluation Group shall be responsible for providing a
representative to the TRB. The representative’s responsibilities are listed below:
a. Attend all TRB meetings.
b. Provide draft issue papers, as tasked to the member, at a specified period prior to the TRB
meeting where it will be discussed.
c. Update, release, and control technical memoranda reflecting the TRB decisions to the group the
member represents.
7.6.2 TRB Chairperson
The PM may serve as the TRB Chairperson, although the task may be delegated to a technical manager. In
that case, the TRB Chairperson shall be accountable to the PM to report problems as they are encountered
by the TRB. The Chairperson’s responsibilities are listed below:
a. Schedule meetings.
b. Provide the meeting space and administrative support.
c. Distribute issue documentation to be addressed at the upcoming TRB.
d. Conduct the TRB meetings.
e. Record, track, and update action items.
f. Ensure the minutes of the TRB meetings are recorded and distributed.
g. Ensure that decisions are distributed within the time frame agreed to by the affected participants.
7.7
CONTRACTOR MANAGEMENT
IEEE Std 1058-1998 Guidance
(Subclause 7.7) Subcontractor management plans
This subclause shall contain plans for selecting and managing any subcontractors that may contribute
work products to the project. The criteria for selecting subcontractors shall be specified and the
management plan for each subcontract shall be generated using a tailored version of this standard.
Tailored plans should include the items necessary to ensure successful completion of each subcontract.
In particular, requirements management, monitoring of technical progress, schedule and budget control,
product acceptance criteria, and risk management procedures shall be included in each subcontractor
plan. Additional topics should be added as needed to ensure successful completion of the subcontract. A
reference to the official subcontract and prime contractor/subcontractor points of contact shall be
specified.
Contractor resources needed by the RBC project are identified in the planning (or plan revision) process.
Elements of the WBS typically become contract requirements. During the planning process, an informal
survey of existing contracts is done to see if an existing contract may be used to meet the contract
requirements, including schedule and budget requirements.
7-5
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
The acquisition and monitoring of required contractor support is done in accordance with the Contractor
Acquisition and Performance Monitoring Process, reference (x). The process establishes the requirement
for contractor management activities implementing reference (h).
A COR will be named to oversee the contract and track contractor process and contract status. The COR
may be outside of the RBC organization; however, they must be technically conversant with RBC system
development issues. The COR will hold periodic technical reviews with the contractor, and periodic
status reviews with the contractor’s management. The reviews are for the benefit of the SYSCOM
Communications Security Office, providing visibility into contract performance, and also for SSC San
Diego, providing visibility into contractor capability and suitability. Contract activity measurements will
be defined in the contract SOW, will complement RBC project measurements, and will be reported to the
RBC PM’s designated representative. Contractor planning documentation will be reviewed and approved
by the RBC project government technical staff. The COR will also ensure compliance with SSC
acquisition regulations.
7.7.1 Contracting Process
The RBC project will follow the guidance of reference (x). Briefly, a Procurement Requirements
Package (PRP) will be published for proposed new contracts. A contract SOW is written. For existing or
new indefinite delivery contracts, Delivery Orders, PRPs and SOWs will be written in accordance with
the overall contract PRP or SOW. Proposals are collected and evaluated by the COR depending upon
requirements satisfaction (cost and schedule), contract type, and contractor capability. An award will be
made employing a formally documented decision analysis and resolution process such as the Decision
Analysis and Resolution Process (Expert Mode), reference (y). The COR will administer the contract,
and monitor and track contractor performance, including measurement collection, correspondence,
funding, and deliverable. The COR will make this information available to the PM in a timely manner.
7.7.2 Contractor Performance Monitoring
The RBC PM is responsible for the management of contractor performance. The PM delegates contractor
monitoring on a technical basis to the technical managers, and on a financial basis to the RBC PM’s
Administrative Office. Issues raised at contractor reviews are either resolved during the review, assigned
to a technical manager, or escalated up the chain-of-command in accordance with Appendix A of
reference (w).
7.8
PROCESS IMPROVEMENT
IEEE Std 1058-1998 Guidance
(Subclause 7.8) Process improvement plan
This subclause shall include plans for periodically assessing the project, determining areas for
improvement, and implementing improvement plans. The process improvement plan should be closely
related to the problem resolution plan; for example, root cause analysis of recurring problems may lead
to simple process improvements that can significantly reduce rework during the remainder of the project.
Implementation of improvement plans should be examined to identify those processes that can be
improved without serious disruptions to an ongoing project and to identify those processes that can best
be improved by process improvement initiatives at the organizational level.
The following paragraphs provide data on the RBC project’s efforts for continuing process improvement.
7.8.1 Systems/Software Process Improvement Lead
The RBC Systems/Software Process Improvement (SPI) Lead, assigned by the PM, will evaluate RBC
practices and make recommendations regarding government and industry best practices in key
management and development areas, and interface with the Department Systems Engineering Process
Group (SEPG) and SSC San Diego Systems Engineering Process Office (SEPO).
7-6
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
7.8.2 Systems Engineering Process Group
Each Department at SSC San Diego maintains an SEPG that is responsible to the Department Head for
the development and maintenance of applied system engineering processes. The SEPG provides a forum
for discussion of systems engineering processes and applicable best practices, and promotes the gathering
and dissemination of information on those processes.
The SEPG shall analyze the measurement data collected and assess the effectiveness and value of the
organization’s processes. This is done to ensure that the processes are being adapted properly and to
identify those processes that need improvement. The SEPG will interface with SEPO to perform and/or
acquire any required training necessary to implement process improvement within the organization. The
SEPG interfaces with SEPO to exchange knowledge on system engineering processes and process
improvement on a center-wide basis. The relationship between SEPO, the Department SEPG, and the
RBC SPI Lead is seen in Figure 4-1. SSC San Diego establishes overall systems engineering policy and
guidance, while the SEPG assures sound application of that policy and guidance within the department.
The RBC project SPI Lead serves as the communication interface between the project and the
Department’s SEPG for all issues related to process improvement for the RBC project.
7-7
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
This page intentionally left blank.
7-8
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
SECTION 8. ADDITIONAL PLANS
IEEE Std 1058-1998 Guidance
(Clause 8) Additional plans
This clause shall contain additional plans, or activities, required to satisfy product requirements and
contractual terms.
Additional plans for a particular project may include plans for assuring that safety, privacy, and security
requirements for the product are met, special facilities or equipment, product installation plans, user
training plans, integration plans, data conversion plans, system transition plans, product maintenance
plans, logistic engineering approach, or product support plans.
General Guidance
In this template this section is used to describe the logistics engineering, and its objectives, inherent in the
RBC project.
8.1
LOGISTICS ENGINEERING
The RBC project performs logistics engineering as an integral part of the development and life cycle
support effort. The objective of the integrated logistics engineering activities is to achieve the maximum
level of System Operational Effectiveness (SOE) following the guidance of Designing and Assessing
Supportability in DoD Weapon Systems – A Guide to Increased Reliability and Reduced Logistics
Footprint, reference (z).
A system’s operational effectiveness derives from a number of component factors that can be described in
a hierarchical model, as shown in Figure 8-1.
Figure 8-1. Components of System Operational Effectiveness
8-1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
8.1.1 System Performance
System performance is realized through designed-in system capabilities and functions. The term
capability refers to the various desired performance attributes of the system, such as maximum data rates
and message capacity. The term functions refer to the desired mission capabilities and mission scenarios
that the system must be capable of executing in an operational environment. For the RBC system, these
characteristics are determined during requirements analysis.
8.1.2 System Availability
The components that contribute to system availability include the systems reliability, maintainability,
supportability and sustainment. Supportability and sustainment are essential components of SOE. For
the RBC system, these characteristics are determined during requirements analysis and the adjudication of
the requirements with the determination of a cost effective component architecture. For example, during
the cyclic activities of requirements analysis and architectural design, decisions on ‘buy-or-build’ for an
architectural component will weigh reliability, maintainability, and supportability as key decision criteria
and may cause reconciliation with capability and/or functional requirements.
8.1.3 Process Efficiency
Process efficiency reflects how well the system can be operated and maintained, and to what degree the
logistics infrastructure and footprint can be reduced to provide a cost effective, deployable, and
operationally effective system. For the RBC system, these issues are both a part of the RBC project’s
continuous process improvement efforts and for the end system, they are addressed during the
adjudication of requirements and the architectural design processes defined in Appendix E.
8.1.4 Technical Effectiveness
Technical effectiveness reflects the inherent balance between system performance and system availability.
These two aspects of the system are designed-in. The PM ensures the processes for designing and
assessing supportability are not only applied during the product development framework, but throughout
the entire life cycle. Supportability assessments, coordinated with systems engineering, are intended to
identify redesign opportunities for fielded systems that would enhance overall operational effectiveness.
For the RBC project, the continuous improvement of technical effectiveness is inherent in the revision
planning for each build of the system and in the efforts for continuous process improvement.
8.1.5 System Effectiveness
System effectiveness reflects the balance achieved between the technical effectiveness and the process
efficiency of the system. In this context, process efficiency constitutes the system operational,
maintenance, and logistics processes. System effectiveness reflects the real mission capability delivered
to the field. The RBC PM is ultimately responsible for the resulting system effectiveness.
8.1.6 System Ownership Cost
The final piece in the overall SOE model pertains to cost effectiveness. The over-riding objective is to
maximize the system effectiveness from the perspective of the end-user. However, given a resourceconstrained environment trade-offs are inevitable among performance, availability, process efficiency,
and cost. The PM must address these issues using the SOE model and negotiate the consequences of
balancing consideration of performance, cost, schedule, system availability, and process efficiency with
the sponsor for each individual RBC build and its content.
8-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDICES
IEEE Std 1058-1998 Guidance
Annexes may be included, either directly or by reference to other documents, to provide supporting
details that could detract from the document if included in the body.
General Guidance
In this template, the following appendices are used for reference purposes only. It should not be assumed
that the referenced RBC documents exists as an example.
Appendices -1
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX A. RBC MASTER SCHEDULE (MICROSOFT PROJECT)
Guidance
The objective of the RBC Master Schedule is to provide management with the task map and tracking tool
needed to guide the RBC Project in the performance of its mission.
The RBC Master Schedule’s Microsoft Project representation of the WBS would be tailored from the
templates available from the SSC San Diego Process Asset Library (PAL) in the “SW-CMM Archive”.
Draft Microsoft Project templates are found under the “Process Assets by SW-CMM KPA”, “Software
Project Planning (SPP)” in the “Tools” section. These templates can be tailored up or down to meet
specific project needs.
Appendices-2
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX B. RBC FACILITIES PLAN
Guidance
The objective of the RBC Facilities Plan is to document the environmental needs of the RBC project.
These needs include space, equipments, security, safety, support tools, and the staff necessary to maintain
and operate an environment needed for project operations.
The facilities requirements for projects vary broadly, often with several projects sharing both facilities
and computer resources. There currently are no templates available from the SSC San Diego PAL to
assist in developing a facilities plan. However, recommended issues to address in a Facilities Plan would
include, but not be limited to, the following list:
1. Facility Objectives/General Description
2. Facility Locations (i.e., Building Locations)
3. Facility Diagrams
a. Floor Plans (i.e., lab, work cubicles)
b. Environmental Requirements i.e. Heating, Lighting
4. Facilities Equipment Requirements
a. Equipment Lists (i.e., work stations, development, test)
b. Equipment Interface Diagrams
c. Space Equipment Layouts
d. Inspections and Records Requirements
5. Facilities Software Requirements
a. Software by Development/Test Host Equipment
b. Software by Workstation
6. Facilities Operating Personnel Requirements
7. Facilities Operating Personnel Training Requirements
8. Security Measures
a. Internal
b. External
9. Safety Measures
10. Maintenance Requirements (i.e., spaces, per equipment)
11. Facilities Performance Measurements
Appendices -3
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX C. RBC PROJECT TRAINING PLAN
Guidance
The objective of the RBC Project Training Plan is to develop the skills and knowledge of the RBC project
staff so they can perform their roles effectively and efficiently.
The RBC Project Training Plan would be tailored from the Department/Project Training Plan Template
available from the SSC San Diego Process Asset Library (PAL). The template is located in the “Process
Assets by CMMI PA” sub-page under the “Organizational Training” PA in the “Plans” section. The
template can be tailored up or down to meet specific project needs.
Appendices-4
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX D. RBC MEASUREMENT PLAN
Guidance
The objective of the RBC Measurement Plan is to develop and present the data needed to support RBC
project management information needs necessary to ensure objective decision-making.
The RBC Measurement Plan would be tailored from the Software Measurement Plan Template available
from the SSC San Diego Process Asset Library (PAL) in the “SW-CMM Archive”. This template can be
found under the ”Process Assets by SW-CMM KPA”, “Software Project Tracking and Oversight
(SPTO)” KPA in the “Tools” section. The template can be tailored up or down to meet specific project
needs.
Appendices -5
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX E. RBC PRODUCT ENGINEERING AND QUALIFICATION
PROCESS
Guidance
The objective of the RBC Product Engineering and Qualification (PE&Q) Process is to document the
processes comprising a technical solution for development, maintenance, test, and product qualification.
The RBC PE&Q Process would be tailored from the Product Engineering and Qualification Process
available from the SSC San Diego Process Asset Library (PAL). The process is located in the “Process
Assets by CMMI PA” sub-page under the “Technical Solution” PA in the “Process” section. The PE&Q
Process can be tailored up or down to meet specific project needs.
Appendices-6
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX F. RBC QUALITY ASSURANCE PLAN
Guidance
The objective of the RBC Quality Assurance Plan is to provide staff and management with objective
insights into processes and associated work products, ensuring their conformance to documented
requirements.
The RBC Quality Assurance Plan would be tailored from the Quality Assurance Plan Template available
from the SSC San Diego Process Asset Library (PAL). The process is located in the “Process Assets by
CMMI PA” sub-page under the “Process and Product Quality Assurance (PPQA)” PA in the “Plans”
section. The template can be tailored up or down to meet specific project needs.
Appendices -7
[[RBC Project]] PMP
[[Document Configuration Identifier]]
[[Date]]
APPENDIX G. RBC CONFIGURATION MANAGEMENT PLAN
Guidance
The objective of the RBC Configuration Management Plan is to establish and maintain the integrity of
RBC work products using configuration identification, configuration control, configuration status
accounting, and configuration audits.
The RBC Configuration Management Plan would be tailored from the Configuration Management Plan
Template available from the SSC San Diego Process Asset Library (PAL). The template is located in the
“Process Assets by CMMI PA” sub-page under the “Configuration Management (CM)” PA in the
“Plans” section. The template can be tailored up or down to meet specific project needs.
Appendices-8
DOCUMENT CHANGE REQUEST (DCR)
Document Title: [[RBC]] Project Management Plan
Tracking Number:
Name of Submitting Organization:
Organization Contact:
Phone:
Mailing Address:
DCR Description:
Date:
Change Location:
(use section #, figure #, table #, etc.)
Proposed change:
Rationale for Change:
Note: For the indicate appropriate authority to take appropriate action on a change request, please provide a clear
description of the recommended change along with supporting rationale.
Send to: Commanding Officer, Space and Naval Warfare Systems Center, Code [[2xx]], 53560 Hull Street, San
Diego, CA 92152-5001
Fax to: indicate appropriate fax number
Email to: indicate appropriate email
Submit online: indicate appropriate URL
DCR Form 2/2005