Key takeaways
- B addresses Business; C addresses Data and Application; D addresses Technology.
- Baseline and target descriptions reveal necessary change.
- Domain phases are coordinated and may be iterative.
Three areas of work
Phase B develops Business Architecture aligned with objectives and the vision. Phase C develops Data and Application Architectures. Phase D develops the Technology Architecture needed for the whole to operate. Domains are coordinated: a data decision may change a process, application, or technical constraint.
Within each domain, work selects viewpoints, models, and tools, describes the relevant baseline, and develops the target. It analyzes gaps, identifies roadmap elements, and considers effects on the landscape. Stakeholders then review proposals and the content of the definition document is refined.
Iterative progress
These activities are revisited when dependencies or new requirements emerge. ABBs become progressively more precise without immediately prescribing implementation products. Gap analysis, interoperability, and trade-off techniques support decisions. Results inform the Architecture Definition Document, Architecture Requirements Specification, and a candidate Architecture Roadmap.
- Tailor baseline detail to the comparison needed.
- Check consequences across domains.
- Preserve assumptions, decisions, and requirements during iteration.
TERMS TO KNOW
The terms, in context.
- Baseline Architecture
- Description of the current state relevant to the study.
- Target Architecture
- Description of the intended state addressing the objectives.