BUSINESS ARCHITECTURE · KNOWLEDGE BASE
A working knowledge base I’m building as I take on a Business Architecture Analyst role at Accenture — the frameworks, the core blueprints, and interactive artifacts to work the discipline. BIZBOK/TOGAF-aligned methodology and study, on a foundation of real delivery experience.
Business Architecture · The map
The blueprint that connects strategy to execution

Business Architecture

Business architecture is the blueprint of the enterprise from a business view — capabilities, value streams, organisation and information — used to align initiatives with strategy, expose gaps and overlaps, and guide transformation. This hub is where I work the discipline: the frameworks, the core-four blueprints, a reading path, and interactive artifacts you can explore. It sits alongside my ERP/SAP delivery work, not instead of it.

FrameworksBIZBOK · TOGAF ADM · ArchiMate
Core-fourCapability · Value · Organisation · Information
ArtifactsCapability map · value streams · traceability · TOM · glossary
ContextBusiness Architecture Analyst · Accenture
4core blueprints
22capabilities modelled
5value streams
55glossary terms
01 · What it is

Strategy on one side, execution on the other — the bridge is business architecture.

A business architect builds and maintains models of the enterprise so leaders can see what the business does, how value flows, and where to invest — then connects those models to strategy and to the change portfolio. The discipline organises around four foundational blueprints (the BIZBOK “core-four”):

02 · A reading path

From what, to how, to how it’s run.

The order the artifacts build on each other.

03 · The frameworks

The bodies of knowledge behind it.

BIZBOK

The Business Architecture Body of Knowledge (Business Architecture Guild) — defines the core blueprints and the techniques for capability, value, organisation and information.

TOGAF · ADM

An enterprise-architecture method; business architecture is Phase B of the Architecture Development Method, across the Business / Data / Application / Technology domains.

ArchiMate

The Open Group’s modelling notation for enterprise architecture, layered into business, application and technology.

04 · The artifacts

Explore each one.

Business Capability Map
A BIZBOK-aligned L1→L3 capability model across four tiers, with a maturity / priority heat-map and click-to-detail sub-capabilities.
heat-map toggle
Value Streams
Five end-to-end value streams (customer, business, employee) with each stage cross-mapped to the capabilities that enable it.
stage → capability cross-map
Information Map
The fourth BIZBOK blueprint — 14 conceptual information concepts across master, transactional and financial domains. Click any concept to light its related concepts with cardinality, and see the SAP object, capability, value stream and project behind it.
click to explore relationships
Organization Map
The third BIZBOK blueprint — 20 business units across governance, core, shared services and partners. Click a unit to light its reporting line, the units it oversees and its partners, and see the capabilities it owns, its value streams and decision rights.
click to trace ownership
Traceability Explorer
The golden thread across six layers — strategy → capability → value stream → initiative → RICEFW deliverable → test. Click any node to light its upstream ancestry and downstream descendants.
click to trace the thread
Target Operating Model
The seven dimensions an operating model is designed across, each with a current-state → future-state shift and its design levers.
current → future
Glossary & Frameworks
55 searchable terms — BIZBOK, TOGAF ADM, ArchiMate, the blueprints, techniques and roles — each with a plain-language definition.
live search
Self-Test Quiz
18 questions across Business Architecture and SAP FI/CO, with instant feedback and a best score saved in your browser.
active recall
HOW THIS CONNECTS TO MY DELIVERY WORK

Business architecture is a natural step up from implementation: I’ve delivered the systems that run capabilities (ERP go-lives, SAP FI/CO), and this is the discipline that decides which capabilities matter and how they’re organised. I’m building this depth as I take on the analyst role — framed honestly as methodology and study on a foundation of real delivery, not a claim of years of business-architecture practice.

See the delivery experience it builds on →