Free Intel — Object Semantics

INT-01 · REFERENCE

The UAF 1.2 Grid

Every view specification in the framework: viewpoints as rows, aspects as columns. Select any cell to read its code. Naming follows the convention Viewpoint-Aspect — St-Sr is Strategic Structure.

Viewpoint	MvMotivation	TxTaxonomy	SrStructure	CnConnectivity	PrProcesses	StStates	SqSequences	IfInformation	PmParameters	CtConstraints	RmRoadmap	TrTraceability

SELECTED VIEW

St-Mv

Strategic Motivation

Chapters 7–21 of the reference walk every cell of this grid — concerns, elements, and worked views.

Get the full reference →

INT-06 · EXPLAINER

Views vs. Viewpoints

The most commonly confused distinction in the framework — and a reliable exam theme.

VIEWPOINT

The governing rules

A viewpoint frames architectural perspective: it names the stakeholder concerns being addressed and governs the conventions — the kinds of elements, relationships and correspondence rules — that any conforming view must follow. Strategic, Operational, Services and the rest are viewpoints.

VIEW

The expression

A view is what you actually produce and read: an expression of the architecture from its governing viewpoint, addressing those concerns for a specific system of interest. A view conforms to its viewpoint the way a chapter conforms to its outline.

VIEW SPECIFICATION

The pattern

UAF's grid cells — St-Sr, Op-Cn, Rs-Rm — are view specifications: named patterns of expression that state which elements and relationships a view of that kind presents. The Grid organizes all of them by viewpoint and aspect.

INT-02 · VOCABULARY

Core glossary

The working vocabulary the rest of the framework depends on, in the book's own framing.

Architecture: The fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and principles of design and evolution — something a system possesses even if never written down.
Architecture Description: The artifact that expresses an architecture. In UAF it is realized as a machine-readable, semantically precise model conforming to the framework — not a folder of drawings.
Model: A structured representation: the underlying repository of elements and relationships from which views are generated, kept consistent because every view draws on the same model.
Stakeholder concern: The driver of structure. Every view specification exists because some stakeholder needs a particular question answered; concerns determine what a view must show.
DMM — Domain Metamodel: The conceptual layer of UAF: the formal definition of every element, relationship and view specification, independent of any notation.
UAFML: The UAF Modeling Language: the SysML-based profile that implements the DMM, giving each concept a concrete, machine-readable stereotype and notation.
Conformance: What it means for an architecture description to be UAF: populating views according to their specifications, using elements and relationships as the DMM and UAFML sanction them.
Architectural Intent: What the Model User certification tests: the ability to correctly interpret UAF-based architectures — reading structure and meaning — rather than implementing or extending the modeling language.

INT-05 · METHOD

A study roadmap

The sequence the book itself recommends for first-time certification candidates.

Foundations first — Chapters 1–6

The certification's shape, UAF's origins, the vocabulary (architecture, description, view, viewpoint), the four-layer metamodel, and the Grid. Everything later depends on these distinctions being exact.

The domain viewpoints — Chapters 7–17

Architecture Management through Actual Resources: each viewpoint's concerns, elements and view specifications. Read with the Grid beside you; the naming convention does half the memorization.

Cross-cutting views — Chapters 18–21

Environment, Measurements, Risk and Requirements — compact chapters, but they thread through every domain and the exam expects you to know where they attach.

Representation and analysis — Chapters 22–24

How views are drawn in SysML terms, how traceability chains run end to end, and the six model-analysis types — the reasoning layer the hardest exam questions live in.

Drill with the appendices, then practice

A1 terms, A2 stakeholders, A3 exam coverage — then a full-length timed practice exam to find your gaps before the real one.

INT-04 · SELF-CHECK

Sample questions

Five questions in the certification's style, with rationale. The full practice exams contain complete timed sets.

Q1An architecture exists only once it has been documented in a conforming model. True or false?

False. The architecture is the fundamental concepts and properties of the system itself — it exists even if never written down. The architecture description is the artifact that expresses it.

Q2What does the code St-Rm-D identify?

Strategic Roadmap: Deployment. Codes read Viewpoint-Aspect(-Qualifier): Strategic viewpoint, Roadmap aspect, Deployment variant — its sibling is St-Rm-P, Phasing.

Q3Which artifact governs the conventions a view must follow — the view, the viewpoint, or the model?

The viewpoint. It frames the stakeholder concerns and the rules of expression; the view is the conforming expression; the model is the repository both draw from.

Q4Requirements does not define its own Requirement stereotype. Where does it come from?

Imported from SysML. UAF adopts and extends the SysML Requirement rather than defining a native one — which is why Requirements is a cross-cutting view rather than a domain of its own.

Q5At the Model User level, what is primarily being assessed?

Interpretation, not implementation. The MU certification validates that a candidate can correctly read UAF-based architectures — Architectural Intent — not extend the metamodel or configure tools.

Start learning
at no cost.