ADM

• All the phases surround requirement management which flows through continuously.
• All phases have inputs, steps and outputs(deliverables in the form of documents).
• ADM is generic in nature but it can be modified to fit our needs.

Phases of EDM:

Preliminary phase

We do this only once. This is preparation and intiatition activity.

• Here we define what enterprise means to us.
• We are going to choose framework here For example like TOGAF and you may want to adopt ITIL and swap some of TOGAF steps with ITIL.
• Evaluating enterprise maturity and capability.
• Defining architecture principles.

Architecture Vision

Here we develop high level vision to be delivered. It is where problems are defined and solutions starts forming. This is at high level. We are talking to stakeholders and come up with vision then obtain approval for statement of architecture work. In this phase we define:

• Define scope
• Estimate resources needed
• develop roadmap and schedule.
• Define KPIs and metrics
• Communications plan

Business Architecture

It is B in BDAT

• Develop the baseline business architecture V1.0 Business requirements dictate what technical requirements will be. Baseline means current architecture.
• Develop the target business architecture V1.0. Target is the future state.
• Identify gaps between baseline and target.

Information Systems Architecture

This is D and A in BDAT. Data and application done separately.

• Develop the baseline data architecture V1.0
• Develop the target data architecture V1.0
• Develop the baseline application architecture V1.0
• Develop the target application architecture V1.0
• Identify gaps between baseline and target.

Technology Architecture

This is T in BDAT

• Develop the baseline technology architecture V1.0
• Develop the target technology architecture V1.0
• Identify gaps between baseline and target.

At the end of this phase you have full defined architecture for business, data and application.

Opportunities and Solutions

• Inside this phase we are going to have initial complete version of the architecture roadmap based on the gap analysis of BDAT.
• Here we determine if incremental approach is required. Which means if there are N number of things to do then it is better to split them in incremental approach called transition architectures.
• Formulate implementation and migration strategy. Here we decide how we are going to break things up and which one we should be doing first and which one second etc.
• Identify and group work packages

Migration Planning

• Finalize the architecture roadmap and implementation and migration plan. Here we are going to work with project managers, implementers, estimates and putting them into actual schedule.
• Make sure that whatever plan we are coming with matches with enterprise approach to change.
• Ensure the business value of the approach is understood by stakeholders.
• Start thinking about implementation: costs, resources, timing
• Transition from developing the architecture to implementing.

Implementation Governance

• Ensure conformance with the target architecture.
• Governance duties.
• Handling change requests from implementation team.
• Update baseline architecture as changes are implemented. As the transition architecture goes live then baseline architecture gets updated.
• This phase ends when solution are fully deployed.

Architecture Change Management

• We have to make sure architecture capability is not lost. keep the architecture alive.
• Ensure architecture governance is happening. So when change comes in changes gets approved, denied and logged, following proper architecture governance.
• Ensure architecture capability is maintained
• Monitoring: Changes to the business enterprise, changes to industry, changes to technology, formal change requests like microsoft comes with new directions and changes in framework, or oracle is replacing some of the products.