OCSMP Model User flashcards
OCSMP Model User · 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.
- Activity partition (swimlane)
- An activity partition groups actions inside an activity and maps them to the block or organizational unit responsible for performing them; it is drawn as a swimlane and does not change token semantics.
- Control flow versus object flow
- A control flow carries control tokens that sequence action execution, while an object flow carries object tokens standing for data or physical items passed from one action to another.
- Decision and merge nodes
- A decision node takes one incoming control flow and selects one outgoing flow using mutually exclusive guards; a merge node reunites alternative incoming flows into a single outgoing flow without synchronization.
- Fork and join nodes
- A fork node splits one incoming control flow into several concurrent outgoing flows, and a join node synchronizes concurrent incoming flows, emitting one token only when all inputs have arrived.
- Composite state
- A composite state contains nested substates and possibly several orthogonal regions running concurrently; its entry, exit and do behaviors execute on entry, on exit and while the state is active.
- Transition trigger kinds
- A state machine transition trigger is a signal event (receipt of a named signal), a time event (after a duration) or a change event (when a Boolean condition becomes true).
- Include versus extend
- Include makes the behavior of one use case a mandatory part of a base use case; extend adds optional behavior to a base use case at a named extension point under a stated condition.
- Combined fragment operator
- A combined fragment groups messages in a sequence diagram under an operator such as alt, opt, loop or par, expressing alternative, optional, iterative or parallel interaction behavior.
- Block
- A block is SysML's basic structural element: a UML class with the «block» stereotype used to model systems, components, items or other structural units with properties and operations.
- Part versus reference property
- A part property has composition, meaning strong ownership in which the part is destroyed with its whole; a reference property uses shared aggregation and points to an element owned elsewhere.
- Proxy port
- A proxy port is a port whose type is a block or interface block; the port exposes the features of that type and delegates incoming requests to internal parts of the enclosing block.
- Conjugated interface block
- Applying «conjugate» to an interface block reverses the direction of its features, so a port typed by the conjugate requires the items the original interface block provided.
- Flow property
- A flow property is a property of a block or port typed by the classifier of an item flow, stating what can flow in or out; it replaces the deprecated flow port notation.
- Item flow
- An item flow is a connector feature drawn as a line with an open arrowhead between ports or parts, labeled with a conveyed classifier, specifying which items travel across that connector.
- Assembly versus delegation connector
- In an internal block diagram, an assembly connector links ports of parts at the same level to pass items between them, while a delegation connector links an outer port of the enclosing block to a nested part's port.
- Value type
- A value type is a block stereotyped «valueType» that models values without identity, typically carrying a unit and dimension, and is used to type value properties and flow properties.
- Requirement element
- A requirement is a UML class stereotyped «requirement» with an added id property identifying it and a text property holding the requirement statement, both shown in its compartments.
- Satisfy relationship
- A «satisfy» dependency from a design element such as a block or part to a requirement asserts that the design element fulfills that requirement.
- Verify relationship
- A «verify» dependency from a test case to a requirement asserts that the test case demonstrates whether the requirement is met by the system under verification.
- Derive requisite
- A «deriveRequisite» dependency points from a derived requirement to the requirement it is derived from, typically tracing a system requirement back to a stakeholder need.
- Requirement containment
- Nesting one requirement inside another through composition expresses decomposition, where the containing requirement is composite and its text summarizes the nested subrequirements.
- Test case
- A test case is a behavior stereotyped «testCase» that specifies how verification is performed and can be connected to requirements by «verify» dependencies.
- Refine relationship
- A «refine» dependency links a model element to a requirement that it elaborates, adding detail without asserting that the requirement is satisfied or verified.
- Copy dependency
- A «copy» dependency points from a copied requirement to its source requirement, recording that the requirement text is reused unchanged from the original.
- Allocate dependency
- An allocation is a cross-cutting «allocate» dependency that maps one model element onto another, for example allocating an activity or action to the block that performs it.
- Allocation compartment
- A block's allocation compartment lists the model elements mapped to or from that block, shown as allocatedFrom entries and allocatedTo entries inside the block rectangle.
- View and viewpoint
- A viewpoint states the stakeholders, concerns and purpose for a perspective on the model; a view is a subset or query of model elements that conforms to a viewpoint via «conform».
- Rationale comment
- A rationale is a UML comment stereotyped «rationale» that records the reasoning behind a modeling decision and is attached to the model element it explains.
- Problem comment
- A problem is a UML comment stereotyped «problem» that documents an issue, risk or open question in the model and is attached to the affected model elements.
- Package import
- A package import is an «import» dependency that makes the public or private members of one package visible by name in another package, as either a public or private import.
- Unit and dimension
- In SysML, «unit» and «dimension» are stereotypes applied to instance specifications, and value types reference them so quantities are expressed with consistent physical units.
- Diagram frame heading
- A SysML diagram frame carries a heading with the diagram kind abbreviation and the diagram name, such as bdd, ibd, act, stm, sd, req, par or alloc.