Phase E: Opportunities and Solutions

Objective    Approach     Inputs     Steps    Outputs

Objective

The objectives of this phase are to:

• evaluate and select among the implementation options identified in the development of the various target architectures (for example, build-versus-buy-versus-reuse options, and sub-options within those major options)

• identify the strategic parameters for change, and the top-level work packages or projects to be undertaken in moving from the current environment to the target;

• assess the dependencies, costs, and benefits of the various projects; and

• generate an overall implementation and migration strategy and a detailed implementation plan.

Approach

This phase identifies the parameters of change, the major phases along the way and the top-level projects to be undertaken in moving from the current environment to the target. The output of this phase will form the basis of the implementation plan required to move to the target architecture. This phase also attempts to identify new business opportunities arising from the architecture work in previous phases.

Sometimes the process of identifying implementation opportunities allows a business to identify new applications, and in this case it may be necessary to iterate between the Opportunities and Solutions phase and previous phases. Iteration must be limited by time or money to avoid wasting effort for the search of a perfect architecture.

The Opportunities and Solutions phase is the first phase which is directly concerned with implementation. The task is to identify the major work packages or projects to be undertaken.

An effective way to do this is to use the gap analysis on the business functions between the old environment and the new, created in Phase D. Any functions appearing as "new" items will have to be implemented (developed or purchased and deployed).

Slightly harder to identify are the projects required to update or replace existing functions which must be done differently in the new environment. One of the options to be considered here is leaving an existing system in place and coexisting with the new environment.

During this final step in the specification of building blocks it must be verified that the organization-specific requirements will be met. Key to this is reason checking against the business scenario driving the scope of this project. It is important to note that the ensuing development process must include recognition of dependencies and boundaries for functions and should take account of what products are available in the marketplace. An example of how this might be expressed can be seen in the Building Blocks Example in Part IV.

Coexistence appears on the surface to be easy. After all, the original system is left in place, largely unchanged. Unfortunately, it is not always as easy as it looks. The main problems with coexistence are:

• user interfaces: Combining user interfaces to the old and new applications in a single unit on the users' desks can be difficult, if not impossible.
• access to data: Often the new applications need to share some data with the old applications, and some kind of data sharing must be established. This can be difficult unless the old and new systems use the same database technology.
• connectivity: This may involve expenditure on software and gateway equipment. In difficult cases, equipment simply may not be available in a useful time scale. Often this happens because the old system is simply too out of date for connectivity solutions to be still on the market.

The most successful strategy for the Opportunities and Solutions phase is to focus on projects that will deliver short-term pay-offs and so create an impetus for proceeding with longer-term projects.

Inputs

Inputs to this phase are:

• Request for Architecture Work
• Statement of Architecture Work
• Business Architecture
• Data Architecture
• Applications Architecture
• Technology Architecture
• Re-usable architecture building blocks (from organization's Enterprise Continuum, if available)
• Product information

Steps

Key steps in this phase include:

1. Identify the key business drivers constraining the sequence of implementation (for example, reduction of costs; consolidation of services; introduction of new customer services; etc.)
2. Review the gap analysis generated in Phase D.
3. Brainstorm technical requirements from a functional perspective
4. Brainstorm co-existence and interoperability requirements
5. Perform architecture assessment and gap analysis
6. Identify major work packages or projects, and classify as new development, purchase opportunity, or reuse of existing system.

Outputs

The outputs of this phase are:

• Implementation and migration strategy
• High-level implementation plan
• Impact Analysis - Project list

Copyright © The Open Group, 1998, 1999, 2000, 2002