How ArcaMira supports the EA function¶
This tier is about practice, not buttons. Each guide takes one enterprise-architecture discipline and answers three questions:
- The EA problem — what you're actually trying to do, and why it's hard.
- How ArcaMira addresses it — the features and the model behind them.
- What good looks like — a realistic target state, so you know when you're done enough.
The disciplines¶
| Discipline | The question it answers |
|---|---|
| Capability-based planning | What does the business do, and how well is each part supported? |
| Application portfolio management | What systems do we run, and which should we invest in, keep, or retire? |
| Technology lifecycle & risk | What are we running on, and what's about to become a liability? |
| Data landscape & governance | What information do we hold, where does it flow, and how is it classified? |
| Architecture governance | How do we steer change — principles, standards, decisions, and review? |
| Roadmapping & change | What's changing, when, and what does each initiative touch? |
| Impact analysis | If this changes or fails, what else is affected? |
| Ownership & accountability | Who is accountable for what — and for which perspective? |
How they connect¶
These disciplines aren't silos — they share one graph:
- Capabilities give applications their purpose; an unmapped application is a question waiting to be answered.
- Applications sit between capabilities and technology; they're where most of the day-to-day cataloguing happens.
- Technology lifecycle risk becomes meaningful only through the applications that depend on it (blast radius).
- Data flows across applications; its classification raises governance stakes.
- Governance sets the rules; planning schedules the change; impact analysis tests the consequences before you commit.
- Ownership runs through all of it — accountability is what turns a diagram into a decision.
The recommended sequence for a team starting out is in the common first-session checklist. The short version: get applications in, sketch capabilities, link the two, set criticality, then layer on governance and planning.