Activity:
|
Purpose
|
|
Role: Deployment Manager | |
Frequency: Final Iterations of the Transition Phase | |
Steps | |
Input Artifacts: | Resulting Artifacts: |
Tool Mentors: |
Workflow Details: |
In true web tradition, any number of clients on the internet (at any given time) should be able to browse to a host site and request files, or purchase product, through the server. The implication is that not only is there a corporate web presence, but the presence is 24x7 reliable and enabled for secure e-commerce transactions.
The Deployment Manager needs to put the Deployment Unit (the executable software, installation files and documentation) and any other product relevant information on the server in a predetermined access directory.
The Deployment Manager needs to work with whoever in the organization is responsible for publishing and maintaining the corporate web site. The web site needs to include a page describing the product with all the appropriate branding artwork. The product page should be enabled to provide access to the product (deployment unit) and related files.
The web site should enable the client to make on-line purchases, and download the product, and provide pointers for product support and answers to "frequently asked questions".
As with getting feedback from the Beta Test Program, the product web site should be set up to solicit feedback from the customer, and otherwise engage the customer in upgrade programs.
Rational Unified Process |