<Project Name>

System Development Plan

 

Version <1.0>

 

 

[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and must be deleted before publishing the document. A paragraph entered following this style is automatically set to normal (style=Body Text).]


Revision History

Date

Version

Description

Author

<dd/mmm/yy>

<x.x>

<details>

<name>

 

 

 

 

 

 

 

 

 

 

 

 

 


Table of Contents

1.          Introduction         

1.1      Purpose     

1.2      Scope     

1.3      Definitions, Acronyms, and Abbreviations     

1.4      References     

1.5      Overview     

2.          Project Overview      

2.1      Project Purpose, Scope, and Objectives     

2.2      Assumptions and Constraints     

2.3      Project Deliverables     

2.4      Evolution of the System Development Plan     

3.          Project Organization  

3.1      Organizational Structure     

3.2      External Interfaces     

3.3      Roles and Responsibilities     

4.          Management Process

4.1      Project Estimates     

4.2      Project Plan 

4.2.1       System Breakdown Structure  

4.2.2       Phase Plan

4.2.3       Iteration Objectives

4.2.4       Releases      

4.2.5       Project Schedule 

4.2.6       Project Resourcing      

              4.2.6.1       Staffing Plan

              4.2.6.2       Plan for Other Project Resources      

              4.2.6.3       Resource Acquisition Plan      

              4.2.6.4       Training Plan      

4.2.7       Budget      

4.3      Iteration Plans     

4.4      Project Monitoring and Control     

4.4.1       Requirements Management Plan      

4.4.2       Schedule Control Plan

4.4.3       Technical Performance Measurement Plan    

4.4.4       Budget Control Plan      

4.4.5       Quality Control Plan      

4.4.6       Reporting Plan      

4.4.7       Measurement Plan      

4.5      Risk Management plan     

4.6      Close-Out Plan     

5.          Technical Process Plans 

5.1      Development Case     

5.2      Methods, Tools, and Techniques     

5.3      Facilities Plan 

5.4      System Integration, Evaluation, and Test Plan       

5.5      Product Acceptance Plan     

6.          Supporting Process Plans 

6.1      Configuration Management Plan      

6.2      Documentation Plan     

6.3      Quality Assurance Plan     

6.4      Problem Resolution Plan     

6.5      Subcontractor and Supplier Management Plan     

6.6      Process Improvement Plan 

6.7      V&V and IV&V Plan

6.8      Specialty Engineering Plans    

6.9      Value Engineering Plan

7.          Subordinate Plans for Hardware and Software Development

8.          Additional Plans 

9.          Annexes 

10.          Index     


System Development Plan

 

1.                  Introduction

[The introduction of the System Development Plan provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this System Development Plan.]

1.1               Purpose

[Specify the purpose of this System Development Plan.]

1.2               Scope

[A brief description of the scope of this System Development Plan; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]

1.3               Definitions, Acronyms, and Abbreviations

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the System Development Plan. This information can provided by reference to the project Glossary.]

1.4               References

