Predeployment tasks are grouped into three phases, as shown in Figure 4–1:
Business analysis. In this phase, you 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. In this phase, you 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. In this phase, you 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 Enterprise System Solution Architectures, you design a logical architecture. The logical architecture shows all the components, and all the interactions between the 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 on the predeployment phases of the life cycle, see the Sun Java Enterprise System 2005Q4 Deployment Planning Guide.