Framework Models, Views and Implementation
From framework to views to implementation
A framework's metamodel defines entity types and relationships. Viewpoints select the subset relevant to a concern; views are the resulting stakeholder-facing artifacts. Implementation is where architecture becomes actionable: principles, standards, and roadmaps guide projects, and governance ensures conformance.
Concepts to master
Understand viewpoint libraries and architecture descriptions; reference models (business, data, application, technology); and building blocks (architecture building blocks vs. solution building blocks). Know architecture governance (compliance reviews, dispensations/waivers, architecture board) and architecture contracts between architecture and implementation teams. Recognize capability as an ability to achieve an outcome, distinct from a process or a system.
Traps
Don't equate a viewpoint with a single diagram. Don't assume governance means blocking projects - it enables controlled deviation via waivers. Watch for confusing architecture building blocks (reusable, conceptual) with solution building blocks (implemented components). Another trap: treating the framework as the deliverable rather than the architecture description.
Worked example
A project wants to skip a mandated standard. The correct response is not "deny" or "ignore," but route a dispensation/waiver through the architecture board with documented rationale and a remediation plan. This preserves governance while allowing justified deviation.
Rule of thumb
Framework → viewpoint → view → model/diagram is a zoom-in chain; each level answers a different question. For governance questions, prefer the answer that documents, reviews, and decides over one that simply blocks.