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

OCSMP Model Builder Intermediate: Parametric Constraints, Inter-relationships, and Model Quality

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

All guide sections

Parametric Constraints, Inter-relationships, and Model Quality

Parametrics, inter-relationships, and model quality

This domain tests constraint modeling, cross-element relationships, and whether the model is well-formed and conformant.

Core rules

  • A «constraint» block owns constraint expressions and parameters. A constraint property is typed by that block and appears on a parametric diagram.
  • Binding connectors assert equality between a constraint parameter and a value property, or between two parameters. Types, dimensions, and units must be compatible.
  • Parametric diagrams show constraint properties, their parameters, value properties, and binding connectors - not arbitrary blocks or associations.
  • Inter-relationships include «satisfy», «verify», «deriveReqt», «refine», «trace», and «allocate». «allocate» assigns responsibility, commonly from behavior to structure; it does not replace «satisfy».
  • Quality checks: every requirement has a unique id and verifiable text; every requirement is satisfied and verified; no dangling dependencies; all constraint parameters are bound; units are consistent; each diagram uses the correct element types for its kind.

Worked example

Constraint block BrakingDistance has parameters v: Speed, t: Time, d: Distance and the expression d = v*t + v^2/(2*mu*g). Vehicle has value properties speed, responseTime, and stoppingDistance. On a parametric diagram, add constraint property bd: BrakingDistance and bind bd.v to Vehicle.speed, bd.t to Vehicle.responseTime, and bd.d to Vehicle.stoppingDistance. Reasoning: each binding connector is an equality; units must resolve to metres, seconds, and m/s. If speed is in km/h, convert it in a value type or an additional constraint. An unbound parameter is a completeness defect.

Traps

Binding to a part instead of a value property; unit mismatch; treating a constraint block as a normal block; using «allocate» where «satisfy» is required; overusing «trace»; putting blocks on a parametric diagram; declaring a model conformant without checking verification coverage or binding completeness.