OCSMP Model Builder Intermediate study materials
OCSMP Model Builder Intermediate study resources

OCSMP Model Builder Intermediate study plan

OCSMP Model Builder Intermediate · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Requirements modeling with the full SysML feature set (detailed and precise requirements modeling)

  • Distinguish requirement, requirement container, and derived requirement semantics, and state when each stereotype applies.

  • Write five textual requirements that each pass a singularity, verifiability, and ambiguity check, then rewrite two deliberately weak ones.

  • Build a requirement containment hierarchy with at least three levels and identify which elements are containers versus leaf requirements.

  • Configure requirement IDs, text, and rationale properties so every requirement is traceable by identifier.

Your checkpoint

A one-page requirement quality checklist plus a 15-requirement containment model with IDs, text, and rationale populated for every element.

Week 2

Requirements modeling with the full SysML feature set (detailed and precise requirements modeling)

  • Create satisfy, derive, refine, trace, and copy relationships and explain the direction and allowed endpoints of each.

  • Justify why satisfy links a requirement to a block rather than to another requirement, and correct three mis-typed links.

  • Apply requirement-relationship constraints to reject at least four invalid link attempts and document the rule violated.

  • Model a derived requirement whose derivation is explained by an explicit rationale property.

Your checkpoint

A traceability matrix exported from the model showing every requirement satisfied by at least one block or explicitly flagged as unallocated.

Week 3

Structure modeling with the full SysML feature set (detailed and precise structure modeling)

  • Build a block definition diagram with generalization, composition, and shared aggregation, and defend each aggregation choice in writing.

  • Define value properties with units and dimensions and verify that incompatible unit assignments are rejected.

  • Specify multiplicity, direction, and navigability on every association end and resolve two ambiguous ends.

  • Create ports and interfaces that type them, then show which connectors are legal between typed ports.

Your checkpoint

A structural model of a small system with at least 12 parts, fully typed ports, and a written justification table for every aggregation and multiplicity decision.

Week 4

Structure modeling with the full SysML feature set (detailed and precise structure modeling) & Parametric constraints and inter-relationships among model elements and diagrams, including assessment of model quality and conformance to language and method constraints

  • Produce an internal block diagram whose parts, connectors, and item flows are consistent with the definition diagram.

  • Distinguish reference versus part properties and correct three cases where the wrong one was used.

  • Assign constraint properties to blocks and connect their parameters to value properties so the parametric model is well-formed.

  • Evaluate a peer-style model against naming, typing, and completeness rules and log every defect found.

Your checkpoint

An internal block diagram plus parametric binding for one subsystem, accompanied by a defect log of at least 10 findings with severity ratings.

Week 5

Behavior modeling with the full SysML feature set (detailed and precise behavior modeling)

  • Model an activity with control flow, object flow, and at least one decision and merge pair, ensuring token flow is unambiguous.

  • Differentiate activity partitions from allocations and apply each where appropriate.

  • Write state machine transitions with triggers, guards, and effects, and eliminate two transitions that can fire simultaneously.

  • Specify an interaction with lifelines, synchronous and asynchronous messages, and combined fragments for a loop and an alternative.

Your checkpoint

A behavior package containing one activity, one state machine, and one sequence diagram for the same scenario, with a note explaining how the three views stay consistent.

Week 6

Behavior modeling with the full SysML feature set (detailed and precise behavior modeling) & Requirements modeling with the full SysML feature set (detailed and precise requirements modeling)

  • Link behavioral elements to requirements via satisfy and refine so each functional requirement has behavioral evidence.

  • Model a use case with actors and include or extend relationships, and justify each relationship choice.

  • Verify that every requirement in the week-1 set is now covered by structure, behavior, or an explicit gap note.

  • Trace one end-to-end scenario from requirement through behavior to structural part.

Your checkpoint

A coverage report listing each requirement against its satisfying block or behavior, with a named owner for every remaining gap.

Week 7

Parametric constraints and inter-relationships among model elements and diagrams, including assessment of model quality and conformance to language and method constraints

  • Construct a parametric constraint network with at least three interdependent constraints and confirm units propagate correctly.

  • Diagnose and fix an over-constrained and an under-constrained parameter set, documenting the symptom of each.

  • Apply method and language conformance checks: stereotype validity, relationship legality, and diagram completeness.

  • Rank model quality findings by risk and propose a remediation order.

Your checkpoint

A constraint network with a written diagnosis of two solved and two unsolved parameter configurations plus a prioritized remediation list.

Week 8

Requirements modeling with the full SysML feature set (detailed and precise requirements modeling) & Structure modeling with the full SysML feature set (detailed and precise structure modeling) & Behavior modeling with the full SysML feature set (detailed and precise behavior modeling) & Parametric constraints and inter-relationships among model elements and diagrams, including assessment of model quality and conformance to language and method constraints

  • Assemble an integrated model spanning requirements, structure, behavior, and parametrics for a single system.

  • Run a self-audit against all four domain checklists and correct every high-severity defect.

  • Rehearse explaining five modeling decisions aloud in under two minutes each.

  • Complete a timed mixed-domain practice set and review every missed item to root cause.

Your checkpoint

An integrated model plus a completed self-audit scorecard showing zero open high-severity defects across all four domains.

Milestones

Week 2: Every requirement has an ID, text, and rationale, and each is either satisfied by a block or explicitly marked unallocated with a reason.

Week 4: Definition and internal views agree on parts and connectors, and every constraint property has typed parameters bound to value properties.

Week 6: Each functional requirement traces to at least one behavioral element, and any uncovered requirement has a named gap owner.

Week 8: Self-audit scorecard shows no open high-severity defects in any of the four domains and the integrated model is internally consistent.