Lesson 1: Understanding the Windows 7 Deployment Life Cycle ChAPTER 1 17 in .NET framework

Maker Denso QR Bar Code in .NET framework Lesson 1: Understanding the Windows 7 Deployment Life Cycle ChAPTER 1 17

After the two teams have generated images that are feature complete, the testing team performs pilot deployments to evaluate them further. Because the actual Genetic Research division is not operational yet, standard pilot deployments in the live environment are not possible. Therefore, the team plans two pilot deployments that they hope will simulate the live environment as closely as possible. The first uses a selected group of users in other divisions, and concentrates on testing general business requirements, such as security mechanisms. The second pilot deployment uses a group of Genetic Research division new hires, who the company is bringing in before the division launch especially for this testing. This pilot concentrates on the specialized scientific applications and hardware that require experienced users. Both pilot deployments emulate real-world use in an attempt to expose any flaws in the plan or its implementation. The building and testing teams work together to assess, triage, and debug any problems that arise. During this stage, it might be necessary to revise the functional specification, the master plan, or the master schedule. If this is the case, all of the project s stakeholders must approve these revisions before they are adopted.

At the conclusion of the Stabilize process, the management team reviews all of the documentation generated during the testing and debugging processes. When team members conclude that the workstation environments are stable and meet all of the requirements set down in the master plan, they sign off on the build, signaling that the Deploy stage can begin.

The deployment process has been carefully plotted during the Project Planning stage, and it has been tested during the Stabilize stage. Now, the live production deployment can begin with the installation of the workstations and other required hardware in the new site for the Genetic Research division. Other IT teams have already completed their own projects, to provide the division with the network infrastructure and other resources it will need to operate. A hardware installation team first unpacks and assembles the new computers on site, testing them for basic functionality. The hardware order included spares, so the team can immediately swap out any computers that are nonfunctional on arrival. With the hardware in place, the deployment team can begin the process of installing the completed image files on the workstations. Although the Stabilize process is formally ended, testing continues during the deployment because there are always variables that cannot be duplicated in the lab. Most of the issues that arise during the deployment likely concern the specialized scientific equipment, and it is prudent for the manufacturers to send technicians to the site. To take advantage of the technicians presence, several of the operations team members participate in the sessions as well because they will likely have to service the equipment later. The Deploy stage concludes with the installation of all of the planned workstations, fulfillment of all planned requirements, and the satisfaction of all stakeholders involved, including management, IT, and end users. The life cycle now proceeds from the Deliver phase to the Operate phase, with responsibility for the workstations passing to the operations teams.

The completion of the workstation deployments signals the beginning of the life cycle s Operate phase, as shown in Figure 1-7. The Operate phase is the culmination of the two phases that preceded it. The Plan phase was concerned with what workstations to build, and the Deliver phase with the process of building them. The Operate phase is all about keeping the workstations running smoothly after they are built.

Responsibility for the workstations now passes to the operate teams, many members of which are individuals who participated in the Deploy phase. The SMFs for the Operate phase all occur concurrently, with each one defining tasks and services that the workstations will use at various times throughout their operational lives.