OCSMP Model Builder Advanced key terms

A model that defines the constructs, relationships, and rules available for building models in a language, so it describes what a valid model of that language may contain.

An OMG standard defining a layered architecture for metamodels, where M2 defines modeling languages, M1 holds user models, and M0 holds the modeled reality.

A UML/SysML extension mechanism that adapts the language to a domain by adding stereotypes, tagged values, and constraints without changing the underlying metamodel.

An extension of an existing metaclass that lets modelers apply domain-specific meaning and additional properties to elements such as blocks, associations, or activities.

A property defined on a stereotype that attaches domain-specific data, such as a safety integrity level or unit cost, to the model elements it extends.

A class in the metamodel whose instances are themselves model elements, such as Class or Association, and which a stereotype extends to add domain semantics.

A reusable package of model elements, such as quantity kinds, units, or interface definitions, that other models import instead of redefining common concepts.

A specification of the conventions, stakeholders, concerns, and allowed model kinds used to construct a view, ensuring each architectural perspective answers a defined set of questions.

A model projection that conforms to a viewpoint and presents only the information relevant to particular stakeholders, such as an interface or a safety view.

A standardized set of viewpoints, rules, and artifacts, such as DoDAF or UAF, used to organize architecture descriptions consistently across projects and organizations.

OMG standards that profile UML and SysML to express defense architecture frameworks, providing stereotypes for capability, operational, service, and resource views.

An OMG UML profile for modeling and analysis of real-time and embedded systems, adding constructs for timing, scheduling, resources, and performance analysis.

An automated operation that reads a source model and produces a target model, commonly used to convert SysML designs into analysis or simulation inputs.

An equation-based, object-oriented modeling language for physical systems whose models can be generated from or linked to SysML structural and parametric descriptions.

A formal language, such as QVT or ATL, that specifies transformation rules between metamodels so that model conversion is repeatable rather than manual.

An OMG standard serialization format for exchanging models between tools, encoding model elements and their relationships as XML for interoperability.

The ability of separate engineering tools to exchange models and data reliably, typically through standard formats, APIs, or shared repositories.

The ability to link model elements to requirements and follow those links in both directions, supporting impact analysis and verification evidence.

A system that stores, versions, and links textual requirements, integrated with the modeling tool so that model elements can satisfy or derive from them.

A SysML dependency that asserts a model element, typically a block or activity, fulfills a requirement, forming the basis of automated traceability reports.

The discipline of identifying, controlling, and auditing model versions and changes, including baselines, branches, and controlled access to shared repositories.

The practice of tracking changes to model elements over time, enabling comparison, rollback, and parallel work by multiple modelers on one model.

A fixed, approved snapshot of a model at a point in time, used as a reference for change control, reviews, and release of engineering data.

A structured evaluation of a model against criteria such as correctness, completeness, consistency, and readability, often using defined metrics and review checklists.

A quantified measure of a model property, such as element count, diagram density, or requirement coverage, used to judge quality objectively over time.

A planned examination of a model by peers or stakeholders against its purpose and standards, producing recorded findings and corrective actions.

A defined set of processes, roles, artifacts, and rules that guides how a team performs modeling work from requirements through verification.

An approach in which models, rather than documents, are the primary artifacts of systems engineering, supporting analysis, communication, and traceability across the lifecycle.

The activity of confirming that a system or model meets its specified requirements, often supported by trace links and test cases defined in the model.

A mechanism that makes elements from another package or library visible in a model, either by reference or by copy, affecting reuse and change propagation.

A SysML type whose instances are values without identity, such as quantities with units, used in parametric and property definitions to support engineering analysis.

A SysML diagram that binds constraint parameters to value properties, enabling engineering equations such as mass or power budgets to be evaluated against the design.

A stable unique key assigned to each model element, allowing tools to maintain trace links and merge changes even after elements are renamed or moved.

A shared, controlled database or file store holding models and their history, supporting concurrent access, locking, and configuration management for teams.