Key takeaways
- A gap may be a missing, changed, or retired element.
- An overlooked concern also signals a gap.
- Trade-offs should consider consequences across the whole architecture.
| Baseline / Target | Retained catalog | Shared service | Eliminated |
|---|---|---|---|
| Existing catalog | Included | — | — |
| Paper register | — | — | Removal to justify |
| New | — | Develop or acquire | — |
Remove the register only after checking that its functions and data are covered. New and Eliminated identify gaps to address or justify; these feed the roadmap.
A gap is more than an addition
Gap Analysis compares baseline and target to identify what should be retained, changed, created, or removed. It can also expose an overlooked stakeholder concern. Analysis spans domains: skills, processes, information, applications, technology, and other required resources. It is not limited to comparing software features.
A data gap may concern availability, quality, freshness, meaning, or relationships. A business gap may concern responsibilities, performance measurement, or working conditions. The description should be precise enough to support an action and avoid treating a symptom as its underlying cause.
Compare before selecting
Trade-off analysis examines options that address concerns differently. Cost, time, risk, flexibility, and quality can conflict. Alternatives are considered within a domain and across the complete architecture. An option that appears optimal for one application may harm operations or information sharing. A trade-off can reveal implicit requirements and require further stakeholder discussion.
- Define criteria with stakeholders.
- Explain the benefits, limitations, and assumptions of each option.
- Record the decision and accepted consequences.
TERMS TO KNOW
The terms, in context.
- Gap
- Meaningful difference between two states being studied.
- Trade-off
- Decision between options with different benefits or constraints.