View

Intro

A view is a representation assembled to address specific stakeholder concerns. It may be visual or non‑visual and often uses one or more models.

Key points:

• Tailors information to decisions and audiences.
• Improves understanding and alignment.
• Common use cases across EA/BPM/Data/App/Tech include capability views, process views, and deployment views.
• Pitfall: generic views that do not answer stakeholder questions.

Examples:

• Executive capability heatmap view.
• Process view highlighting handoffs and SLAs.
• Integration view for solution design.

In practice:

Define the viewpoint first, then construct views that directly address its concerns.

Related terms: Viewpoint; Model; Architecture Framework

FAQs:

Q: Can one view serve multiple stakeholders?
A: Yes, if their concerns overlap.

Q: Are views tied to a specific tool?
A: No; they are conceptual and can be rendered by many tools.

‍