Gap analysis
A template for formally documenting discontinuities, unanswered questions, and perceived shortcomings between the current state and target state architecture.
For this activity, refer to chapter 2.6 Target state architecture as a guide. Gaps can be identified at any stage of the design process, and should be documented to ensure they are addressed in time.
Analysis steps
- Identify the components affected: Associate the scope of the gap with specific components or functional areas. You can’t move forward with that component until the gap has been resolved to an acceptable degree.
- Assess the current state: Document the existing or current state, if there is one, again highlighting the functional area that aligns with the future state gap.
- Determine the desired future state: Describe the function required in the future state architecture (focusing on the specific functional area that is exposed to a gap).
- Assess the gap: Identify exactly what the gap is. This is usually expressed in terms of the lack of function or impact to the design. Try to state clear metrics that quantitatively express the gap between current and future state.
- Summarize: Include a summary of the gap and metrics in clear language, so that anyone reading the gap can quickly see its potential impact and risk.
- Create action plan: Document an action plan to resolve the gap within necessary project parameters.
The gap analysis provides a clear understanding of the differences between the current state and the target state, highlighting the specific areas where improvements or changes are needed. By identifying and addressing these gaps methodically, you can make strategic improvements to technical infrastructure and capabilities, ultimately achieving a desired future state.
Gap: [GAP TITLE]
| Component | Current state/function |
|---|---|
Event Log |
|
| Target state | |
| |
| Gap | |
| |
| Action Plan | |
| Summary | Current (legacy) state relies on older generation on-prem relational database technology. The future state is a modern, even streaming system that can handle inbound events at scale, using on-demand (elastic) scaling. The on-prem technology does not meet performance/functional requirements, and may also have some security and governance weaknesses. |
| Action plan |
|
| Business capabilities affected |
|
| Component detail |
|
| Data and security impact |
|
| Recommendations |
|
| Roadmap impact |
|