I85PREP
⌘ K
OCSMP Model Builder Fundamental study materials
OCSMP Model Builder Fundamental study resources

OCSMP Model Builder Fundamental: Model concepts and organization

OCSMP Model Builder Fundamental · Work through your exam, one topic at a time.

All guide sections

Model concepts and organization

Model concepts and organization covers the vocabulary the rest of the exam builds on: model elements and ownership, namespaces and imports, how diagrams relate to the model, and how a model is structured into packages and views. Questions here test whether you can navigate a model repository without confusing the picture with the thing pictured.

Model, element, diagram

A model is a set of interconnected elements. A diagram is one view of a chosen subset. Deleting a diagram never deletes elements; deleting an owning element deletes everything it owns.

Namespaces and packages

Every element is owned by exactly one namespace, so names need to be unique only inside that namespace. A qualified name chains owners from the root (UAV::Structure::FlightController). Packages are namespaces and containers; a public or private import makes names visible without moving ownership, and model libraries (SI units, ISO 80000 quantity kinds) should be imported, never copied.

Diagram taxonomy

SysML 1.x defines nine diagram kinds: Block Definition, Internal Block, Package, Parametric, Activity, Sequence, State Machine, Use Case, and Requirement. Allocation has no dedicated diagram kind; it is expressed with «allocate» dependencies and usually presented as a table or matrix.

Views and viewpoints

Following ISO/IEC 42010, a viewpoint is the convention for constructing a view, and a view is a model or subset conforming to it. Views are built by query or import, not by copying elements into a new package.

Worked example

A UAV team creates a root package UAV with child packages Structure, Behavior, Requirements, Parametrics, Verification. FlightController lives in Structure, Navigate in Behavior, and an «allocate» dependency in Verification links them. Adding a second Controller in Behavior does not clash, because the qualified names differ.

Traps

Treating a diagram as the model, expecting import to copy elements, assuming unqualified names are globally unique, and looking for an allocation diagram among the nine diagram kinds.