OCSMP Model Builder Fundamental key terms

A simplified, purposeful representation of a system that omits irrelevant detail so engineers can reason about structure, behavior, and constraints before committing to costly physical implementation.

A set of interacting elements organized to achieve a purpose, treated as a whole while its environment lies outside its boundary.

The dividing line that separates what is inside a system from its environment, determining which elements the model owns and which are external actors or interfaces.

Any named, uniquely identifiable construct in a model, such as a package, block, activity, or requirement, that can own other elements and be referenced by relationships.

A namespace container used to group related model elements into logical units, controlling naming scope and enabling reuse or separate ownership of model content.

A model element that owns other named elements and gives them a scope, so the same simple name can be reused in different containers without ambiguity.

The containment relation in which one model element holds another, so deleting the owner deletes the owned elements and the owned element has exactly one owner.

A specification of the conventions, concerns, and stakeholders that one kind of diagram or model view must address, guiding which elements and relationships are shown.

A projection of a model that shows only the elements and relationships relevant to one viewpoint, hiding the rest of the model to reduce complexity for its audience.

A graphical presentation of selected model elements and relationships; it is a view onto the model, not the model itself, so the same element may appear on many diagrams.

An extension mechanism that lets a modeler define a new kind of model element with extra properties and constraints, applied to existing elements to refine their meaning.

A packaged collection of stereotypes, tagged values, and constraints that adapts the modeling language to a specific domain, methodology, or standard without changing its core metamodel.

A modeling-language construct that defines what kinds of model elements exist and what properties they have; stereotypes extend a metaclass such as Class or Component.

A named property attached to a model element through a stereotype, holding domain-specific metadata such as a safety level, owner, or unit of measure.

The fundamental structural element in systems modeling, describing a modular unit with features such as parts, ports, operations, and constraints that can be composed into larger structures.

A property of a block that is typed by another block, expressing that each instance of the whole owns instances of that type as its components.

A property typed by a block that represents a relationship to an object the owner does not own, distinguishing shared or external objects from owned parts.

A whole-part relationship in which the composite owns its parts, so the parts' lifetimes are bound to the whole and each part has one composite owner.

A weaker whole-part relationship in which the whole groups parts but does not own them, so parts can exist independently and be shared among several wholes.

A structural relationship between classifiers describing links between their instances, optionally with roles, multiplicities, and navigability at each end.

A taxonomic relationship in which a more specific classifier inherits the features of a more general one and may add or override features, supporting reuse and polymorphism.

A constraint on how many instances may participate at an association end or property, written as a range such as 1, 0..1, or 1..*, bounding valid configurations.

A specific occurrence of a classifier at runtime, having its own identity and slot values for the properties defined by its type.

A model element that describes a particular instance, naming its classifier and giving values for selected properties, often used to illustrate example configurations.

A point on a block through which it interacts with its environment or internal parts, typed by an interface to define what can flow in or out.

A port whose type is a classifier such as an interface block, delegating interactions to internal parts rather than exposing only individual flow properties.

A block that specifies a contract of features, such as operations and flow properties, that conforming ports provide or require across a system boundary.

A link between two parts or ports within a block that enables them to interact, carrying flows or delegating requests between internal and external features.

A statement of a capability or condition the system must satisfy, modeled as an element with an identifier and text so it can be traced, verified, and managed.

A diagram that shows requirements and their relationships to each other and to design elements, exposing containment, derivation, satisfaction, and verification links.

A dependency stating that one requirement is inferred from another, typically flowing from stakeholder needs down to more detailed system or component requirements.

A dependency asserting that a design element fulfills a requirement, providing the evidence link between captured needs and the model elements that meet them.

A relationship linking a requirement to the test case, procedure, or analysis that demonstrates the requirement is met, distinct from the design element that satisfies it.

A model element specifying the conditions, inputs, and expected results used to verify a requirement, often connected to requirements through verify relationships.

A general dependency recording that one model element has a meaningful link to another, used for impact analysis when either element changes.

A behavior model of coordinated actions with control and object flows, describing how work is performed or how a process transforms inputs into outputs.

A single step within an activity that consumes inputs, performs a transformation, and produces outputs, connected to other steps by flows.

A directed relationship in a behavior model that sequences execution, indicating that one action completes before the next begins.

A directed relationship that carries data or items from one action to another, showing what information moves through an activity rather than only its ordering.

A behavior model describing the discrete states an object can occupy, the events that trigger transitions, and the conditions guarding those transitions.

A condition during an object's life in which it satisfies some invariant, performs some activity, or waits for an event within a state machine.

A directed relationship between states or pseudostates in a state machine, taken when a trigger occurs and its guard condition evaluates true.

An interaction diagram that shows lifelines and the ordered messages exchanged between them over time, emphasizing the temporal order of interactions.

The vertical line in an interaction diagram representing one participant over time, along which messages are sent and received during the interaction.

A communication between lifelines in an interaction diagram that invokes an operation, sends a signal, or returns a result, ordered in time.

A behavior description of a sequence of interactions between a system and external actors that yields an observable result of value to a stakeholder.

A role played by a person, device, or external system that interacts with the system under consideration, drawn outside the system boundary.

A rule or restriction expressed on model elements, often as a formal expression, that must hold for the model or its instances to be valid.

A block that groups parameters and constraint expressions defining a reusable mathematical or logical rule, such as an equation relating mass, force, and acceleration.

A diagram that binds value properties of a system to the parameters of constraint blocks, showing how equations and rules constrain system properties.

A property typed by a value type that represents a quantifiable characteristic of a block, such as mass or voltage, with units and dimensions.

A classifier defining a kind of value together with its unit and dimension, such as kilograms or meters per second, used to type value properties.

A standardized quantity used as a reference for measuring a value type, such as second or newton, supporting dimensional consistency checks across a model.

A connector in a parametric diagram that equates the values of two properties, linking a system value property to a constraint parameter.

A relationship mapping elements of one model area to elements of another, such as requirements to design, or functions to the components that perform them.

A labeled compartment on a model element that lists the elements allocated to or from it, making allocation relationships visible without drawing every dependency.

A flow in an internal block diagram that specifies what is conveyed along a connector, including its type, direction, and rate.

A behavioral feature of a classifier that names a service the classifier provides, with parameters and a return type, implemented by methods.

A feature of a block or interface block indicating something that can flow in or out, such as matter, energy, or information, with a direction and type.