Architecture Landscape

Intro

The Architecture Landscape represents the complete set of architectural assets, views, and states across the organisation. In EA, it helps stakeholders understand current and target architectures.

Key points:

• Captures baseline, transition, and target states
• Improves planning and impact analysis
• Common use cases: portfolio views, capability maps, technology stacks, roadmap stages, dependency analysis
• Pitfall: outdated artefacts reduce trust and usefulness

Examples:

• Current vs target application portfolio view
• Capability map linked to process and system ownership
• Technology standards by platform and lifecycle

In practice:

Explore Business Capability Management and Application and Technology Lifecycle Management for structuring landscape views.

Related terms: Roadmap; Capability; Application Portfolio Management

FAQs:

Q: What makes a landscape actionable?
A: Clear ownership, freshness, links across business/process/data/app/tech.

Q: How often should it be updated?
A: Align to governance cadence; update after material changes or quarterly reviews.

‍