Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

Snippets (text quotes and extracts from authoritative sources)

A Snippet is a short quote or extract (typically a phrase, a sentence, or at most a few sentences) from an authoritative source document such as a specification, technical manual, or design manual. Throughout this site, content is often related to supporting Snippets and each Snippet page links back to the content pages that reference it! The Snippet and Note concepts are very closely related and they support each other.

The Snippet concept is also at the heart of the Parsing Analysis recipe for UML® and SysML®

Kind Snippet quote/extract Source UML keywords SysML keywords Keywords
SEMANTIC NOTE. Each submachine State represents a distinct instantiation of a submachine, even when two or more submachine States reference the same submachine. Unified Modeling Language 2.5.1 State, StateMachine, submachine
SEMANTIC The entry, exit, and effect Behaviors and internal Transitions are defined as contained in the submachine State. Unified Modeling Language 2.5.1 State, StateMachine, submachine, State::entry, State::exit, Transition, Transition::effect
SEMANTIC The Regions of the submachine StateMachine are the Regions of the composite State. Unified Modeling Language 2.5.1 State, StateMachine, submachine, Region, composite State
SEMANTIC A submachine State implies a macro-like insertion of the specification of the corresponding submachine StateMachine. It is, therefore, semantically equivalent to a composite State. Unified Modeling Language 2.5.1 State, StateMachine, submachine, composite State
SEMANTIC Each ConnectionPointReference is matched by a corresponding entry or exit point in the referenced submachine StateMachine. This provides the necessary binding mechanism between the submachine invocation and its specification. Unified Modeling Language 2.5.1 State, StateMachine, submachine, ConnectionPointReference, Transition, State::exit, State::entry
SEMANTIC A ConnectionPointReference represents a point on the submachine State at which a Transition either terminates or originates. That is, they serve as targets for incoming Transitions to submachine States, as well as sources for outgoing Transitions ... Unified Modeling Language 2.5.1 State, StateMachine, submachine, ConnectionPointReference, Transition, DirectedRelationship::/target, DirectedRelationship::/source
SEMANTIC The concept of ConnectionPointReference is provided to support binding between the submachine State and the referenced StateMachine. Unified Modeling Language 2.5.1 State, StateMachine, submachine, ConnectionPointReference
SEMANTIC Consequently, they require a more complex binding. This is achieved through the concept of submachine State (i.e., States with isSubmachineState = true), which represent references to corresponding submachine StateMachines. Unified Modeling Language 2.5.1 State, StateMachine, submachine, State::/isSubmachineState
SEMANTIC However, whereas encapsulated composite States and their internals are contained within the StateMachine in which they are defined, submachines are, like programming language macros, distinct Behavior specification ... Unified Modeling Language 2.5.1 State, StateMachine, submachine, Behavior, composite State
SEMANTIC Submachines are a means by which a single StateMachine specification can be reused multiple times. They are similar to encapsulated composite States in that they need to bind incoming and outgoing Transitions to their internal Vertices. Unified Modeling Language 2.5.1 State, StateMachine, submachine, Transition, Vertex
NOTATION Receptions are shown in the receptions compartment using the same notation as for Operations with the keyword «signal». Unified Modeling Language 2.5.1 Reception
NOTATION A required Interface may be shown by the socket notation attached to the Port. Unified Modeling Language 2.5.1 Interface, Usage
NOTATION A provided Interface may be shown using the lollipop notation ... attached to the Port. Unified Modeling Language 2.5.1 Interface, InterfaceRealization
SEMANTIC DataTypes model Types whose instances are distinguished only by their value Unified Modeling Language 2.5.1 Type, DataType
SEMANTIC Features represent structural and behavioral characteristics of Classifiers. Unified Modeling Language 2.5.1 Feature, Classifier, StructuralFeature, BehavioralFeature
CAVEAT ValuePin – Value pins are excluded from fUML because they are redundant with using value specifications to specify values. Semantics of a Foundational Subset for Executable UML Models 1.4 ValuePin, ValueSpecification fUML, Foundational UML, execution, simulation
CONSTRAINT If the triggers of an AcceptEventAction are all for ChangeEvents and/or CallEvents, then the AcceptEventAction has no result OutputPins (unless the AcceptEventAction is an AcceptCallAction ...) Unified Modeling Language 2.5.1 AcceptEventAction, ChangeEvent, CallEvent, Trigger, OutputPin, AcceptCallAction
SEMANTIC Such an AcceptEventAction is terminated when its immediately containing Activity (or StructuredActivityNode) is terminated. Unified Modeling Language 2.5.1 AcceptEventAction, Activity, StructuredActivityNode
SEMANTIC That is, it does not terminate after accepting an Event occurrence and outputting any values (as described above), but continues to wait for another Event occurrence. Unified Modeling Language 2.5.1 AcceptEventAction, Activity
SEMANTIC However, in addition, an AcceptEventAction with no incoming edges remains enabled after it accepts an Event occurrence. Unified Modeling Language 2.5.1 AcceptEventAction, Activity, Event
SEMANTIC If the AcceptEventAction has no incoming edges, by the usual rules, it is enabled when its immediately containing Activity (or StructuredActivityNode) begins execution. Unified Modeling Language 2.5.1 AcceptEventAction, Activity
RULE If an AcceptEventAction is used in an Activity, there are special rules for when it is enabled .. Unified Modeling Language 2.5.1 AcceptEventAction, Activity
CONSTRAINT 7.10.2.2 ActivityEdge [1] fuml_activity_edge_allowed_guards A guard is only allowed if the source of the edge is a DecisionNode. Semantics of a Foundational Subset for Executable UML Models 1.4 ActivityEdge, ActivityEdge::guard
CAVEAT Variables are excluded from fUML because the passing of data between actions can be achieved using object flows. Semantics of a Foundational Subset for Executable UML Models 1.4 Variable
CAVEAT The sole mechanism for asynchronous invocation in fUML is via send signal action. This can be used to achieve the effect of broadcasting and sending objects. Semantics of a Foundational Subset for Executable UML Models 1.4 BroadcastSignalAction, SendObjectAction, SendSignalAction fUML
CONSTRAINT NOTE. Operation referenced in the CallEvent of an AcceptCallAction should not have an associated method Behavior. Otherwise, a call to the Operation will have the immediate effect of executing the method and will not be placed into the event pool ... Unified Modeling Language 2.5.1 AcceptCallAction, Operation, CallEvent, Behavior