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
EXAMPLE, INFO To manage the complexity, a hierarchical sequence diagram is used which refers to other interactions that further elaborate the system behavior (“ref StartVehicleBlackBox”). OMG Systems Modeling Language (SysML) 1.6 interactionOperator ref SysML Sequence Diagram
INFO To signify that only water flows between the pump and the tank, we can specify an ItemFlow of type Water on the connector. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow, FlowProperty, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind
INFO Today this process can occur in reverse, with the digital model developed first followed by the physical asset. ANZLIC 2019 - Principles for Spatially Enabled Digital Twins of the Built and Natural Environment in Australia digital twin
INFO Tokens are placed on control OutputPins according to the same semantics as tokens placed on ControlFlows coming out of an Actions. Unified Modeling Language 2.5.1 OutputPin, control Pin, Pin::isControl, ObjectNode::isControlType, control token, Action
INFO Tokens arriving at a control InputPin have the same semantics as control tokens arriving at the Action, except that control tokens can be buffered in control Pins. Unified Modeling Language 2.5.1 InputPin, control Pin, Pin::isControl, ObjectNode::isControlType, control token, Action
INFO Tokens arriving at a full object node with the Overwrite stereotype applied take up their positions in the ordering as normal, if any. The arriving tokens do not take the positions of the removed tokens. OMG Systems Modeling Language (SysML) 1.6 ObjectNode, MultiplicityElement::/upper, InputPin, Action::/input, token Overwrite, «overwrite»
INFO Tokens consumed by an Action are immediately removed from its InputPins when the action begins an execution (except in some cases for StructuredActivityNodes, where tokens may remain on InputPins during the Action execution ...) Unified Modeling Language 2.5.1 Activity, Activity Diagram, Action, Pin, InputPin, Action::/input, MultiplicityElement::/lower, execution, StructuredActivityNode, token, control token, object token
INFO Tokens offered to a ForkNode are offered to all outgoing ActivityEdges of the node. If at least one of these offers is accepted, the offered tokens are removed from their original source and the acceptor receives a copy of the tokens. Unified Modeling Language 2.5.1 Activity, Activity Diagram, ControlNode, ForkNode, ActivityNode::outgoing, ActivityEdge
INFO Top: The formation of a real image using a convex lens. Bottom: The formation of a real image using a concave mirror. In both diagrams, f is the focal point, O is the object, and I is the image. Wikipedia real image, optics, convex lens, lens, focal point
INFO Top: The formation of a virtual image using a diverging lens. Bottom: The formation of a virtual image using a convex mirror. In both diagrams, f is the focal point, O is the object and I is the image, shown in grey ... Wikipedia optics, focal point, virtual image, convex mirror
INFO Trace::getTracedFrom (in ref : NamedElement) : AbstractRequirement [0..*] The query getTracedFrom() gives all the requirements that are clients ("from" end of the concrete syntax) of a «Trace» relationship whose supplier is the element in parameter ... OMG Systems Modeling Language (SysML) 1.6 «trace», NamedElement Trace, Trace::getTracedFrom(in ref), AbstractRequirement
INFO Trade studies are commonly used in the design of aerospace and automotive vehicles and the software selection process ... to find the configuration that best meets conflicting performance requirements. Wikipedia trade study, trade-off study
INFO Traditionally, industry has created digital twins by retrospectively mapping, scanning, surveying, digitising or developing a digital copy of a real world object. ANZLIC 2019 - Principles for Spatially Enabled Digital Twins of the Built and Natural Environment in Australia digital twin
INFO Transition::/redefinitionContext : Classifier [1..1] ... References the Classifier in which context this element may be redefined. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::/redefinitionContext
INFO Transition::container : Region [1..1] ... Designates the Region that owns this Transition. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::container, Region
INFO Transition::effect : Behavior [0..1] ... Specifies an optional behavior to be performed when the Transition fires. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::effect, Behavior
INFO Transition::guard : Constraint [0..1] ... A guard is a Constraint that provides a fine-grained control over the firing of the Transition. The guard is evaluated when an Event occurrence is dispatched by the StateMachine. ... Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::guard, Constraint, Event, Event occurrence
INFO Transition::guard : Constraint [0..1] ... If the guard is true at that time, the Transition may be enabled, otherwise, it is disabled. Guards should be pure expressions without side effects. Guard expressions with side effects are ill formed. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::guard, Constraint, Event, Event occurrence
INFO Transition::kind : TransitionKind [1..1] = external Indicates the precise type of the Transition. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Vertex, compound transition, Transition::kind, kind : TransitionKind [1..1] = external
INFO Transition::redefinedTransition : Transition [0..1] ... The Transition that is redefined by this Transition. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::redefinedTransition
INFO Transition::source : Vertex [1..1] ... Designates the originating Vertex (State or Pseudostate) of the Transition. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::source, Vertex
INFO Transition::target : Vertex [1..1] ... Designates the target Vertex that is reached when the Transition is taken. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Vertex, Transition::target
INFO Transition::trigger : Trigger [0..*] ... Specifies the Triggers that may fire the transition Unified Modeling Language 2.5.1 State, StateMachine, Transition, Transition::trigger, Trigger
INFO TransitionKind is an Enumeration type used to differentiate the various kinds of Transitions. Unified Modeling Language 2.5.1 Transition, TransitionKind, Transition::kind, Enumeration, TransitionKind::internal, TransitionKind::local, TransitionKind::external
INFO Transitions are executed as part of a more complex compound transition that takes a StateMachine execution from one stable state configuration to another. Unified Modeling Language 2.5.1 State, StateMachine, Transition, compound transition
NOTATION Transitions of the kind internal are not shown explicitly in diagrams. Unified Modeling Language 2.5.1 State, StateMachine, Transition, Vertex, TransitionKind, Transition::kind, TransitionKind::internal, Internal Transition compartment
CONSTRAINT Transitions terminating on a join Pseudostate cannot have a guard or a trigger. Unified Modeling Language 2.5.1 Pseudostate, PseudostateKind::join, Transition, Transition::guard, Transition::trigger
CONSTRAINT Transitions terminating on an exit point within any Region of the composite State or a StateMachine referenced by a submachine State implies exiting of this composite State or submachine State (with execution of its associated exit Behavior). Unified Modeling Language 2.5.1 State, Pseudostate, PseudostateKind::exitPoint, StateMachine, composite State, Region, State::exit, Behavior
INFO Trigger::event : Event [1..1] The Event that detected by the Trigger. Unified Modeling Language 2.5.1 Trigger, Trigger::event
INFO Trigger::port : Port [0..*] A optional Port of through which the given effect is detected. Unified Modeling Language 2.5.1 Trigger::port, Trigger, Port
CONSTRAINT trigger_with_ports: If a Trigger specifies one or more ports, the event of the Trigger must be a MessageEvent. Unified Modeling Language 2.5.1 Event, Trigger, Trigger::event, Port, Trigger::port, MessageEvent
INFO Turning the key on has a duration constraint specifying that this action lasts no more than 0.1 seconds. OMG Systems Modeling Language (SysML) 1.6 DurationConstraint SysML specification figure
INFO Turning the key on starts two behaviors, Driving and Braking. These behaviors execute until the key is turned off, using streaming parameters to communicate with other behaviors. OMG Systems Modeling Language (SysML) 1.6 Behavior, Parameter::isStreaming SysML specification figure
INFO Two main classes of leptons exist, charged leptons (also known as the electron-like leptons), and neutral leptons (better known as neutrinos). Wikipedia
INFO Two quarks can have their spins aligned, in which case the two spin vectors add to make a vector of length S = 1 and three spin projections (Sz = +1, Sz = 0, and Sz = −1). Wikipedia
INFO Two such InstanceSpecifications represent the same "kind-of-quantity" if and only if their definitionURIs have values and their values are equal. OMG Systems Modeling Language (SysML) 1.6 InstanceSpecification QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO Two such InstanceSpecifications represent the same "measurement unit" if and only if their definitionURIs have values and their values are equal. OMG Systems Modeling Language (SysML) 1.6 InstanceSpecification QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO Two types of history Pseudostates are provided. Unified Modeling Language 2.5.1 State, StateMachine, Vertex, Pseudostate, history, PseudostateKind::deepHistory, PseudostateKind::shallowHistory
CONSTRAINT, INFO Two UseCases specifying the same subject cannot be associated as each of them individually describes a complete usage of the subject. Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, Association
CONSTRAINT two_input_parameters If the DecisionNode has a decisionInputFlow and a second incoming ObjectFlow, then any decisionInput has two in Parameters ... Unified Modeling Language 2.5.1 DecisionNode, ObjectFlow, ObjectNode, ActivityNode::incoming, ActivityEdge, DecisionNode::decisionInputFlow, TypedElement, object token, token, TypedElement::type, Type
INFO Typical examples of across variables, that we will be discussing shortly, are temperature, voltage and pressure. Differences in these quantities typically lead to dynamic behavior in the system. Modelica By Example Modelica, acausal connection
INFO Ultraviolet (UV) is a form of electromagnetic radiation with wavelength from 10 nm (with a corresponding frequency of approximately 30 PHz) to 400 nm (750 THz), shorter than that of visible light but longer than X-rays. Wikipedia UV radiation, electromagnetic radiation, ultraviolet
INFO UML 2.5.1: «Trace»: As model changes can occur in both directions, the directionality of the dependency can often be ignored. The mapping specifies the relationship between the two, but it is rarely computable and is usually informal. Unified Modeling Language 2.5.1 Trace, «trace»
INFO UML 2.5.1: «Trace»: Specifies a trace relationship between model elements or sets of model elements that represent the same concept in different models. Traces are mainly used for tracking requirements and changes across models. Unified Modeling Language 2.5.1 Trace, «trace»
INFO Uncharged mesons may decay to photons. Wikipedia
INFO Under ideal laboratory conditions, people can see infrared up to at least 1050 nm; children and young adults may perceive ultraviolet wavelengths down to about 310–313 nm. Wikipedia visible light, infrared, ultraviolet
INFO unit : InstanceSpecification [0..1] A unit, represented by an InstanceSpecification classified by a kind of SysML Unit, in terms of which the magnitudes of other quantities that have the same quantity kind can be stated. OMG Systems Modeling Language (SysML) 1.6 ValueType, ValueType::unit, QuantityKind
INFO Unit is defined as a non-abstract SysML Block defined in the SysML UnitAndQuantityKind model library. OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO Unit, or a specialization of it, classifies an InstanceSpecification to define a particular "measurement unit" in the sense of a "real scalar quantity, defined and adopted by convention, with which any other quantity of the same kind can be compared ... OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO Unlike a regular CentralBufferNode, a DataStoreNode contains objects uniquely. Unified Modeling Language 2.5.1 Activity, CentralBufferNode, token, object token, DataStoreNode, token offer
SEMANTIC Unlike ControlFlows, ObjectFlows also provide additional support for multicast/receive, token selection from ObjectNodes and transformation of tokens Unified Modeling Language 2.5.1 Activity, ActivityEdge, ObjectFlow, object token, token, ObjectFlow::selection, ObjectFlow::transformation, ObjectNode, multicast
INFO Unlike leptons, quarks possess color charge, which causes them to engage in the strong interaction. Wikipedia
INFO Unlike quarks, however, leptons are not subject to the strong interaction, but they are subject to the other three fundamental interactions: gravitation, the weak interaction, and to electromagnetism ... Wikipedia
INFO Unstereotyped ports do not commit to whether they are proxy or full, and do not prevent or dictate future application of the stereotypes, except for ports that violate constraints of the stereotypes. OMG Systems Modeling Language (SysML) 1.6 Port FullPort, "standard" Port, ProxyPort
INFO Unstereotyped ports have the basic functionality of stereotyped ones, including flow properties and nested ports, so they can be used as long as the modeler is not concerned with the distinction between proxy and full, and the constraints they impose. OMG Systems Modeling Language (SysML) 1.6 Port FullPort, "standard" Port, ProxyPort
INFO Up and down quarks have the lowest masses of all quarks. Wikipedia
INFO UseCase::extend : Extend [0..*]{subsets A_source_directedRelationship::directedRelationship, subsets Namespace::ownedMember} ... The Extend relationships owned by this UseCase. Unified Modeling Language 2.5.1 UseCase::extend, UseCase, Extend
INFO UseCase::extensionPoint : ExtensionPoint [0..*]{subsets Namespace::ownedMember} ... The ExtensionPoints owned by this UseCase. Unified Modeling Language 2.5.1 UseCase, UseCase::extensionPoint, ExtensionPoint
INFO UseCase::include : Include [0..*]{subsets A_source_directedRelationship::directedRelationship, subsets Namespace::ownedMember} ... The Include relationships owned by this UseCase. Unified Modeling Language 2.5.1 UseCase, UseCase::include, Include
INFO UseCase::subject : Classifier [0..*] ... The subjects to which this UseCase applies. Each subject or its parts realize all the UseCases that apply to it. Unified Modeling Language 2.5.1 UseCase, Classifier, UseCase::subject, Classifier::useCase
INFO UseCases can be used both for specification of the (external) requirements on a subject and for the specification of the functionality offered by a subject. Unified Modeling Language 2.5.1 UseCase, UseCase::subject functional requirement, external requirement
INFO UseCases define the offered Behaviors of the subject without reference to its internal structure. These Behaviors, involving interactions between the Actors and the subject, may result in changes to the state of the subject and communications with its... Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Classifier, Behavior, Actor, BehavioredClassifier black box
INFO UseCases may have associated Actors, which describe how an instance of the Classifier realizing the UseCase and a user playing one of the roles of the Actor interact. Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, Actor, Association
INFO UseCases need not be owned by their subject. Unified Modeling Language 2.5.1 UseCase, UseCase::subject
INFO Using an InstanceValue in a ValueSpecificationAction is similar to creating an instance using a CreateObjectAction, except that values may be given for the StructuralFeatures of the instance using slots on the InstanceSpecification of the InstanceValue. Unified Modeling Language 2.5.1 Action, ValueSpecificationAction, CreateObjectAction, InstanceValue, InstanceSpecification, Slot, StructuralFeature
INFO Using existing blocks with ports only requires knowing the port types, because they define the features available for linking or communication with those ports via connectors. OMG Systems Modeling Language (SysML) 1.6 Port FullPort, "standard" Port, ProxyPort
INFO Validation can be expressed by the query "Are you building the right thing?" and verification by "Are you building it right?" Wikipedia validation, verification, V&V, V-model, ISO/IEC/IEEE 15288, ISO/IEC/IEEE 15288-2015, ISO/IEC/IEEE 12207:2017, ISO/IEC/IEEE 12207
INFO Value types may be used to type properties, operation parameters, or potentially other elements within SysML. OMG Systems Modeling Language (SysML) 1.6 DataType, Type, Property, Parameter ValueType
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
INFO ValuePins and ActionInputPins are InputPins, but are not used in the determination of whether an Action is enabled for execution. If an Action has no other way to start execution, simply having ValuePins or ActionInputPins for its inputs will not enable.. Unified Modeling Language 2.5.1 Activity, Activity Diagram, Action, Pin, InputPin, ValuePin, ActionInputPin, execution
INFO Values are specified in an initialValues compartment by lines in the form <property-name> = <value-specification> or <property-name> : <type> = <value-specification>, each line of which specifies the initial value for one property owned either by ... OMG Systems Modeling Language (SysML) 1.6 compartment initial values, initialValues compartment, context-specific values
INFO Vapor refers to a gas phase at a temperature where the same substance can also exist in the liquid or solid state, below the critical temperature of the substance. Wikipedia vapour, Psychrometrics, gas, critical temperature, pressure
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
NOTATION Various notations for properties are available to distinguish these specialized kinds of properties on an internal block diagram. OMG Systems Modeling Language (SysML) 1.6 Property Block, block property, value property, SysML Internal Block Diagram systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
EXAMPLE, INFO Various other model elements may be necessary to help develop a derived requirement, and these model element may be related by a «refinedBy» relationship. OMG Systems Modeling Language (SysML) 1.6 Refine HSUV sample problem, Requirement, DeriveReqt, Refine requirements engineering
INFO Various sources define visible light as narrowly as 420–680 nm to as broadly as 380–800 nm. Wikipedia visible light
INFO View::/stakeholder : Stakeholder [0..*] The list of stakeholders is derived from the viewpoint the view conforms to. (derived) OMG Systems Modeling Language (SysML) 1.6 View, View::/stakeholder, Stakeholder
INFO View::/viewpoint : Viewpoint [1] The viewpoint for this View is derived from the conform relationship. (derived) OMG Systems Modeling Language (SysML) 1.6 View, View::/viewpoint, Conform, Viewpoint
INFO Viewpoint::/concern : String [0..*] The interest of the stakeholders displayed as the body of the comments from concernList. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment::body Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::/concern, Stakeholder::concernList, Viewpoint::concernList
INFO Viewpoint::/method : Behavior [0..*] The behavior is derived from the method of the operation with the Create stereotype. (derived) OMG Systems Modeling Language (SysML) 1.6 Behavior, «Create», constructor, Operation, BehavioralFeature::method Viewpoint, Viewpoint::/method URI, URL
CONSTRAINT Viewpoint::1_method_derived_from_create_operations The derived values of the method attribute shall be the names of the methods of the operations stereotyped by the UML Create stereotype on the classifier stereotyped by Viewpoint. OMG Systems Modeling Language (SysML) 1.6 «Create», constructor, Operation, BehavioralFeature::method Viewpoint, Viewpoint::/method
CONSTRAINT Viewpoint::2_create_view_operation The property ownedOperation shall include at least one operation named "View" with the UML Create stereotype applied. OMG Systems Modeling Language (SysML) 1.6 «Create», constructor, Operation, Class::ownedOperation Viewpoint, View
INFO Viewpoint::concernList : Comment [0..*] The interests of the stakeholders addressed by this viewpoint. OMG Systems Modeling Language (SysML) 1.6 Comment::body Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::/concern, Stakeholder::concernList, Viewpoint::concernList
INFO Viewpoint::language : String [0..*] The languages used to express the models that represent content which is represented by the view. The language specification such as its metamodel, profile, or other language specification is referred to by its URI. OMG Systems Modeling Language (SysML) 1.6 Viewpoint, Viewpoint::language URI, URL
INFO Viewpoint::presentation : String [0..*] The specifications prescribed for formatting and styling the view. OMG Systems Modeling Language (SysML) 1.6 String Viewpoint, Viewpoint::presentation, View
INFO Viewpoint::purpose : String [1] The purpose addresses the stakeholder concerns. OMG Systems Modeling Language (SysML) 1.6 String Viewpoint, Viewpoint::purpose, Stakeholder, Viewpoint::/concern, Stakeholder::/concern
INFO Viewpoint::stakeholder : Stakeholder [0..*] Set of stakeholders whose concerns are to be addressed by the viewpoint. OMG Systems Modeling Language (SysML) 1.6 Viewpoint, Viewpoint::stakeholder, Stakeholder, Stakeholder::/concern, Viewpoint::/concern
CONSTRAINT When a Copy dependency exists between two requirements, the requirement text of the client requirement is a read-only copy of the requirement text of the requirement at the supplier end of the dependency. OMG Systems Modeling Language (SysML) 1.6 Dependency, Dependency::client, Dependency::supplier Requirement, Copy, AbstractRequirement::text, AbstractRequirement::id
RULE When a DataStoreNode accepts an object token, if that token contains an object with the same identity as an object contained in a token already held by the node, then the duplicate object token shall not be placed on the DataStoreNode. Unified Modeling Language 2.5.1 Activity, token, object token, DataStoreNode, token offer, identity
CONSTRAINT, INFO When a proxy port is connected to a single internal part [or port or internal part], the connector shall be a binding connector, or have the same semantics as a binding connector ... OMG Systems Modeling Language (SysML) 1.6 Port, part ProxyPort, part property, MD:PartProperty, BindingConnector
CONSTRAINT, INFO When a proxy port is connected to multiple internal parts, the connectors have the same semantics as a single binding connector to an aggregate of those parts, supporting all their features, and treating flows and invocations from outside the aggregate... OMG Systems Modeling Language (SysML) 1.6 Port, part, Feature ProxyPort, part property, MD:PartProperty, BindingConnector
SEMANTIC When a Region of the submachine StateMachine reaches the corresponding exit point, the submachine state is exited via this exit point. Unified Modeling Language 2.5.1 State, StateMachine, submachine, ConnectionPointReference, exit point, PseudostateKind::exitPoint, Region
INFO When a requirement has nested requirements, all the nested requirements apply as part of the container requirement. Deleting the container requirement deleted [deletes] the nested requirements, a functionality inherited from UML. OMG Systems Modeling Language (SysML) 1.6 Requirement, composite (compound) requirement, subrequirement requirements engineering
INFO When an Action in an Activity completes execution, object tokens for output data placed on its OutputPins may be offered on any outgoing ObjectFlows from those Pins ... In addition, control tokens shall be offered on any outgoing ControlFlows ... Unified Modeling Language 2.5.1 Action, Activity, OutputPin, ObjectFlow, ObjectNode, ControlFlow, ExecutableNode, execution, completion, run-to-completion
INFO When an ExecutableNode completes an execution, the control token representing that execution is removed from the ExecutableNode and control tokens are offered on all outgoing ControlFlows of the ExecutableNode. That is, there is an implicit fork ... Unified Modeling Language 2.5.1 Behavior, Activity, Activity Diagram, ExecutableNode, implicit join, ControlFlow, ActivityNode::outgoing, token, control token, implicit fork
RULE When an offer for an object token held by a DataStoreNode is accepted by a downstream object node, the offered token is removed from the DataStoreNode, per the usual CentralBufferNode semantics. However, a copy is made of the removed object token ... Unified Modeling Language 2.5.1 Activity, CentralBufferNode, token, object token, DataStoreNode, token offer
INFO When calibrated to ITS-90, where one must interpolate between the defining points of gallium and indium, the boiling point of VSMOW water is about 10 mK less, about 99.974 °C. Wikipedia thermodynamics, temperature, celsius, kelvin, Kelvins, water, boiling point
INFO When completed, an Action execution provides any output data on the OutputPins of the Action, and it terminates. Unified Modeling Language 2.5.1 Activity, Activity Diagram, Action, execution, completion, termination, Action::/output, OutputPin
INFO When composition is used with activity blocks, the termination of execution of an activity on the whole end will terminate executions of activities on the part end of the links. OMG Systems Modeling Language (SysML) 1.6 Activity, Association, AggregationKind::composite Block
INFO When exiting a State, regardless of whether it is simple or composite, the final step involved in the exit, after all other Behaviors associated with the exit are completed, is the execution of the exit Behavior of that State. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit