Skip to main content
Architecture Roadmaps Approach
![Understanding the WHY](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg9mAqSf0VayOiaS3yun7GMNm2KkAip-MT91K6p6imQNujVYEYHfmxnlTuCZb8ZYsNTh-0xGwvKg8PuQthny9-hFwQQkpWp7JkASFm-XUs_1GgJtXe93_IfF5FS5SBJuonwxMkuQ7MHw8F88xKHl77-ObHKTQ5n6YB2Fj6mGMFMaeI6lyD_-lfTew/w488-h255/BusinessMotivation-WHY.png) |
Motivation |
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiHSayfzTrUj9a0P6M31CGTkt3oF8bOB8krTYzmXO5BoeDzjDGH6tMegY_awtfPMa94541VzvWEh7vwQyV_gtxGkLpBLlLX-qlrVauzckIERYoUXhzlm57ZsDDgYFVQ-mMtJ1o25gwjcSaqMapgvZNX4XZqG-hzfeqTp3AGJb7b0TyakgQIiLBSNQ/w640-h226/CaseStudies-Roadmaps%20Approach.png) |
EA Roadmaps process |
Key Stages of the EA roadmap process -
- Discovery
- Collect all the current documentations from various sources
- Baseline the current state
- Document the current state of the architecture (Business, Applications, Tech, Mappings between various concepts using the Fan-Out method)
- Architecture Assessment -
- Understand the reasons (Motivation) for change.
- Conduct architecture assessment of the current state based on the business goals/objectives (End) and drivers(Influencers) using various proven tools (Reference Architectures, Heatmaps, Applications Portfolio Rationalisation Methods )
- Model the target state of the architecture (Reference architectures for Business, Applications, Tech layer, Mappings between various concepts using the top-down method)
- These models need to be socialised with various stakeholders and approved formally to initiate the change programs to identify target solutions.
- Transition Planning
- Breakdown the changes into multiple blocks and work with the management team to order them based on various priorities
- Build artefacts to govern the implementation phase if required
Comments