<Project Name>

Deployment 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.       Introduction

1.1     Purpose

1.2     Scope

1.3     Definitions, Acronyms, and Abbreviations

1.4     Overview

2.       References

3.       Deployment Planning

3.1     Responsibilities

3.2     Schedule

4.       Resources

4.1     Facilities

4.2     Hardware

4.3     The Deployment Unit

4.3.1         Support Software

4.3.2         Support Documentation

4.3.3         Support Personnel

5.       Training

Deployment Plan

1.                  Introduction

[Provide an overview of the entire document.]

1.1               Purpose

[Describe the purpose of the software to which this document applies.]

1.2               Scope

[Identify the recipients for the items identified in the Deployment Plan.]

1.3               Definitions, Acronyms, and Abbreviations

[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Deployment Plan.  This information may be provided by reference to the project's Glossary.]

1.4              Overview

[Explain how this document is organized.]

 

2.                  References

[This subsection provides a complete list of all documents referenced elsewhere in the Deployment Plan.  Identify each document 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.]

 

3.                  Deployment Planning

[Describe all activities performed in deploying the product to the customer. Activities include planning, beta testing, preparing items to be delivered, packaging, shipping, installation, training, and support.]

3.1               Responsibilities

[Identify the responsibilities of both the customer and the development team in preparing for deployment. Of particular relevance in this section is the description of the customer’s involvement in acceptance tests and the process for handling any discrepancies.]

3.2               Schedule

[Describe the schedule and milestones to conduct the deployment activities. Deployment milestones need to conform to the project milestones. 

Take into account the following Deployment workflow details:

• Planning the Deployment
• Developing the Supporting Material
• Managing the Acceptance Tests
  • Acceptance Testing at the Development Site
  • Acceptance Testing at the Deployment Site
• Producing the Deployment Unit
• Managing the Beta Program
• Managing the Product Mass Production and Packaging
• Making the Product Accessible Over the Internet]
  

4.                  Resources

[List the resources and their sources required to carry out the planned deployment activities.]

4.1               Facilities

[As applicable, describe the facilities required to test and deploy the software. Facilities may include special buildings or rooms with raised flooring, power requirements, and special features to support privacy and security requirements.]

4.2               Hardware

[Identify the hardware required to run and support the software. Specify model, versions, and configurations. Provide information about manufacturer support and licensing.]

4.3               The Deployment Unit

[List the software and documentation provided as part of the deliverable product.]

4.3.1          Support Software

[As applicable, describe all software needed to support the deliverable product, such as tools, compilers, test tools, test data, utilities, Configuration Management tools, databases, data files, and so on.]

4.3.2          Support Documentation

[As applicable, describe the documentation required to support the delivered product, including design descriptions, test cases and procedures, user manuals, and so on.]

4.3.3          Support Personnel

[As applicable, describe the personnel, and their skill levels, required to support the deliverable product.]

 

5.                  Training

[Describe the plan and inputs for training the end users such that they can use and adapt the product as required.]