Enterprise Architecture Software

Enterprise architecture software for the architecture team

Enterprise architecture (EA) software supports the practice of cataloguing the firm's business, data, application, and technology architecture, defining target-state, building the transition roadmap, and governing change against that roadmap. This page shows the EA practice cycle as a BPMN process map and covers the platform options most architecture teams choose between.

By Jack Finnegan · Updated 21 May 2026

Map your EA cycle Application portfolio management

What it is

What enterprise architecture software actually is

Enterprise architecture (EA) software is the category of platform that supports the EA practice. The classic reference is TOGAF (The Open Group Architecture Framework), which structures architecture around four domains: business, data, application, and technology. Modern EA platforms support cataloguing each domain (the inventory), defining target-state architecture, building the transition roadmap, governing change requests against the roadmap, and reporting to executive sponsors.

Major platforms include LeanIX (acquired by SAP in 2023, now SAP LeanIX), Ardoq, Bizzdesign (which absorbed MEGA HOPEX in September 2024 and Alfabet from Software GmbH in January 2025, now offering Horizzon, HOPEX, and Alfabet as a combined portfolio), ARIS (the standalone business that launched in January 2025 following the Software AG restructure), and ServiceNow EA. Smaller architecture teams often combine a lightweight cataloguing tool with a diagramming layer (BPMN, ArchiMate) for visualisation. The category overlaps significantly with application portfolio management and business capability modelling.

The problem today

The architecture catalogue is a year out of date and everyone knows it

Most EA catalogues drift the moment they ship. The architects move on; the platform owners change; the live application landscape evolves three times faster than the catalogue refresh cycle. Within 12 months the catalogue is materially wrong, and within 24 months the architecture team has lost the political confidence to be quoted as the source of truth. The result is shadow architecture - the real architecture lives in spreadsheets the platform leads maintain individually, and the EA platform becomes a museum.

The fix is treating the catalogue and the roadmap as working artefacts that are touched by every governance review, not annual deliverables. BPMN process maps of the architecture-governance workflow itself make the touchpoints visible: every change request goes through the same flow, every approved change updates the catalogue, every catalogue change feeds the next roadmap iteration.

Four pillars

Four pieces of an EA practice

Current-state catalogue

A maintained inventory of business capabilities, data domains, applications, and technology. Without this the rest of the practice is unmoored.

Target architecture

A described target state for each domain, aligned to the business strategy and operating model. Specific enough to make decisions against, abstract enough to survive tactical reorganisations.

Transition roadmap

The sequenced changes between current and target - the implementable artefact most stakeholders engage with.

Architecture governance

A working review process for change requests. Where most EA practices fail - the governance becomes a bottleneck or a rubber stamp instead of a living conversation.

Process Map

The EA practice cycle as a process map

The cataloguing → target → roadmap → governance loop, with the explicit deviation-review branch for changes that depart from the roadmap.

Open in editor

The enterprise architecture practice cycle as a process map

A TOGAF-aligned enterprise architecture cycle rendered as a BPMN 2.0 process. Catalogue current-state architecture, define target architecture, build the transition roadmap, govern change requests, and feed the result back to portfolio decisions.

Catalogue the current-state architecture: business, data, application, technology layers.
Define target-state architecture aligned to the business strategy and operating model.
Build the transition roadmap - the sequence of changes between current and target.
For every change request, run architecture governance against the target.
If the change is on-roadmap, approve; otherwise loop back to refine the target architecture before approval.
Execute approved changes, update the catalogue, and feed monitoring back into the next cycle.

What this diagram shows: The cycle starts at kickoff (annual or biannual). Cataloguing the current state refreshes the inventory. Target architecture is reviewed against the business strategy; the transition roadmap sequences the changes between current and target. Architecture governance runs continuously for change requests; the on-roadmap gateway routes deviations to a deviation review for explicit decision-making rather than ad-hoc accept/reject. Execution updates the catalogue, closing the loop into the next cycle.

FAQ

Frequently asked questions

What is enterprise architecture software?

Enterprise architecture software supports the EA practice - cataloguing the firm's architecture across business, data, application, and technology domains, defining target-state, building roadmaps, and governing change. Major platforms include SAP LeanIX, Ardoq, Bizzdesign (which now also owns the MEGA HOPEX and Alfabet products), ARIS, and ServiceNow EA.

What is TOGAF and how does it relate to EA software?

TOGAF (The Open Group Architecture Framework) is the most widely-adopted EA framework. It defines an Architecture Development Method (ADM) - the canonical cycle EA teams run - and a content metamodel (the structure of the architecture artefacts). Most EA platforms align to TOGAF as their default methodology, though many also support ArchiMate notation and lighter-weight variants.

What is the difference between EA software and APM software?

Application portfolio management (APM) is one slice of EA - specifically the application-domain inventory plus scoring (Gartner TIME: Tolerate, Invest, Migrate, Eliminate) and rationalisation decisions. EA software covers all four domains (business, data, application, technology) plus the target-state and roadmap layers. Many platforms (LeanIX, Bizzdesign, Ardoq) include both; some focus mainly on APM.

How does process mapping fit into EA?

Process mapping sits in the business architecture domain. BPMN process maps describe how capabilities are operationalised - the steps, decisions, and handoffs that turn the abstract "capability" into work people actually do. Strong EA practices anchor every business capability to one or more process maps; weak ones leave capabilities as bullet points in a catalogue.

Does BA Copilot replace LeanIX / Bizzdesign / Ardoq?

No. BA Copilot is the BPMN modelling layer - it produces the process maps that anchor business capabilities to operational reality. The dedicated EA platforms own the catalogue, the target architecture, the roadmap, and the governance workflow. BA Copilot integrates by exporting BPMN that the EA platform can attach to capability or application records.

Jack Finnegan, Founder & CEO, BA Copilot

From the founder

14 Years in BPMN

I'm Jack Finnegan. I've spent fourteen years working hands-on with BPMN, as an analyst, an engineer, and a product director, where I felt every sharp edge of legacy business process platforms.

BA Copilot is the platform I wanted on every one of these projects: AI-first process management, which treats BPMN as a first-class output rather than an export afterthought.

Jack Finnegan on LinkedIn

Anchor EA to real processes

Open the EA cycle template, customise the governance flow to your decision rights, and produce the BPMN process maps that anchor capabilities to the work people actually do.