| The following roles typically are involved in the deployment discipline: -
The Deployment Manager plans and organizes deployment. She is responsible for the beta test feedback program and ensuring the product is packaged appropriately for shipment. -
The Project Manager is the primary customer interface and is responsible for approving deployment based on feedback and test result evaluations and for the customer's acceptance of the delivery. -
The Technical Writer plans and produces end- user support material and the Course Developer plans and produces training material. -
The Graphic Artist is responsible for all product- related artwork. -
The Tester runs the acceptance tests and is responsible for ensuring that the product has been tested adequately. -
The Implementer creates installation scripts and related artifacts that will help the end user install the product. Deployment Artifacts Deployment as described in the Rational Unified Process ranges from the deployment of customized systems to the situation where the end user can download software from a specified Web site. Given this vast range, whether or not the artifacts listed below will be required depends on the deployment mode. The key artifact is a release, packaged in one or more Deployment Units, which may consist of one or more of the following artifacts: -
The executable software, in all cases -
Installation artifacts: script, tools, files, guides, licensing information -
Release Notes, describing the release for the end user -
Support Material, such as user manual, operations and maintenance manuals -
Training Materials In the case of the shrink-wrapped product, additional artifacts will be required for creating the "product," such as: Other deployment artifacts used in the development of the product, but not necessarily released to the customer, include Figure 15-1 shows roles and key artifacts in the Deployment discipline. Figure 15-1. Roles and key artifacts in the deployment discipline  |
