OCSMP Model Builder Fundamental flashcards
OCSMP Model Builder Fundamental · 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.
- Model vs view
- A model is the set of elements and relationships; a view is a selected projection of it. Changing a view does not create or delete model elements.
- Qualified name
- A name formed by the chain of owning namespaces, such as Package::Subpackage::Element. It uniquely identifies an element within the model.
- Package import visibility
- A public package import makes imported elements visible to clients of the importing package; a private import makes them visible only inside the importing package.
- Diagram deletion semantics
- Deleting a diagram removes only that view. Deleting an element removes it from the model and from every diagram that displays it.
- Dependency vs association
- A dependency is a directed supplier/client relationship with no instances. An association is structural, has multiplicities, and links instances.
- Purpose of abstraction
- A model omits detail irrelevant to the questions it must answer. Its fidelity is chosen by purpose, not by trying to represent everything.
- MBSE primary artifact
- In model-based systems engineering the model is the authoritative artifact. Documents, reports, and diagrams are generated from it rather than maintained separately.
- Simulation benefit
- Behavior and parametric simulation lets engineers evaluate alternatives and detect design errors before hardware exists, reducing the cost of late rework.
- Model quality attributes
- Correctness, consistency, completeness relative to purpose, and comprehensibility. A model can be complete for one purpose and incomplete for another.
- Traceability benefit
- Links between requirements and design elements make impact analysis a query. A requirement change reveals affected elements through derive and satisfy links.
- Requirement element
- A SysML Requirement is a UML Class with the requirement stereotype. It carries a unique id and text and can own subrequirements by containment.
- Satisfy relationship
- A «satisfy» dependency goes from a design element to a requirement, asserting that the design element meets that requirement.
- Verify relationship
- A «verify» dependency goes from a test case or verification element to a requirement, asserting that the test demonstrates satisfaction of the requirement.
- deriveReqt direction
- The «deriveReqt» dependency points from the derived requirement to its source requirement. Navigation follows the arrow to find the origin.
- Verifiable requirement text
- Requirement text states a measurable condition with a unique id so that a test can demonstrate satisfaction. Adjectives without criteria cannot be verified.
- Composition vs aggregation
- A filled diamond means the whole owns the part and bounds its lifetime. An open diamond is a non-owning whole-part relationship.
- Multiplicity meaning
- Multiplicity [n..m] on an association end states how many instances of the target type may be linked to one instance of the source type.
- Proxy port vs full port
- A proxy port exposes features of its owning block through an interface. A full port is itself an interaction point with its own behavior.
- Internal block diagram
- An IBD shows the internal structure of one block: its part properties, ports, connectors, and item flows. It is a white-box structural view.
- Value type and units
- A value type defines a type with a unit and dimension for value properties, enabling dimensional consistency checking instead of bare numbers.
- Decision vs merge node
- A decision node has one input and multiple guarded outputs; a merge node has multiple inputs and one output. They are distinct activity nodes.
- Fork and join
- A fork produces concurrent tokens on several outgoing flows. A join synchronizes them and proceeds only when all incoming tokens are present.
- Transition firing rule
- A transition fires when its trigger event occurs and its guard evaluates true. If the guard is false, the transition does not fire.
- Include vs extend
- «include» inserts mandatory shared behavior into a use case. «extend» adds optional behavior at a named extension point under a condition.
- State machine entry and do
- A state may have entry, exit, and do activities. Entry runs on entering, exit on leaving, and do while the state is active.
- Constraint block
- A constraint block encapsulates an equation and its parameters. It is reusable and can be applied many times as constraint properties with different bindings.
- Binding connector
- A binding connector equates a value property with a constraint parameter. It is a value equality, not an association or an item flow.
- Dimensional consistency check
- Binding values of different dimensions is an error. Units on value types let a parametric model detect such mismatches during evaluation.
- Parametric diagram scope
- A parametric diagram shows constraint properties, bound value properties, and binding connectors. It evaluates resulting values, not behavior over time.
- Allocate direction
- The «allocate» relationship points from the allocated source element to the allocated-to target, such as behavior allocated to the block that performs it.
- Allocate vs satisfy
- Allocation assigns responsibility across model domains. Satisfaction claims that a design element meets a requirement. The two relationships answer different questions.
- Stereotype and profile
- A stereotype extends a metaclass and adds tagged values. A profile is a package of stereotypes that must be applied before use.