Business Architecture Tools: Types, Selection and Comparison
What the main types of business architecture software do well, where each falls short, and how to choose between them.
By Capstera Business Architecture Staff · Updated
10 min read
Business architecture tools are the software used to build, maintain and share business architecture models: capability maps, value streams, organization and information models, and the relationships between them and strategy, initiatives and applications. They range from spreadsheets and diagramming tools to enterprise architecture suites and platforms built for business architecture. This article sorts the market into five types, compares them on what matters in practice, and sets out six questions to answer before talking to vendors. Capstera, which publishes this article, sells a business architecture platform; the comparison is by type of tool, and each type has a place.
Tool choice is one of the first questions a new business architecture practice asks, and one of the easiest to get wrong. A tool bought before the practice knows which decisions it supports tends to be configured around a vendor's metamodel rather than the organization's, and adoption stalls. The type of tool matters more than the brand within a type.
Key Takeaways
- There are five broad types of business architecture tool: office and diagramming tools, modeling tools, process modeling suites, enterprise architecture management suites, and business architecture platforms.
- The main dividing line is between drawing tools, where each diagram stands alone, and repository tools, where one model feeds many views.
- Who maintains the model and who reads it decides more than any feature list. Architect-centric tools struggle to reach business readers.
- Reference content, such as industry capability maps, shortens the first draft and keeps naming consistent.
- Start from the decisions the architecture must support, and move to a repository when several people need to keep one model consistent.
What Are Business Architecture Tools?
A business architecture tool is software for creating and maintaining models of what a business does and how it delivers value, and for connecting those models to strategy, change and technology.
At minimum, a business architecture tool lets you draw a capability map. A capable one also stores each capability as an object with a definition, an owner and attributes such as maturity and importance; relates it to value streams, organization units, information concepts, initiatives and applications; and produces views from that single model, such as heat maps, impact analyses and roadmaps, without redrawing anything.
That distinction, between drawing a picture and maintaining a model, is the most important one in the market. A drawing has to be updated by hand everywhere it appears. A model is updated once, and every view that uses it changes with it.
Types of Business Architecture Tools
Five types cover most of what organizations use. The names are generic on purpose: products change faster than categories do.
Office and diagramming tools, such as spreadsheets, presentation software, Microsoft Visio, Lucidchart or Miro, are where most practices start. They are familiar, cheap and flexible. They hold no relationships between objects, so every heat map or impact view is a separate, manually maintained picture.
Modeling tools, such as Sparx Systems Enterprise Architect, or Archi for the ArchiMate notation, store a real model and support formal notations. They suit architects comfortable with those notations; business readers usually need the output translated.
Process modeling suites, such as ARIS or SAP Signavio, are built around process models and process mining. They are strong where the main question is how work flows, and they can hold capability maps, but capabilities are usually secondary to processes.
Enterprise architecture management suites, such as LeanIX, Ardoq, Bizzdesign, MEGA HOPEX or Orbus iServer, provide a repository with a broad metamodel spanning business, application, data and technology. They are strongest on application portfolio management and IT planning, and typically need configuration and dedicated administration to serve business architecture well.
Business architecture platforms, Capstera among them, put the capability map, value streams and strategy at the center, provide business-readable views, and usually ship industry reference content. They are narrower than EA suites on application and technology portfolio management.
| Type | Best for | Main strength | Main limitation | Who maintains it |
|---|---|---|---|---|
| Office and diagramming tools | A first capability map; small or new practices | Familiar, cheap, flexible | No shared model; every view is redrawn by hand | Anyone |
| Modeling tools | Architects using formal notations such as ArchiMate | Rigorous models and notations | Output needs translating for business readers | Architects |
| Process modeling suites | Process design, process mining, operational excellence | Depth on processes | Capabilities and strategy are secondary | Process and operations teams |
| Enterprise architecture management suites | Application portfolio and IT planning across the enterprise | Broad metamodel across business and IT | Configuration effort; business views need tailoring | An EA team with an administrator |
| Business architecture platforms | Capability-based planning, investment and transformation decisions | Business-readable views; reference content | Narrower on application and technology portfolio management | Business architects, with business owners contributing |
How Do You Choose a Business Architecture Tool?
Answer six questions before comparing vendors. The answers usually point to one or two types, and the shortlist follows.
The decisions come first because they determine everything else. A practice that exists to support annual investment planning needs capability, importance and maturity attributes and a heat map; one that exists to rationalize applications needs capability-to-application mapping and an application inventory; one that supports operating model design needs organization and value stream views.
The readers come second. If executives and business owners are expected to read and maintain parts of the model, a tool that requires notation training will not reach them, however capable it is.
- Ask each vendor to load a sample of your own capability map and show the views your decisions need. Demonstrations on the vendor's sample data show the tool, not the fit.
- Check how the metamodel is changed, and by whom. Some tools are configured in the interface; others need a specialist.
- Ask who keeps reference content current, and whether you may adapt it.
- Confirm how data comes in and goes out: imports, APIs and exports in open formats, so the model is not locked in.
When to Move Beyond Spreadsheets
Spreadsheets and diagrams are a sound way to start. These signs show a practice has outgrown them.
- The same capability map exists in several versions, and nobody is sure which is current.
- Producing a heat map or an impact view means redrawing a diagram by hand.
- Capabilities need to be related to applications, initiatives or value streams, and the relationships live in separate spreadsheets.
- Several architects or business owners need to update the model at the same time.
- Leaders ask questions the architecture should answer, such as which initiatives touch a capability, and answering takes days.
Common Mistakes When Buying a Business Architecture Tool
Most disappointing tool purchases follow one of a few patterns.
- Buying before the framework exists. Without agreed definitions and naming rules, the tool's default metamodel becomes the framework by accident.
- Choosing on feature count. The longest feature list usually comes with the most configuration, and unused features still have to be administered.
- Planning for architects only. A model that business owners cannot read or update becomes the architecture team's private asset, and loses its sponsors.
- Ignoring the cost of content. A tool is empty on day one. Populating and maintaining the model costs more over time than the license.
- Skipping the exit question. If the model cannot be exported in a usable form, switching tools later means rebuilding it.
Frequently Asked Questions
What are business architecture tools?
Business architecture tools are software for building and maintaining business architecture models, such as capability maps, value streams and organization models, and for relating them to strategy, initiatives and applications. They range from spreadsheets and diagramming tools to enterprise architecture suites and dedicated business architecture platforms.
What is the difference between business architecture tools and enterprise architecture tools?
Enterprise architecture tools cover business, application, data and technology architecture in one repository and are strongest on IT portfolio management. Business architecture tools center on capabilities, value streams and strategy, with views written for business readers. Many EA suites can be configured for business architecture, and some business architecture platforms connect to EA suites.
Can you do business architecture in Excel?
Yes, to start. A capability map with definitions, owners and ratings fits in a spreadsheet, and many practices begin there. The limits appear when the map has to be related to applications, initiatives and value streams, or kept consistent by several people.
What should a capability mapping tool do?
Store each capability as an object with a definition, owner, level and attributes; show the map at different levels; color it by any attribute as a heat map; and relate capabilities to value streams, initiatives and applications so impact questions can be answered from the model.
How much do business architecture tools cost?
It varies widely, from free diagramming tools to enterprise suites priced per user or per module. Compare the cost of running the tool, including configuration, training and the time to keep content current, rather than the license alone.
Which business architecture tool is best?
The one that fits the decisions your practice supports and the people who will maintain and read the model. Decide the type of tool from those two answers first; comparing brands across types rarely produces a clear answer.
Pro Tips
- Run a pilot on one real decision, such as next year's investment plan for one domain. A pilot on a sample model proves only that the tool can draw.
- Count the people who will update the model each month. If the answer is one architect, the tool's collaboration features matter less than its import and export.
- Keep a copy of the capability map outside the tool, in an open format, for the first year.