Business Architecture Knowledgebase (BIZBOK® Guide-Aligned)
What the knowledgebase organizes
The Business Architecture Body of Knowledge describes business architecture as a blueprint of the enterprise that provides a common understanding of the organization and is used to align strategic objectives and tactical demands. A candidate should be able to name the core domains and how they relate: strategy and its expression through value, capability, information, organization, and initiatives. The knowledgebase treats the capability map as a foundational view, with value streams describing how value is delivered to stakeholders, information concepts describing what the business must know, and organization maps describing who does the work.
Relationships, not lists
Questions often test relationships rather than definitions. Know that capabilities answer what the business does, value streams answer how value flows end to end, and organization maps answer who performs work. A common trap is confusing a capability with a process: a process is a sequence of activities, while a capability is an ability the business possesses regardless of process design. Another trap is treating the value stream as a department; value streams are cross-functional by nature.
Traps and terminology
Watch for questions that conflate the business architecture knowledgebase with a software repository. The knowledgebase is conceptual; tools are implementation choices. Also be ready to distinguish a business capability from an IT capability and to recognize that strategy, capability, and value are linked through mapping techniques such as capability-to-value-stream and capability-to-initiative heat maps.
Rule of thumb
When a stem asks where something belongs, ask: is it an ability (capability), a flow of value (value stream), a fact the business manages (information), or an accountable group (organization)? That four-way test resolves most classification items.