OCSMP Model Builder Fundamental study materials
OCSMP Model Builder Fundamental study resources

OCSMP Model Builder Fundamental study plan

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

8 weeks · About 6 hours per week

Week 1

Model concepts and organization & Purposes and benefits of modeling a system

  • Define the SysML model as a container of packages and explain how namespace ownership differs from containment

  • Classify each of the four SysML diagram categories (structure, behavior, requirement, parametric) and name the diagram types inside each

  • Draw a package containment hierarchy for a small system and label at least two views that serve different stakeholders

  • List five concrete benefits of a model over a document set, tying each to a stakeholder concern

  • Identify the modeling language constructs that support model organization, such as packages, imports, and view/viewpoint

Your checkpoint

A one-page model organization diagram with a package hierarchy, diagram taxonomy table, and five stakeholder benefit statements

Week 2

Model concepts and organization & Purposes and benefits of modeling a system

  • Explain the purpose of a viewpoint and show how it filters model content for a specific concern

  • Compare model-based and document-based approaches on change impact, consistency, and traceability

  • Describe the system-of-interest boundary and distinguish it from the environment and external actors

  • Build a small package structure that separates requirements, structure, behavior, and parametrics

  • Write a short justification memo that maps each modeling activity to a lifecycle phase

Your checkpoint

A boundary-and-viewpoint worksheet for a chosen system plus a 300-word memo justifying the modeling approach

Week 3

Basic requirements capture and management

  • Write at least ten well-formed textual requirements that each express a single verifiable statement

  • Model requirements in a requirement diagram with id, text, and rationale properties populated

  • Connect requirements using containment, derive, and satisfy relationships and explain when each is appropriate

  • Identify ambiguous or non-verifiable wording in a sample requirement set and rewrite each defect

  • Explain how requirement traceability supports impact analysis when a requirement changes

Your checkpoint

A requirement diagram with ten requirements, at least three derive links, and a defect log of five rewritten requirements

Week 4

Structure models

  • Build a block definition diagram with at least six blocks, showing composition and reference associations with multiplicities

  • Distinguish parts, ports, and connectors and place each correctly on an internal block diagram

  • Apply generalization and explain the inheritance of features between a subtype and its supertype

  • Define value properties with types and units and attach them to the correct owning block

  • Explain how a part's multiplicity affects the number of instances in the internal structure

Your checkpoint

A block definition diagram plus internal block diagram for a system with ports, connectors, multiplicities, and typed value properties

Week 5

Behavior models

  • Model an activity with inputs, outputs, control flow, and at least one decision node with guards

  • Build a state machine with entry and exit behavior and explain the difference between a state and an action

  • Write a sequence diagram with lifelines, synchronous and asynchronous messages, and a combined fragment

  • Explain when to choose activity, state machine, or sequence modeling for a given question

  • Trace a behavior to the block that owns it and to the requirement it satisfies

Your checkpoint

Three behavior diagrams for one scenario, each annotated with the question it answers and the requirement it traces to

Week 6

Parametric models

  • Define a constraint block with parameters, a constraint expression, and bound value properties

  • Build a parametric diagram that binds block value properties to constraint parameters

  • Explain how a parametric model enables trade studies and sensitivity analysis

  • Distinguish a constraint parameter from a value property and state why the distinction matters

  • Identify at least two common binding errors that make a parametric model unevaluable

Your checkpoint

A parametric diagram with two interacting constraint blocks and a written trade-study scenario that varies one parameter

Week 7

Allocation relationships

  • Explain what an allocation relationship asserts and how it differs from a satisfy relationship

  • Allocate behavior to structure using an allocation compartment or allocation table

  • Allocate requirements to design elements and verify that every requirement has at least one allocation

  • Explain how allocation supports impact analysis across abstraction levels

  • Review a model for orphaned or double-allocated elements and record each finding

Your checkpoint

An allocation table covering all requirements and behaviors of the sample system, plus a review log of allocation defects

Week 8

Use of stereotypes

  • Explain how a stereotype extends a metaclass and what a profile packages

  • Apply at least three standard or custom stereotypes and populate their tagged values

  • Distinguish a stereotype from a subclass and justify when each is the right tool

  • Review the full model for stereotype misuse, such as stereotypes replacing valid structure

  • Complete a timed practice set across all eight domains and score each domain separately

Your checkpoint

A custom profile with three stereotypes applied in the model plus a per-domain practice score report

Milestones

Week 2: Can name all four diagram categories, explain viewpoint filtering, and justify modeling over documents without notes

Week 4: Can build a block definition and internal block diagram with correct multiplicities and ports, and explain composition versus reference association

Week 6: Can state the difference between a constraint parameter and a value property and produce a bindable parametric diagram

Week 8: Scores at least 80 percent overall on a timed practice set with no domain below 70 percent