<Project Name>
Software 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 should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms and Abbreviations
2.1 Project Purpose, Scope and Objectives
2.2 Assumptions and Constraints
2.4 Evolution of the Software Development Plan
3.3 Roles and Responsibilities
4.2.5.2 Resource Acquisition Plan
4.4 Project Monitoring and Control
4.4.1 Requirements Management Plan
5.2 Methods, Tools and Techniques
6.1 Configuration Management Plan
6.6 Subcontractor Management Plan
Software Development Plan
[The introduction of the Software Development Plan should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Software Development Plan.]
[Specify the purpose of this Software Development Plan.]
[A brief description of the scope of this Software Development Plan; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Software Development Plan. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Software Development Plan. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.
For the Software Development Plan, the list of referenced artifacts should include:
- Iteration Plans
- Requirements Management Plan
- Measurement Plan
- Risk Management Plan
- Development Case
- Business Modeling Guidelines
- User Interface Guidelines
- Use-Case-Modeling Guidelines
- Design Guidelines
- Programming Guidelines
- Test Guidelines
- Manual Style Guide
- Infrastructure Plan
- Product Acceptance Plan
- Configuration Management Plan
- Evaluation Plan (only if this is a separate plan - normally this is part of the SDP at Section 6.2)
- Documentation Plan
- Quality Assurance Plan
- Problem Resolution Plan
- Subcontractor Management Plan
- Process Improvement Plan]
[This subsection should describe what the rest of the Software Development Plan contains and explain how the document is organized.]
[A brief description of the purpose and objectives of this project and a brief description of what deliverables the project is expected to deliver.]
[A list of assumptions that this plan is based and any constraints, for example. budget, staff, equipment, schedule, that apply to the project.]
[A tabular list of the artifacts to be created during the project, including target delivery dates.]
[A table of proposed versions of the Software Development Plan, and the criteria for the unscheduled revision and reissue of this plan.]
[Describe the organizational structure of the project team, including management and other review authorities.]
[Describe how the project interfaces with external groups. For each external group, identify the internal and external contact names.]
[Identify the project organizational units that will be responsible for each of the disciplines, workflow details, and supporting processes.]
[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.]
[Include the following:
- Work Breakdown Structure (WBS)
- a timeline or Gantt chart showing the allocation of time to the project phases or iterations
- identify major milestones with their achievement criteria
Define any important release points and demos]
[List the objectives to be accomplished for each of the iterations.]
[A brief description of each software release and whether it's demo, beta, etc.]
[Diagrams or tables showing target dates for completion of iterations and phases, release points, demos, and other milestones.]
[Identify here the numbers and type of staff required, including any special skills or experience, scheduled by project phase or iteration.]
[Describe how you will approach finding and acquiring the staff needed for the project.]
[List any special training project team members will require, with target dates for when this training should be completed.]
[Allocation of costs against the WBS and the Phase Plan.]
[Each iteration plan will be enclosed in this section by reference.]
[Enclosed by reference.]
[Describes the approach to be taken to monitor progress against the planned schedule and how to take corrective action when required.]
[Describes the approach to be taken to monitor spending against the project budget and how to take corrective action when required.]
[Describe the timing and methods to be used to control the quality of the project deliverables and how to take corrective action when required.]
[Describes internal and external reports to be generated, and the frequency and distribution of publication.]
[Enclosed by reference.]
[Enclosed by reference.]
[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]
[Enclosed by reference.]
[Lists the documented project technical standards, etc., by reference:
- Business Modeling Guidelines
- User Interface Guidelines
- Use-Case-Modeling Guidelines
- Design Guidelines
- Programming Guidelines
- Test Guidelines
- Manual Style guide]
[Enclosed by reference]
[Enclosed by reference]
[Enclosed by reference]
[Part of the Software Development Plan, this describes the project's plans for product evaluation, and covers the techniques, criteria, metrics, and procedures used for evaluation- this will include walkthroughs, inspections, and reviews. Note that this is in addition to the Test Plan which is not enclosed in the Software Development Plan.]
[Enclosed by reference.]
[Enclosed by reference.]
[Enclosed by reference.]
[Enclosed by reference.]
[Enclosed by reference]
[Additional plans if required by contract or regulations.]
[Additional material of use to the reader of the SDP.]