Software Development Plan
[pic]This Plan is Scheduled for Review / Revision during a Future Iteration of the Development Case and is provided as is.
Software Product Name
(ACRONYM)
Software Development Plan
(SDP)
Written by:
Marc W. George
Last revision by:
Marc W. George
Latest Revision
April 22, 2000
Company Name
[Note: The following template is provided for use with the Development Case. 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).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]
[During the development of the Development Case, it was decided that certain plans and guidelines should be standardized to reduce the duplication of effort and to unify management practices. This document contains hyperlinks to those documents. It was also decided that to simplify the deployment of a project’s workspace and the creation of the project’s web site while implement a standardized configuration management plan that the Project Management artifacts could be pre-organized. The hyperlinks within this document are based on that organization]
Revision History
|Date |Version |Description |Author |
| | | | |
| | | | |
| | | | |
| | | | |
Table of Contents
1. Introduction 6
1.1 Purpose 6
1.2 Scope 6
1.3 Definitions, Acronyms and Abbreviations 6
1.4 References 6
1.4.1 Development Case 6
1.4.2 Standardized Plans 7
1.4.3 Standardized Guidelines 7
1.4.4 Other Resources 7
1.4.5 External Resources 7
1.5 Overview 7
Project Overview 8
1.6 Project Purpose, Scope, and Objectives 8
1.7 Assumptions and Constraints 8
1.8 Project Deliverables 8
1.9 Evolution of the Software Development Plan 8
2. Project Organization 9
2.1 Organizational Structure 9
2.2 External Interfaces 9
2.3 Roles and Responsibilities 9
3. Management Process 10
3.1 Project Estimates 10
3.2 Project Plan 10
3.2.1 Phase Plans 10
3.2.2 Iteration Objectives 10
3.2.3 Releases 10
3.2.4 Project Schedule 10
3.2.5 Project Resourcing 10
3.2.6 Budget 10
3.3 Iteration Plans 10
3.4 Project Monitoring and control 11
3.4.1 Requirements Management Plan 11
3.4.2 Schedule Control Plan 11
3.4.3 Budget Control Plan 11
3.4.4 Quality Control Plan 11
3.4.5 Reporting Plan 11
3.4.6 Measurement Plan 11
3.5 Risk Management plan 11
3.6 Close-out Plans 11
4. Technical Process Plans 12
4.1 Development Case 12
4.2 Methods, tools and techniques 12
4.3 Infrastructure Plan 12
4.4 Product Acceptance Plan 12
5. Supporting Process Plans 13
5.1 Configuration Management Plan 13
5.2 Evaluation Plan 13
5.3 Documentation Plan 13
5.4 Quality Assurance Plan 13
5.5 Problem Resolution Plan 13
5.6 Subcontractor Management Plan 13
5.7 Process Improvement Plan 13
6. Additional plans 14
7. Annexes 15
8. Index 16
Software Development Plan
Introduction
[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.]
1 Purpose
[Specify the purpose of this Software Development Plan.]
This Software Development Plan (SDP) is the one of two primary artifacts of the Software development process that is being used by this project, the Ration Unified Process, the other being the Software Architecture Document (SAD). This document provides the framework under which all artifacts of this project are organized. It is the replacement for the traditional “Project Plan” of other development processes.
Traditionally the SDP consists of plans, guidelines and work breakdown structures of a project. During the development of the Development Case, it was decided that most plans and guidelines could be standardized to reduce duplication of effort while unifying management and development practices across all projects. This SDP combines together those standardized documents with the plans, guidelines and work breakdown structures that are unique to this project, and incorporates significant external reference sources. These documents are either referenced or hyperlinked as appropriate.
2 Scope
[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 SDP includes the organization, plans, guidelines, work breakdown structures and other materials that are pertinent to the “PROJECTNAME” project which was authorized under MAP ID “MAP ID”.
This project is associated to the following projects:
1. None
This document affects or influences the following:
1. Nothing
3 Definitions, Acronyms and Abbreviations
[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.]
4 References
1 Development Case
Development Case
2 Standardized Plans
Configuration Management Plan
Documentation Plan
Infrastructure Plan
Measurement Plan
Problem Resolution Plan
Process Improvement Plan
Product Acceptance Plan
Quality Assurance Plan
Requirements Management Plan
Risk Management Plan
Subcontractor Management Plan
3 Standardized Guidelines
Business Modeling Guidelines
User-Interfaces Guidelines
Use-Case Modeling Guidelines
Design Guidelines
Programming Guidelines
Test Guidelines
Manual Style Guide
4 Other Resources
5 External Resources
5 Overview
[This subsection should describe what the rest of the Software Development Plan contains and explain how the document is organized.]
This document presents a high level overview of the project, its scope and deliverables followed by the organization of the project and the project management, technical and supporting processes that will be used. It is concluded by an index.
Project Overview
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 Assumptions and Constraints
[A list of assumptions that this plan is based and any constraints, for example. budget, staff, equipment, schedule, that apply to the project.]
3 Project Deliverables
[A tabular list of the artifacts to be created during the project, including target delivery dates.]
4 Evolution of the Software Development Plan
[A table of proposed versions of the Software Development Plan, and the criteria for the unscheduled revision and reissue of this plan.]
Project Organization
1 Organizational Structure
[Describe the organizational structure of the project team, including management and other review authorities.]
2 External Interfaces
[Describe how the project interfaces with external groups. For each external group, identify the internal and external contact names.]
3 Roles and Responsibilities
[Identify the project organizational units that will be responsible for each of the core workflows, workflow details, and supporting processes.]
Management Process
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.]
MAP
Original Estimate Work Breakdown Structure (Schedule)
Current Estimate Work Breakdown Structure (Schedule)
2 Project Plan
1 Phase Plans
Inception Phase Plan
Elaboration Phase Plan
Construction Phase Plan
Transition Phase Plan
2 Iteration Objectives
[List the objectives to be accomplished for each of the iterations.]
3 Releases
[A brief description of each software release and whether it’s demo, beta, etc.]
4 Project Schedule
[Work Breakdown Structure (WBS), diagram, charts or tables showing target dates for completion of iterations and phases, release points, demos, and other milestones.]
Current Work Breakdown Structure (Schedule)
5 Project Resourcing
1 Staffing Plan
Staffing Plan
2 Resource Acquisition Plan
Resource Acquisition Plan
3 Training Plan
Training Plan
6 Budget
[Allocation of costs against the WBS and the Phase Plan.]
3 Iteration Plans
Inception Phase
Iteration 1
Elaboration Phase
Iteration 1
Construction Phase
Iteration 1
Transition Phase
Iteration 1
4 Project Monitoring and control
1 Requirements Management Plan
Requirements Management Plan
2 Schedule Control Plan
Schedule Control Plan
3 Budget Control Plan
Budget Control Plan
4 Quality Control Plan
Quality Control Plan
5 Reporting Plan
Reporting Plan
6 Measurement Plan
Measurement Plan
5 Risk Management plan
Risk Management Plan
6 Close-out Plans
Inception Phase Closeout Plan
Elaboration Phase Closeout Plan
Construction Phase Closeout Plan
Transition Phase Closeout Plan
Technical Process Plans
1 Development Case
Development Case
2 Methods, tools and techniques
Business Modeling Guidelines
User-Interfaces Guidelines
Use-Case Modeling Guidelines
Design Guidelines
Programming Guidelines
Test Guidelines
Manual Style Guide
3 Infrastructure Plan
Infrastructure Plan
4 Product Acceptance Plan
Product Acceptance Plan
Supporting Process Plans
1 Configuration Management Plan
Configuration Management Plan
2 Evaluation Plan
Evaluation Plan
3 Documentation Plan
Documentation Plan
4 Quality Assurance Plan
Quality Assurance Plan
5 Problem Resolution Plan
Problem Resolution Plan
6 Subcontractor Management Plan
Subcontractor Management Plan
7 Process Improvement Plan
Process Improvement Plan
Additional plans
[Additional control processes]
Annexes
[Additional material of use to the reader of the SDP.]
Index
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- software development business plan template
- software development plan example word
- types of software development models
- software development process models
- types of software development processes
- software development plan example
- software development plan template excel
- software development plan template government
- software development plan template word
- software development project plan template
- software development project plan example
- software development plan template