Java ES Solution Life Cycle
The tasks involved in creating business solutions based on Java ES software can be divided into several phases, as shown in the following figure. The illustration also shows the category of Java ES user that generally performs the tasks.
Figure 1–3 Solution Life Cycle Phases and User Categories
The life cycle phases shown in the preceding figure can be divided into the following general groupings:
-
Predeployment. In these phases, a business need is translated into a deployment scenario, which is a logical architecture and a set of quality of service requirements. The deployment scenario serves as a specification for designing a deployment architecture.
-
Deployment. In these phases, a deployment scenario is translated into a deployment architecture. This architecture can be used as a basis for project approval and budgeting. The deployment architecture is also the basis for an implementation specification that provides the details needed to deploy (build, test, and roll out) a software solution in a production environment.
-
Postdeployment. In the operations phase, a deployed solution is run under production conditions and monitored and optimized for performance. The deployed solution is also upgraded to include new functionality as necessary.
The tasks in each life cycle phase shown in Figure 1–3 are discussed more fully in Chapter 4, Java ES Solution Life Cycle.
Figure 1–3 shows the Java ES users who typically perform the tasks shown for the life cycle phases. The following table describes the skills and background for each category of user.
Table 1–5 Java ES User Categories for Life Cycle Tasks
- © 2010, Oracle Corporation and/or its affiliates