OCSMP Model Builder Intermediate key terms

A SysML stereotype applied to a class-like element that captures a text statement of capability or condition, plus an identifier and optional rationale, and can be related to other model elements by satisfy, derive, verify, refine, and trace links.

A dependency from a block or other model element to a requirement asserting that the supplier element fulfils the requirement, typically drawn with the «satisfy» keyword and read as the client satisfying the supplier.

A dependency linking a test case or verification element to the requirement it checks, indicating the evidence that demonstrates whether the requirement is met; distinct from satisfy, which asserts design fulfilment.

A dependency between requirements showing that one requirement is derived from another, usually because a higher-level requirement is decomposed into more detailed, traceable child requirements.

A general dependency that records an arbitrary traceability link between a requirement and any other model element, used when satisfy, derive, verify, or refine do not precisely describe the relationship.

A dependency from a model element to a requirement stating that the element provides additional detail, structure, or analysis that elaborates the requirement's meaning beyond its text statement.

The composite ownership relationship in which a requirement owns nested requirements, forming a hierarchy shown in a requirement diagram; containment is structural ownership and is not the same as a derive dependency.

A SysML diagram frame whose primary purpose is to show requirements, their textual properties, and relationships such as containment, derive, satisfy, verify, refine, and trace among requirements and other elements.

A comment-like property of a requirement or other element that records the reasoning, justification, or design decision behind it, helping reviewers understand why the element exists in its current form.

A SysML stereotype on a comment used to record an issue, concern, or open question associated with a model element, often annotated with a severity or status so reviewers can track resolution.

The fundamental SysML structural element, a class stereotyped «block» that can own properties, operations, ports, connectors, constraints, and behavior, and serves as the type for parts and references in a model.

A property typed by a block and owned through a composite association, representing a whole-part relationship in which the containing block owns the lifetime of the part instance.

A property typed by a block that refers to an instance owned elsewhere, expressed with a non-composite association, so the referenced object can exist independently of the referring block.

An association with a filled-diamond end denoting strong whole-part ownership, where destroying the whole destroys its parts and the parts cannot be shared among multiple wholes.

A SysML structure diagram that shows blocks, their features, and relationships such as generalization, associations, and dependencies, typically depicting the type-level taxonomy rather than instance configurations.

A SysML structure diagram framed on a single block that shows its internal parts, ports, connectors, and item flows, revealing how the block's components are wired together to realize its behavior.

A property of a block that specifies a distinct interaction point through which the block exchanges items or services with its environment, typed by an interface block or a flow specification.

A port whose type defines the features the port exposes but which does not itself own those features; requests arriving at a proxy port are forwarded to the owning block's internal parts.

A port that owns its own features and behavior, so interactions at the port are handled by the port itself rather than being delegated to internal parts of the owning block.

A block used as the type of a port or connector that defines the operations, receptions, and flow properties available across that interaction point, often realized by a conforming block.

A relationship in an internal block diagram linking two parts or ports, enabling them to interact; it may be typed by an association or interface block and can carry item flows.

A flow of items along a connector between parts or ports, defined by a flow property and often typed by a block or value type, showing what material, energy, or information moves across the connection.

A property of a block or interface block that identifies something that can flow through a connector, such as fuel, a signal, or data, and gives the direction and type of that flow.

A taxonomic relationship in which a specific block or classifier inherits features from a more general one, shown with a hollow-triangle arrow, supporting reuse and polymorphic substitution in the model.

A SysML stereotype on a data type used to represent quantities, units, and dimensions, allowing properties to be typed with measurable values that support unit consistency and parametric analysis.

A model element associated with a value type that names a measurement scale, such as kilogram or second, and supports conversion and dimensional checking of quantities in the model.

A kind of quantity, such as length, mass, or time, associated with a value type that defines what is being measured and supports dimensional consistency checks across parametric constraints.

A SysML behavior element that describes a flow of actions connected by control and object flows, used to specify behavior at a level that can be allocated to blocks and decomposed hierarchically.

A step within an activity that represents a unit of work, which may be typed by a behavior such as an activity or operation, and which consumes inputs and produces outputs through pins.

A kind of activity edge that sequences actions by transferring control from one action to the next without carrying object data, determining execution order in an activity.

A kind of activity edge that carries objects or data from an output pin of one action to an input pin of another, representing the movement of information or material during execution.

A small object node on the boundary of an action that holds inputs or outputs of that action, typed by a classifier and used to connect object flows between actions.

A SysML behavior describing the states of an object and the transitions triggered by events, used to specify reactive or mode-dependent behavior of a block over its lifetime.

A condition or mode in a state machine during which an object satisfies certain invariants, may perform entry, do, and exit behaviors, and may contain nested regions with substates.

A directed relationship between states in a state machine that fires when its trigger event occurs and its guard is true, executing optional effect behavior while moving the object between states.

A boolean condition attached to a transition that must evaluate true for the transition to fire, allowing the same trigger to lead to different target states depending on model state.

A container within a state machine or composite state that holds states and transitions, enabling orthogonal concurrent regions or nested sequential decomposition of state behavior.

A SysML behavior element that describes a set of interactions between a system and external actors yielding an observable result of value, used to scope system capabilities from a user perspective.

A role played by a person, external system, or device that interacts with a system's use cases, depicted outside the system boundary and typically connected to use cases by associations.

A SysML behavior diagram showing interactions among lifelines ordered in time, with messages exchanged between them, used to specify scenarios and verify behavior against requirements.

A vertical line in a sequence diagram representing an individual participant in an interaction, along which messages are ordered and execution occurrences are shown.

A communication from one lifeline to another in a sequence diagram, which may be synchronous, asynchronous, or a reply, and which can be typed by an operation or a signal.

A SysML block stereotyped «constraint» that groups parameters and a constraint expression, such as an equation, and can be reused and bound to value properties in parametric diagrams.

A property whose type is a constraint block, placed inside a block or parametric diagram so its parameters can be bound to value properties, making the equation part of the owning block's definition.

A property of a constraint block that represents a variable in the constraint expression, which must be bound to a value property or other parameter before the constraint can be evaluated.

A connector in a parametric diagram that equates the values of two properties, binding a constraint parameter to a value property so changes propagate through the equation.

A SysML diagram that shows constraint properties and their parameters bound to value properties via binding connectors, expressing equations and their interrelationships without prescribing computation order.

A cross-cutting relationship that maps elements from one model area to another, such as allocating activities to blocks or requirements to design elements, often shown on an allocation table or diagram.

The degree to which a model obeys language rules, such as well-formedness constraints, correct stereotype usage, and consistent relationships, plus method rules such as naming, traceability, and completeness conventions.