Predeployment

In the predeployment phases of the life cycle, you translate an analysis of business needs into a deployment scenario. The deployment scenario serves as a specification for a deployment design.

Predeployment tasks are grouped into three phases, as shown in Figure 4–1:

• Business analysis. Define the business goals of a proposed deployment effort and state the business requirements and constraints that must be met to achieve that goal.

• Technical requirements. Use the results of the business analysis to create use cases that model user interaction with an anticipated software system. You also determine the usage patterns expected for those use cases. Using both the business analysis and the usage analysis, you formulate quality of service requirements (see Table 2–2) that the proposed deployment must meet.

• Logical design. Analyze the use cases developed in the technical requirements phase to determine which Java ES infrastructure components and which custom-developed application components are needed to provide end-user services. Using the concepts discussed in Chapter 2, Java ES Solution Architectures, you design a logical architecture. The logical architecture shows all components and all interactions between components that are needed to effect the use cases of a particular software solution.

The logical architecture combined with performance, availability, security, and other quality of service requirements is encapsulated in a deployment scenario, as shown in the following figure. For more information about predeployment phases of the life cycle, see the Sun Java Enterprise System Deployment Planning Guide.

Figure 4–2 Specifying a Deployment Scenario