OCSMP Model Builder Advanced flashcards
OCSMP Model Builder Advanced · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- SysML profile definition
- A UML Profile that extends UML metaclasses with stereotypes, each having tagged values and OCL constraints; applying it to a package makes its stereotypes available for that package.
- Stereotype extension multiplicity
- An Extension association from a stereotype to a metaclass has multiplicity 0..1 on the stereotype end and 1 on the metaclass end; isRequired=true forces application on every instance.
- Model library stereotype
- A package stereotyped «modelLibrary» holding reusable elements referenced by user models; it is not instantiated and its elements are imported, not copied.
- SysML viewpoint and view
- A «viewpoint» is a Requirement-like element specifying stakeholders and concerns; a «view» is a model element conforming to exactly one viewpoint and showing only permitted notation.
- Block stereotype base metaclass
- «Block» extends UML Class; it adds isEncapsulated and may own value properties, parts, ports, and operations. «ValueType» extends DataType for quantities with units.
- Profile application transitivity
- If Profile A imports Profile B, applying A to a package makes B's stereotypes available but does not apply B to the model; B must be applied separately if required.
- Viewpoint conformance dependency
- A dependency from a «view» to a «viewpoint» declares conformance; the view's diagrams must respect the viewpoint's stakeholder concerns and permitted diagram types.
- SysML-to-UML mapping
- Block maps to Class, ValueType to DataType, ItemFlow to InformationFlow with ItemProperty, and Allocate to Abstraction with «allocate»; every SysML model is a valid UML model.
- MARTE and SysML integration
- MARTE extends UML for real-time systems; integration pairs MARTE «Resource» and «SchedulableResource» stereotypes with SysML blocks and uses SysML ValueTypes for unit-consistent non-functional properties.
- UPDM and SysML integration
- UPDM (now UAF) is a UML/SysML profile for DoDAF/MODAF; integration maps SysML internal block diagrams to operational/resource views and UPDM «Capability» to SysML requirements.
- Modelica connector mapping
- In SysML-to-Modelica transformation, SysML ports map to Modelica connectors, value properties to Modelica variables with units, and constraints to equations; blocks map to models.
- QVT transformation rules
- Model transformation from a SysML profile to a target metamodel uses QVT or ATL rules that must preserve units, types, and interface directionality across the mapping.
- FMI/FMU co-simulation wrapper
- A SysML block's behavior is exported as a Functional Mock-up Unit; its ports map to FMU input/output variables so the model can co-simulate with other engineering tools.
- Simulink block profile
- A profile stereotyping blocks as «SimulinkBlock» maps value properties to Simulink signals; algebraic loops must be resolved before transformation to executable form.
- Cross-language semantic mapping table
- A table aligning constructs: SysML ItemFlow to Modelica connector flow, SysML «Allocate» to UPDM «Implements», and SysML «Requirement» to UPDM «Capability».
- OSLC and ReqIF
- OSLC is a REST-based linked-data standard for lifecycle tool integration; ReqIF is a file-based requirements interchange format. Both link SysML requirements to external requirement tools.
- External requirement proxy element
- A model element representing an external requirement, carrying its stable external ID and linked by «satisfy» or «deriveRequisite»; the ID must persist across imports to avoid duplicates.
- Identity mapping for round-trip sync
- A persistent mapping between external requirement IDs and model element GUIDs; without it, re-importing from the requirements tool creates duplicate elements and breaks traceability.
- Model repository baselines
- Configuration management integration stores SysML models as versioned baselines in a repository; cross-model references must be resolved by version-qualified identifiers.
- XMI diff and merge
- When a CM tool stores models as XMI, differences are computed on XMI and merge conflicts are resolved at the element level, not at the diagram level.
- Traceability matrix export
- An export of «satisfy» and «allocate» links to the requirements tool must include source and target IDs and the model baseline identifier for auditability.
- Authoritative attribute ownership
- In CM/RM integration, each attribute must have one authoritative system (model or requirements tool); conflicting edits are resolved by that owner, not by last-write-wins.
- Post-sync consistency check
- After each synchronization, validate that every external requirement has at least one «satisfy» link and every link resolves to an existing external ID.
- Model quality dimensions
- Syntactic quality is well-formedness against the metamodel; semantic quality is consistency, completeness, and correctness; pragmatic quality is usefulness to stakeholders. Assessment must name the dimension.
- OCL validation rules
- Constraints from the metamodel and profiles expressed in OCL, such as no cyclic generalization or every port typed, are checked automatically by the modeling tool during validation.
- Requirement coverage metric
- The percentage of requirements with at least one «satisfy» link to a design element; a common quality target is 100% coverage per baseline.
- Interface completeness check
- A quality rule requiring every port to have a type and direction, and every connector to join compatible ports; violations indicate incomplete interface definitions.
- Allocation completeness metric
- The percentage of logical elements allocated to at least one physical element via «allocate»; incomplete allocation signals gaps in the design-to-architecture trace.
- Orphan and proxy checks
- Consistency checks that flag elements with no relationships (orphans) and unresolved external references (proxies), both of which indicate model integrity problems.
- Methodology framework conformance
- Quality assessment verifies the model follows the chosen framework (OOSEM, Harmony, MagicGrid) in package structure, artifact set, and prescribed diagram usage.
- Traceability link density
- The ratio of actual trace links to possible trace links between requirements and design; combined with link correctness, it measures traceability quality.
- Repeatable quality assessment
- A quality process that defines metrics, thresholds, and review steps, and records results per baseline so trends across model versions can be compared.