<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).]
[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.]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.4áááá Definitions, Acronyms and Abbreviations
3.2.1áááááááá Deployment Planning
3.2.2áááááááá Support Material Development
3.2.3áááááááá Acceptance Test Management
3.2.4áááááááá Producing the Deployment Unit
3.2.5áááááááá Beta Program Management
3.2.6áááááááá Manage Product Mass Production and Packaging
3.2.7áááááááá Making the Product Accessible over the Internet
4.3.1áááááááá Support Software
4.3.2áááááááá Support Documentation
4.3.3áááááááá Support Personnel
Deployment Plan
[Provide an overview of the entire document.]
[Describe the purpose of the software to which this document applies.]
[Identify the recipients for the items identified in the Deployment Plan.]
[Explain how the document is organized.]
[This subsection should provide 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 Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Deployment 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.]
[Describe all activities to be performed in deploying the product to the customer. Activities include planning, beta testing, preparation of items to be delivered, packaging, ôshippingö, installation, training and support.]
[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 to handle any discrepancies.]
[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.]
[List the resources, and their sources, required to carry out the planned deployment activities.]
[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. ]
[Identify the hardware required to run and support (as required) the software. Specify model, versions and configurations. Provide information about manufacturer support and licensing.]
[List the software and documentation that is provided as part of the deliverable product.]
[As applicable, describe all the software (tools, compilers, test tools, test data, utilities, CM tools, databases, data files, etc) needed to support the deliverable software.]
[As applicable, describe the documentation (design descriptions, test cases and procedures, user manuals, etc) required to support the delivered software.]
[As applicable, describe the personnel, and their skill levels, required to support the deliverable software.]
[Describe the plan and inputs for training the end user such that they can use and/or adapt the product as required.]