WORKFLOW

WORKFLOW

The activity diagram in Figure 15-2 identifies the major kinds of activities that are necessary to deploy software effectively to the end user .

Figure 15-2. The deployment workflow
graphics/15fig02.gif

Plan Deployment

Given that successful deployment is defined by the customer's willingness to use the new software, deployment planning not only must take into account how and when the complete list of deliverables will be developed, but also must ensure that the end user has all the necessary information to take delivery of the new software. To ensure a smooth transition, deployment plans include the beta test program for iteratively assessing earlier versions of the software under construction.

Overall system deployment planning requires a high degree of customer collaboration and preparation. A successful conclusion to a software project can be impacted severely by factors outside the scope of software development such as the building, hardware infrastructure not being in place, and users who are ill-prepared for cut-over to the new system.

Develop Support Material

Support material covers the full range of information that will be required by the end user to install, operate , use, and maintain the delivered system. It also includes training material for all the various positions that will be required to use the new system effectively.

Test Product at Development Site

Testing at the development site helps determine whether the product is sufficiently mature for release either as the final deliverable or for distribution to beta testers.

Beta testing a packaged product is done by polling a wide range of end users for feedback. In the case of a custom-installed system, a beta test could be a pilot installation at the target site.

To reinforce the idea that testing activities and platforms at the development site should closely approximate the intended target site, Test Product activities are identical for testing at the development site and the target site, with one exception. The exception is that the testing at the development site may use test harnesses orsimulators. Testing at the target site will use the actual target hardware.

Create Release

The purpose of this workflow detail on the deployment activity diagram is to ensure that the product is prepared for delivery to the customer. A release consists of everything the end user will need to install and run the executable software.

Beta Test Release

Beta testing requires the delivered software to be installed by the end user, who provides feedback on its performance and usability.

In the context of iterative development, beta testing is essential to ensuring that customer expectations are met and that user feedback is factored into the next development iteration.

Test Product at Installation Site

Following sufficient internal and beta testing, the product needs to be installed on-site and tested by the customer. Based on the preceding iteration tests and customer engagements, the final site tests should come as no surprise, but should be only a formality for the customer to "accept" the system!

Package Product

This set of optional activities describes what needs to occur for producing "packaged software" products. In this case, the release is saved as a master for mass production and then packaged in product boxes together with the Bill of Materials for shipment to the customer.

Provide Access to Download Site

The appeal of Web commerce and the Internet as a software distribution channel is obvious. The product is entirely accessible through the software environment of browsers and Web sites. The challenge for the provider is to make sure the product is available at all times (24/7) to a global marketplace even through varying loads that could choke the host hardware and communication bandwidths.

Setting up the hardware infrastructure to host the corporate Web presence is beyond the scope of a software development process. However, the Deployment Manager needs to know how to add the product to the list of products offered through the Web and communicate that the product is available for purchase or delivery on demand.

The Web provides a good mechanism for enabling feedback from users, announcing upgrades, or otherwise providing access, perhaps through passwords, to other corporate services.



The Rational Unified Process. An Introduction
The Rational Unified Process: An Introduction (3rd Edition)
ISBN: 0321197704
EAN: 2147483647
Year: 1998
Pages: 176

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net