Overview

A significant difference between the enhanced lifecycle for the Unified Process (depicted in Figure 5.1) and the initial lifecycle is that the enhanced version recognizes the fact that most organizations have more than one software project that they need to manage. The reality is that software project teams are dependent on the infrastructure of your organization and on one another from a resource-sharing point of view. At the same time, within their definedscope software project, teams are also independent of one another and free to make decisions in an appropriate manner. In short, for a software process to be truly effective, it must include activities that support the successful management of portfolios of software projects. The Infrastructure Management workflow was added to the enhanced lifecycle of the Unified Process to focus on the management and support of cross-project issues.

Figure 5.1: The enhanced lifecycle for the Unified Process.

Project teams are both dependent and independent.

The activities of infrastructure management are summarized Table 5.1, and as you can see, there are a wide variety of important activities that this workflow encompasses. Because the Elaboration phase concentrates on the development of the architecture for your project, you will focus your efforts on reuse management and organization/enterprise-level architectural modeling for the Infrastructure Management workflow. Through your reuse management efforts, you will identify existing artifacts, such as common frameworks and components, that you can likely apply to your project efforts. You should also start...