Architecture Overview Document
A high-level architecture document providing stakeholders with
an overview of the architecture landscape, component inventory, dependencies,
and standards compliance. Suitable for governance reviews and onboarding.
Target Purposes: Informing, Governing
Available Formats: MarkdownFormat, HTMLFormat, PDFFormat
Sections
1. Architecture Landscape
High-level overview of the architecture showing major components and domains.
2. Stakeholder Analysis
Map stakeholders to their concerns and the viewpoints that address them.
3. Component Inventory
Catalog of all architecture components with key attributes.
4. Dependency Analysis
Matrix showing dependencies between components for impact analysis.
5. Standards Compliance
Assessment of component compliance with applicable standards.
Solution Design Document
A solution-level architecture document covering process design,
interface design, deployment topology, and architecture decisions. Used by
solution architects and development teams during design and implementation.
Target Purposes: Designing
Available Formats: MarkdownFormat, HTMLFormat
Sections
1. Solution Context
Overview of the solution within the broader architecture landscape.
2. Process Design
Process flows showing activities, decision points, and handoffs.
3. Interface Design
Interface map showing component connections, protocols, and data flows.
4. Deployment Design
Deployment map showing where components run and hosting relationships.
5. Architecture Decisions
Log of architecture decisions with context, rationale, and status.
Change Impact Assessment
An assessment document for evaluating the impact of a proposed
architecture change. Covers impact propagation, dependency analysis, gap analysis,
and migration planning. Used for change governance and decision-making.
Target Purposes: Deciding, Governing
Available Formats: MarkdownFormat, PDFFormat, SlideFormat
Sections
1. Impact Analysis
Propagation of change through dependencies — what breaks if this changes.
2. Dependency Assessment
Full dependency matrix for the affected components.
3. Gap Analysis
Differences between current and target state after the change.
4. Migration Roadmap
Planned evolution steps to implement the change.
