Business Architecture Frameworks
Frameworks as lenses
Frameworks provide structure for organizing architecture content and thinking. Candidates should recognize the major families without memorizing proprietary detail: enterprise architecture frameworks such as TOGAF and Zachman, business-focused approaches aligned to BIZBOK concepts, and lightweight modeling approaches. Know what each is good for. Zachman is a taxonomy of perspectives and abstractions; TOGAF offers an architecture development method and governance cycle; BIZBOK-style approaches focus on business capabilities, value streams, and their mapping.
Trap: framework as dogma
A common exam trap is treating one framework as mandatory or universally superior. Questions reward selecting a framework based on context - organizational maturity, regulatory needs, and stakeholder expectations. Another trap is confusing a framework with a modeling notation. A framework organizes content and process; a notation (such as BPMN or ArchiMate) expresses models.
Combining frameworks
Real practices blend frameworks. You might use a capability and value-stream approach for business content, an architecture development method for governance, and a notation for expression. Be ready to say which layer each contributes.
Worked example
A stem asks which framework best supports a taxonomy of architecture artifacts across perspectives. The answer points to a taxonomy-style framework such as Zachman, not to a development-method framework, because the question is about organizing artifacts by perspective rather than running a change cycle.
Reference Models
What reference models are
Reference models are reusable, industry-generic models that accelerate architecture work. They provide common vocabularies, baseline capability maps, value streams, and information models that organizations tailor rather than build from scratch. Candidates should know the categories: industry reference models, capability reference models, process reference frameworks, and data or information reference models.
Using them well
Reference models save time and improve comparability, but they are starting points. A frequent trap is adopting a reference model wholesale without tailoring to the organization's strategy and context. Another trap is treating a reference model as authoritative truth; it is a template. Questions may ask when a reference model is inappropriate - for example, when the organization's differentiation depends on a nonstandard capability that the generic model would flatten.
Traps in questions
Distinguish a reference model from a metamodel. A metamodel defines the types of elements and relationships you may use; a reference model provides example content within such a structure. Also distinguish a reference model from a framework: frameworks organize approach, reference models supply reusable content.
Rule of thumb
Adopt for the commodity, tailor for the differentiator. Use reference models to cover common capabilities quickly and invest customization where the business competes.
Governance
Governance defined
Architecture governance is the set of decision rights and processes that guide change against the architecture. It ensures that initiatives align with strategy, that standards are applied consistently, and that exceptions are visible and managed. Candidates should understand governance bodies (architecture review boards or equivalent), decision rights, exception handling, and the linkage to investment and portfolio decisions.
What governance is not
A common trap is equating governance with gatekeeping or bureaucracy. Effective governance enables change by clarifying decisions and reducing rework; it is not a veto machine. Another trap is placing architecture accountability in the governance body rather than with business owners. The board advises and recommends; accountable executives decide.
Mechanisms to know
Know the difference between principles, standards, and guidelines. Principles are durable statements guiding decisions; standards are mandatory rules; guidelines are recommended practices. Also understand compliance review, waivers or exceptions with expiry, and metrics that show governance effectiveness.
Worked example
A project requests a deviation from a standard. The correct handling is a documented exception with rationale, risk assessment, an approver with authority, and a review or expiry date - not silent approval or automatic rejection. That pattern captures the balance governance questions reward.