Architects often need to perform analysis on a set of IT Applications for redundancy and gaps in the functionality it offers. This activity is required for example during
Application convergence
Redundant Application phase-out
Activity 1: Contextual Analysis
(IAF's contextual analysis, TOGAF's Preliminary Phase: Framework and Principles (Re-look) and Architecture Vision Phase)
When conducting any architecture analysis, it is recommended to conduct a contextual analysis of the architecture so that the objectives are agreed upon. This is a collaborative effort which requires proper buy-in from all sponsors. Note that the risk of failure is high if this step is skipped. Also the effectiveness of this critical step depends on the maturity and capability of the EA practice within the organization. The common denominator of all enterprise architecture wisdom is: start simple, remain simple but grow (mature). This is very true in this stage. Based on TOGAF and my own experience the following needs to be exchanged and validated by all stakeholders of the architecture.
· To review the organizational context for conducting architecture analysis
· To identify the sponsor stakeholder(s) and other major stakeholders impacted by the business directive to create the architecture analysis
· To ensure that everyone who will be involved in, or benefit from, this approach is committed to the success of the architectural process
· To define the "architecture footprint" - the people responsible for performing architecture work, where they are located, and their responsibilities
· To define the framework and detailed methodology that are going to be used to develop the architecture and share it across
· To confirm a governance
· To define the architecture principles that will form part of the constraints on the architecture work
Activity 2: Application modeling
(IAF's Physical IS/IT, TOGAF's Phase C: Information Systems Architectures)
Most of the situations, architects a-priori know what applications need to be analyzed. But before making a rational call to make an analysis on an application, it is necessary to make a technical analysis on all relevant application on inter-application dependencies (technical and functional). If a legacy application which needs to be phased out has dependencies on other applications and vice-versa, an impact analysis needs to be made. Following are few considerations need to be made.
· Applications transmitting data.
· Applications receiving data.
· Architecture standards of the applications and the interdependent and potentially impacted applications.
Activity 3: Information system functional (capability) modeling
(IAF's Logical IS/IT, TOGAF's Phase C: Information Systems Architectures)
ARIS identifies information system functions as IT capabilities. This name best captures this aspect. Depending on the complexity of the application, either a complete architecture development lifecycle (from business to IS/IT) or a direct functional mapping can be done. A mix of a top-down and vice versa approach is to be used to identify and map the IS Functions to the supporting IT Applications. Mark a cross or a percentage of coverage of the functionality.
I have developed a very smart analysis report using ARIS which populates functionality coverage. However a level based modeling approach is to be used. This works like charm and very simple to manage, though it looks a bit complicated. We were able to model and make analysis with ease and intuitively. A simple example is shown below. Function 1 is broken down into further details and its lower level functionality is also mapped to the applications which support it. For example, resource management which is functionality can be provided by multiple applications. But there can be very important differences in its lower level details which may or may not be supported by other applications.
| | App 1 | App 2 | App 3 | App 4 |
| Function 1 | 40% | 60% | 80% | 20% |
| Function 2 | 35% | 40% | 100% | 0% |
| Function 3 | 0% | % | 100% | 0% |
| … | | | | |
| …. | | | | |
| | App 1 | App 2 | App 3 | App 4 |
| Function 1.1 | 100% | 100% | 100% | 100% |
| Function 1.2 | 100% | 100% | 100% | |
| Function 1.3 | | | | |
| Function 1.4 | | | 100% | |
| Function 1.5 | | 100% | 100% | |
Activity 4: Analysis
(TOGAF’ Phase E: Opportunities and Solutions)
After identifying gaps and convergences, prepare a road map to phase-out and build if needed.
If you have any comments please do let me know.
.jpg)
No comments:
Post a Comment