[This subsection provides a complete list of all documents referenced elsewhere in the System Development Plan. Idenify each document by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information can be provided by reference to an appendix or to another document.

For the System Development Plan, the list of referenced artifacts includes:

1.5               Overview

[This subsection describes what the rest of the System Development Plan contains and explains how the document is organized.]

2.                  Project Overview

2.1               Project Purpose, Scope, and Objectives

[A brief description of the purpose and objectives of this project and a brief description of what deliverables the project is expected to deliver.]

2.2               Assumptions and Constraints

[A list of assumptions upon which this plan is based and any constraints, for example, budget, staff, equipment, schedule, that apply to the project.]

2.3               Project Deliverables

[A tabular list of the products to be created during the project, including target delivery dates.]

2.4               Evolution of the System Development Plan

[A table of proposed versions of the System Development Plan, and the criteria for the unscheduled revision and reissue of this plan.]

3.                  Project Organization

3.1               Organizational Structure

[Describe the organizational structure of the project team, including management and other review authorities.]

3.2               External Interfaces

[Describe how the project interfaces with external groups, for example, associate contractors and IV&V agents. For each external group, identify the internal and external contact names.]

3.3               Roles and Responsibilities

[Identify the project organizational units that are responsible for each of the disciplines, workflow details, and supporting processes.]

4.                  Management Process

4.1               Project Estimates

[Provide the estimated cost and schedule for the project, as well as the basis for those estimates, and the points and circumstances in the project when re-estimation will occur.]

4.2               Project Plan

4.2.1     System Breakdown Structure (SBS)

[The SBS is an evolving view of the way the system or product is broken down into elements (both operational and enabling/support) that constructed separately and are separately budgeted and resourced. Also known as the Product Breakdown Structure, the SBS contrasts with the Work Breakdown Structure that is task-based and defines the kinds and amounts of work and other resources needed to produce an element in the SBS.]

4.2.2          Phase Plan

[Include the following:

Define any important release points and demonstrations.]

4.2.3          Iteration Objectives

[List the objectives to be accomplished for each of the iterations.]

4.2.4          Releases

[A brief description of each system release and whether it is a prototype, demonstration, beta, and so forth.]

4.2.5          Project Schedule

[Diagrams or tables showing target dates for completion of iterations and phases, release points, demos, and other milestones.]

4.2.6          Project Resourcing

4.2.6.1     Staffing Plan

[Identify here the numbers and type of staff required, including any special skills or experience, scheduled by project phase or iteration.]

4.2.6.2     Plan for Other Project Resources

[Identify other resources (materials, equipment, facilities, tools, and so forth) needed for the project. Refer to other plans (for example, the Facilities Plan) as appropriate.]

4.2.6.3     Resource Acquisition Plan

[Describe your approach to finding and acquiring the staff and other resources needed for the project. Refer to other plans (for example, the Facilities Plan) as appropriate.]

4.2.6.4     Training Plan

[List any special training project team members require, with target dates for when this training must be completed.]

4.2.7          Budget

[Allocation of costs against the WBS, the SBS and the Phase Plan.]

4.3               Iteration Plans

[Each iteration plan is enclosed in this section by reference.]

4.4               Project Monitoring and Control

4.4.1          Requirements Management Plan

[Enclosed by reference.]

4.4.2          Schedule Control Plan

[Describes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.]

4.4.3          Technical Performance Measurement Plan

[Describes the approach and methods to identify, measure, track, and control the critical technical characteristics, for example weight, power consumption. Identify these characteristics and, where necessary, decompose them into lower-level characteristics and map to elements in the SBS. This plan also includes a description of the risks associated with meeting the planned profiles, and contingency plans to deal with deviations.]

4.4.4          Budget Control Plan

[Describes the approach to be taken to monitor spending against the project budget and how to take corrective action when required.]

4.4.5          Quality Control Plan

[Describes the timing and methods used to control the quality of the project deliverables and how to take corrective action when required.]

4.4.6          Reporting Plan

[Describes internal and external reports to be generated, and the frequency and distribution of publication.]

4.4.7          Measurement Plan

[Enclosed by reference.]

4.5               Risk Management Plan

[Enclosed by reference.]

4.6               Close-out Plan

[Describes the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports, and so on.]

5.                  Technical Process Plans

5.1               Development Case

[Enclosed by reference.]

5.2               Methods, Tools, and Techniques

[Lists the documented project technical standards, and so forth, by reference:

5.3               Facilities Plan

[Enclosed by reference.]

5.4               System Integration, Evaluation, and Test Plan

[Enclosed by reference.]

5.5               Product Acceptance Plan

[Enclosed by reference.]

6.                  Supporting Process Plans

6.1               Configuration Management Plan

[Enclosed by reference.]

6.2               Documentation Plan

[Enclosed by reference.]

6.3               Quality Assurance Plan

[Enclosed by reference.]

6.4               Problem Resolution Plan

[Enclosed by reference.]

6.5               Subcontractor Management Plan

[Enclosed by reference.]

6.6               Process Improvement Plan

[Enclosed by reference.]

6.7               V&V and IV&V Plan

[Enclosed by reference.]

6.8               Specialty Engineering Plans

[These plans address the requirement for various special engineering disciplines, for example, covering:

6.9               Value Engineering Plan

[Enclosed by reference.]

7.                  Subordinate Plans for Hardware and Software Development

[Enclosed by reference.]

8.                  Additional plans

[Additional plans may be required by the contract or regulations.]

9.                  Annexes

[Additional material of use to the reader of the System Development Plan.]

10.                  Index