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 Sort descending Source UML keywords SysML keywords Keywords
INFO Component parametric diagrams show properties typed by constraint blocks (constraint properties), as well as component and port simulation variables and constants. SysPhS-1.1 Constraint constraint parameter, ConstraintBlock, BindingConnector, SysML Parametric Diagram SysPhS
INFO Component PhSConstants (SimulinkParameters and ModelicaParameters) for vectors and matrices have MultidimensionalElement applied, with dimension * and *,*, respectively ... SysPhS-1.1 Port "standard" Port
INFO Compound requirements can be created by using the nesting capability of the class definition mechanism. OMG Systems Modeling Language (SysML) 1.6 Class Requirement, «system», AbstractRequirement, composite (compound) requirement requirements engineering
INFO Computer has ports u and y of type RealInSignalElement [ERROR:TYPO] and RealOutSignalElement [ERROR:TYPO] from the signal flow library (see Subclause 11.2.1), respectively. SysPhS-1.1 Port "standard" Port SysPhS, SysML, Systems Modeling Language
INFO Conjugation is specified by a constraint giving the features of ~InterfaceBlocks according to those of their original InterfaceBlocks ... It is expected that tools conforming to this specification automatically create features of ~InterfaceBlocks. OMG Systems Modeling Language (SysML) 1.6 InterfaceBlock, ~InterfaceBlock, conjugation, ~InterfaceBlock::original, DirectedFeature, FlowProperty, FlowProperty::direction, FlowDirectionKind, DirectedFeature::featureDirection, FeatureDirectionKind, FlowDirectionKind::in, FlowDirectionKind::out, FeatureDirectionKind::provided, FeatureDirectionKind::providedrequired
SEMANTIC Connection point references are sources/targets of Transitions implying exits out of/entries into the submachine StateMachine referenced by a submachine State. Unified Modeling Language 2.5.1 State, StateMachine, submachine, ConnectionPointReference, Transition, DirectedRelationship::/source, DirectedRelationship::/target
SEMANTIC Connection point references of a submachine State can be used as sources/targets of Transitions. They represent entries into or exits out of the submachine StateMachine referenced by the submachine State. Unified Modeling Language 2.5.1 State, StateMachine, submachine, ConnectionPointReference, Transition, DirectedRelationship::/source, DirectedRelationship::/target
INFO Connectors can be typed by association classes that are stereotyped by Block (association blocks, see ParticipantProperty ... OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass ConnectorProperty, AssociationBlock, ParticipantProperty
INFO Connectors may be drawn that cross the boundaries of nested properties to connect to properties within them. The connector is owned by the most immediate block that owns both ends of the connector. OMG Systems Modeling Language (SysML) 1.6 Connector, NestedConnectorEnd
INFO Connectors typed by association blocks, including their connector properties, are replaced by the internal structure of the association blocks. Figure 3 shows the content of Figure 2 after processing. SysPhS-1.1 Connector AssociationBlock, ConnectorProperty SysPhS, SysML, Systems Modeling Language
INFO Connectors with item flows can be decomposed by association blocks that have additional item flows. The relationship between an item flow and those in the association block is determined by the modeler. OMG Systems Modeling Language (SysML) 1.6 Connector ItemFlow, AssociationBlock
INFO Consequently, a particular “state” of an executing StateMachine instance is represented by one or more hierarchies of States, starting with the topmost Regions of the StateMachine and down through the composition hierarchy to the simple, or leaf, States. Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite, State::/isSimple
SEMANTIC Consequently, choice is used to realize a dynamic conditional branch. It allows splitting of compound transitions into multiple alternative paths such that the decision on which path to take may depend on the results of Behavior executions performed ... Unified Modeling Language 2.5.1 Pseudostate, PseudostateKind::choice, StateMachine, dynamic conditional branch, Behavior, compound transition
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
INFO Constraint blocks can be used to specify a network of constraints that represent mathematical expressions such as {F=m*a} and {a=dv/dt}, which constrain the physical properties of a system. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock mathematics, equation
INFO Constraint blocks define generic forms of constraints that can be used in multiple contexts. For example, a definition for Newton’s Laws may be used to specify these constraints in many different contexts. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, MD:ConstraintParameter, constraint parameter mathematics, equation
INFO Constraint blocks provide a mechanism for integrating engineering analysis such as performance and reliability models with other SysML models. OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock
NOTATION Constraint properties and their parameters also have their own notations ... OMG Systems Modeling Language (SysML) 1.6 Property, Port constraint property, MD:ConstraintProperty
INFO Constraint Properties are a special class of property used to constrain other properties of blocks... OMG Systems Modeling Language (SysML) 1.6 Property, part, Constraint Block, block property, constraint property, ConstraintBlock systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Constraint properties are further defined in Clause 10. A port is another category of property, as further defined in Section 9. OMG Systems Modeling Language (SysML) 1.6 Property, AggregationKind, Property::aggregation, AggregationKind::composite, Port Block, MD:ConstraintProperty, constraint property
INFO Constraints can be added between the flow properties for the engine and those for the parts, to indicate the flowing parts are inside the flowing engine, or are separate, for example as spare parts. OMG Systems Modeling Language (SysML) 1.6 Connector, InformationFlow::conveyed ItemFlow, AssociationBlock
INFO Context blocks are typically the owner of the first property in the path of properties, but can be specializations of the owner to limit the scope of the relationship. OMG Systems Modeling Language (SysML) 1.6 DirectedRelationship, DirectedRelationship::/source, DirectedRelationship::/target DirectedRelationshipPropertyPath, DirectedRelationshipPropertyPath::sourceContext, DirectedRelationshipPropertyPath::sourcePropertyPath, DirectedRelationshipPropertyPath::targetContext, DirectedRelationshipPropertyPath::targetPropertyPath
INFO Continuous ... It is independent from UML streaming, see clause 11.3.2.8. A streaming parameter may or may not apply to continuous flow, and a continuous flow may or may not apply to streaming parameters. OMG Systems Modeling Language (SysML) 1.6 Parameter, ActivityEdge, Parameter::isStreaming Continuous, «continuous», Rate continuous system, flow, energy, water, material
INFO Continuous rate is a special case of rate of flow (see Rate) where the increment of time between items approaches zero. It is intended to represent continuous flows that may correspond to water flowing through a pipe, a time continuous signal, or ... OMG Systems Modeling Language (SysML) 1.6 Parameter, ActivityEdge Continuous, «continuous», Rate continuous system, flow, energy, water, material
INFO Continuous variables have values that are close to their values at nearby times in the past and future. Discrete variables have values that are the same as their values at nearby times in either the past or future, or both. SysPhS-1.1 SysPhS, SysML, Systems Modeling Language
INFO Control flow may be notated with a dashed line and stick arrowhead, as shown in Figure 11-4. OMG Systems Modeling Language (SysML) 1.6 ControlFlow SysML control flow notation, SysML Activity Diagram presentation option
INFO Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...). Unified Modeling Language 2.5.1 Pin, control Pin, Pin::isControl, ObjectNode::isControlType, control token, Action, InvocationAction
NOTATION Control Pins are shown with the textual annotation {control} placed near the Pin symbol. Unified Modeling Language 2.5.1 control Pin, Pin::isControl, {control}, notation
SEMANTIC ControlFlows are used to explicitly sequence execution of ActivityNodes, as the target ActivityNode cannot receive a control token and start execution until the source ActivityNode completes execution and produces the token. Unified Modeling Language 2.5.1 Activity, ActivityEdge, ControlFlow, ActivityNode, ActivityEdge::target, ActivityEdge::source, execution, control token
SEMANTIC ControlNodes act as “traffic switches” managing the flow of tokens across ActivityEdges. Tokens cannot “rest” at ControlNodes (with exceptions for InitialNodes and ForkNodes ...). Unified Modeling Language 2.5.1 Activity, ActivityNode, ControlNode, token, control token, object token, ActivityEdge, InitialNode, ForkNode
CONSTRAINT Copy::1_source_and_taget_are_requirements A Copy dependency may only be created between two NamedElements that have a subtype of the abstractRequirement stereotype applied OMG Systems Modeling Language (SysML) 1.6 Dependency, Dependency::client, Dependency::supplier Requirement, Copy, AbstractRequirement::text, AbstractRequirement::id
CONSTRAINT Copy::2_same_text The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement and this applies recursively to all subrequirements OMG Systems Modeling Language (SysML) 1.6 Dependency, Dependency::client, Dependency::supplier Requirement, Copy, AbstractRequirement::text, AbstractRequirement::id
INFO CreateObjectAction::classifier : Classifier [1..1] The Classifier to be instantiated. Unified Modeling Language 2.5.1 CreateObjectAction, CreateObjectAction::classifier UML, Unified Modeling Language
INFO CreateObjectAction::result : OutputPin [1..1]{subsets Action::output} The OutputPin on which the newly created object is placed. Unified Modeling Language 2.5.1 CreateObjectAction, CreateObjectAction::result UML, Unified Modeling Language
INFO Data types in SysML are called value types. SysPhS-1.1 DataType ValueType SysPhS, SysML, Systems Modeling Language
SEMANTIC DataTypes model Types whose instances are distinguished only by their value Unified Modeling Language 2.5.1 Type, DataType
SEMANTIC Decimal notation consists of an optional sign character (+/-) followed by zero or more digits followed optionally by a dot (.) followed by one or more digits. Unified Modeling Language 2.5.1 value, notation, LiteralReal, Real, decimal, digit
INFO decisionInput : Behavior [0..1] ... A Behavior that is executed to provide an input to guard ValueSpecifications on ActivityEdges outgoing from the DecisionNode. Unified Modeling Language 2.5.1 DecisionNode, DecisionNode::decisionInput, ControlNode, ActivityEdge, Behavior, ValueSpecification, ActivityEdge::guard
INFO decisionInputFlow : ObjectFlow [0..1] ... An additional ActivityEdge incoming to the DecisionNode that provides a decision input value for the guards ValueSpecifications on ActivityEdges outgoing from the DecisionNode. Unified Modeling Language 2.5.1 DecisionNode, DecisionNode::decisionInputFlow, ControlNode, ActivityEdge, ObjectFlow, ValueSpecification, ActivityEdge::guard
CONSTRAINT DecisionNode::edges The ActivityEdges incoming to and outgoing from a DecisionNode, other than the decisionInputFlow (if any), must be either all ObjectFlows or all ControlFlows. Unified Modeling Language 2.5.1 DecisionNode, ControlFlow, ObjectNode, ActivityNode::incoming, ActivityEdge, DecisionNode::decisionInputFlow
CONSTRAINT DecisionNode::incoming_outgoing_edges A DecisionNode has one or two incoming ActivityEdges and at least one outgoing ActivityEdge. Unified Modeling Language 2.5.1 DecisionNode, ActivityEdge, ActivityNode::incoming, ActivityNode::outgoing
CONSTRAINT decision_input_flow_incoming The decisionInputFlow of a DecisionNode must be an incoming ActivityEdge of the DecisionNode. Unified Modeling Language 2.5.1 DecisionNode, ControlFlow, ObjectNode, ActivityNode::incoming, ActivityEdge, DecisionNode::decisionInputFlow
INFO Deep history (deepHistory) represents the full state configuration of the most recent visit to the containing Region. Unified Modeling Language 2.5.1 State, StateMachine, Vertex, Pseudostate, history, PseudostateKind::deepHistory, Region, enclosing Region
SEMANTIC deepHistory – ... The entry Behaviors of all States in the restored state configuration are performed in the appropriate order starting with the outermost State Unified Modeling Language 2.5.1 StateMachine, State, Pseudostate, PseudostateKind::deepHistory, State::entry
SEMANTIC deepHistory – This type of Pseudostate is a kind of variable that represents the most recent active state configuration of its owning Region. ... a Transition terminating on this Pseudostate implies restoring the Region to that same state ... Unified Modeling Language 2.5.1 StateMachine, State, Pseudostate, PseudostateKind::deepHistory, Region
INFO Defined quantitatively, the heat involved in a process is the difference in internal energy between the final and initial states of a system, and subtracting the work done in the process. This is the formulation of the first law of thermodynamics. Wikipedia heat, thermodynamics, energy, energy transfer
INFO Delegation Connectors can be used to model the hierarchical decomposition of behavior, where services provided by an EncapsulatedClassifier may ultimately be realized by one that is nested multiple levels deep within it. Unified Modeling Language 2.5.1 Port, Connector, Connector::kind, ConnectorKind, ConnectorKind::delegation
EXAMPLE, INFO Derived requirements, for the purpose of this example, express the concepts of requirements in the HSUVSpecification in a manner that specifically relates them to the HSUV system. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Requirement, DeriveReqt requirements engineering
CONSTRAINT DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement. OMG Systems Modeling Language (SysML) 1.6 Dependency, Dependency::supplier DeriveReqt, Requirement
CONSTRAINT DeriveReqt::2_client_is_requirement The client shall be an element stereotyped by a subtype of AbstractRequirement. OMG Systems Modeling Language (SysML) 1.6 Dependency, Dependency::client DeriveReqt, Requirement
INFO Determine the amount of sensible heat needed to increase the temperature of air from 50°F and 50% RH to 90°F. CED Engineering course PDF: 'Air Conditioning Psychrometrics (A.Bhatia)' thermodynamics, Psychrometrics, humid air, temperature, dry bulb temperature, wet bulb temperature, relative humidity, absolute humidity, sensible heat, heat, energy, energy transfer, cooling
INFO Determine the cooling required to sensibly cool 20,000 cfm of air from a temperature of 90 F and a relative humidity of 60% to a temperature of 75 F. CED Engineering course PDF: 'Air Conditioning Psychrometrics (A.Bhatia)' thermodynamics, Psychrometrics, humid air, temperature, dry bulb temperature, wet bulb temperature, relative humidity, absolute humidity, sensible heat, heat, energy, energy transfer, cooling
INFO Determine the total, sensible and latent cooling required cooling 20,000 cfm of air from a temperature of 90 F and a relative humidity of 60% to a temperature of 55 F and 100% relative humidity. CED Engineering course PDF: 'Air Conditioning Psychrometrics (A.Bhatia)' thermodynamics, Psychrometrics, humid air, temperature, dry bulb temperature, wet bulb temperature, relative humidity, absolute humidity, sensible heat, heat, energy, energy transfer, water, moisture
INFO Diagram of the lightpath through a Gregorian telescope. Wikipedia Gregorian reflector, reflecting telescope, reflector, optical telescope
INFO Digital twins are dynamic, data driven, multi-dimensional digital replicas of a physical entity. ANZLIC 2019 - Principles for Spatially Enabled Digital Twins of the Built and Natural Environment in Australia
NOTATION Directed features can appear in compartments for the various kinds of properties and behavioral features. OMG Systems Modeling Language (SysML) 1.6 compartment, Property, BehavioralFeature DirectedFeature, DirectedFeature::featureDirection, FeatureDirectionKind, FeatureDirectionKind::provided, FeatureDirectionKind::providedrequired, FeatureDirectionKind::required
INFO Discrete and continuous flows are unified under rate of flow, as is traditionally done in mathematical models of continuous change, where the discrete increment of time approaches zero. OMG Systems Modeling Language (SysML) 1.6 «continuous», «discrete», Continuous, Discrete, Rate continuous system, flow, discrete system
INFO Discrete rate is a special case of rate of flow ... where the increment of time between items is a non-zero. Examples include the production of assemblies in a factory and signals set at periodic time intervals. OMG Systems Modeling Language (SysML) 1.6 Discrete, «discrete», Rate, Rate::rate
INFO Don't judge a book by its cover Wikipedia proverb, Webel Parsing Analysis
INFO Due to a phenomenon known as color confinement, quarks are never found in isolation; they can be found only within hadrons, which include baryons (such as protons and neutrons) and mesons, or in quark–gluon plasmas. Wikipedia
INFO Each ActivityParameterNode is associated with one Parameter of the Activity that owns the node. The type of an ActivityParameterNode shall be the same as the type of its associated Parameter. Unified Modeling Language 2.5.1 Activity, Behavior, Parameter, ActivityParameterNode, Type
INFO Each block defines a collection of features to describe a system or other element of interest. These may include both structural and behavioral features, such as properties and operations, to represent the state of the system and behavior ... OMG Systems Modeling Language (SysML) 1.6 Feature, StructuralFeature, BehavioralFeature, Property, Operation, Behavior Block, «system» systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Each classifier of conveyed items on an item flow shall be the same as, a specialization of, or a generalization of at least one flow property type on each end of the connected block usages (or their accessible nested block usages recursively, ... OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
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
INFO Each Connector may be attached to two or more ConnectableElements, each representing a set of instances that contribute to the instantiation of the containing StructuredClassifier. Unified Modeling Language 2.5.1 Connector, link, instance, StructuredClassifier, roles, Association, ConnectableElement
EXAMPLE, INFO Each instance of Operating Car is an execution of that behavior. It owns the executions of the behaviors it invokes synchronously, such as Driving. OMG Systems Modeling Language (SysML) 1.6 AggregationKind::composite, Association AdjunctProperty, SysML Block Definition Diagram
INFO Each kind of component has its own behaviors, defined as constraints ... SysPhS-1.1 Constraint ConstraintBlock SysPhS, signal processing, mixer
INFO Each link may be realized by something as simple as a pointer or by something as complex as a network connection, and may represent the possibility of instances being able to communicate because their identities are known by virtue of being passed in ... Unified Modeling Language 2.5.1 Connector, link, instance, StructuredClassifier, roles
EXAMPLE, INFO Each model element depicted may include a graphical icon to help convey its intended meaning. OMG Systems Modeling Language (SysML) 1.6 icon, Stereotype, image
INFO Each type of component has its own behaviors, defined as constraints ... SysPhS-1.1 Constraint ConstraintBlock SysPhS, hydraulics
INFO Each UseCase specifies a unit of useful functionality that the subject provides to its users (i.e., a specific way of interacting with the subject). This functionality must always be completed for the UseCase to complete. Unified Modeling Language 2.5.1 UseCase, Behavior, BehavioredClassifier, UseCase::subject
INFO electromagnetism ... is proportional to charge, and is thus zero for the electrically neutral neutrinos. Wikipedia
INFO Electrons have an electric charge of −1.602176634×10−19 coulombs, which is used as a standard unit of charge for subatomic particles, and is also called the elementary charge. Wikipedia
INFO Electrons have the least mass of all the charged leptons. Wikipedia
INFO Element groups are named using the name property. OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::name
INFO Element groups can be members of other element groups, but this does not imply that members of the first are members of the second. OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO Element groups do not own their elements and thus an element can participate in an unlimited number of groups. OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO Elementary fermions are grouped into three generations, each comprising two leptons and two quarks. Wikipedia
INFO Elementary fermions are grouped into three generations, each comprising two leptons and two quarks. The first generation includes up and down quarks, the second strange and charm quarks, and the third bottom and top quarks. Wikipedia
INFO ElementGroup::/criterion : String [0..1] Specifies the rationale for being member of the group. Adding an element to the group asserts that the criterion applies to this element. Derived from Comment::body. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::body ElementGroup, ElementGroup::/criterion, ElementGroup::/member
INFO ElementGroup::/member : Element [0..*] Set specifying the members of the group. Derived from Comment::annotatedElement. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO ElementGroup::/size : Integer [1] Number of members in the group. Derived. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::/size, ElementGroup::/member
INFO ElementGroup::name : String [1] Name of the element group OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::name
INFO ElementGroup::orderedMember : Element [0..*] Organize member according to an arbitrary order. Optional. (subsets: ElementGroup::member) OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::orderedMember
INFO ElementGroups appear in diagrams as comments, and properties of the stereotype appear in the notation for stereotype properties. OMG Systems Modeling Language (SysML) 1.6 Comment, Stereotype, stereotype Property ElementGroup
INFO Entry points represent termination points (sources) for incoming Transitions and origination points (targets) for Transitions that terminate on some internal Vertex of the composite State. Unified Modeling Language 2.5.1 State, StateMachine, Transition, PseudostateKind, PseudostateKind::entryPoint, Vertex, Transition::source, Transition::target
CONSTRAINT entryPoint – ... NOTE. ... If multiple Regions are involved, the entry point acts as a fork Pseudostate. Unified Modeling Language 2.5.1 State, Pseudostate, PseudostateKind::entryPoint, StateMachine, PseudostateKind::fork
CONSTRAINT entryPoint – ... NOTE. If the owning State has an associated entry Behavior, this Behavior is executed before any behavior associated with the outgoing Transition. Unified Modeling Language 2.5.1 State, Pseudostate, PseudostateKind::entryPoint, StateMachine, Behavior, Transition, State::entry
SEMANTIC entryPoint – An entryPoint Pseudostate represents an entry point for a StateMachine or a composite State that provides encapsulation of the insides of the State or StateMachine. Unified Modeling Language 2.5.1 State, Pseudostate, PseudostateKind::entryPoint, StateMachine, composite State
INFO Equations define mathematical relationships between the values of numeric variables. Equations in SysML, are constraints in constraint blocks that use properties of the blocks (parameters) as variables. SysPhS-1.1 Constraint constraint parameter, ConstraintBlock, Block SysPhS
INFO Equations define mathematical relationships between the values of numeric variables. Equations in SysML, are constraints in constraint blocks that use properties of the blocks (parameters) as variables. SysPhS-1.1 Constraint ConstraintBlock, constraint parameter SysPhS, signal processing
INFO Equations define mathematical relationships between the values of numeric variables. Equations in SysML, are constraints in constraint blocks that use properties of the blocks (parameters) as variables. SysPhS-1.1 Constraint constraint parameter, ConstraintBlock
INFO Equations in constraint blocks are applied to components using binding connectors in component parametric diagrams. SysPhS-1.1 Constraint ConstraintBlock, constraint parameter, BindingConnector, SysML Parametric Diagram SysPhS, signal processing
INFO Equations in constraint blocks are applied to components using binding connectors in component parametric diagrams. SysPhS-1.1 Constraint constraint parameter, ConstraintBlock, BindingConnector, SysML Parametric Diagram SysPhS
INFO Examples of additional non-normative stereotypes based on AbstractRequirement are included in E.8. OMG Systems Modeling Language (SysML) 1.6 AbstractRequirement, Requirement
INFO Except in the case of an input ActivityParameterNode ... the tokens held by an ObjectNode arrive from incoming ActivityEdges. Unified Modeling Language 2.5.1 Activity, ObjectNode, token, object token, ActivityParameterNode, ActivityEdge
INFO Except in the case of an output ActivityParameterNode, tokens held by an ObjectNode may leave the node on outgoing ActivityEdges. Unified Modeling Language 2.5.1 Activity, ObjectNode, token, object token, ActivityParameterNode, ActivityEdge
SEMANTIC ExecutableNodes actually carry out the desired behavior of an Activity. If an ExecutableNode has incoming ControlFlows, then there must be tokens offered on all these flows that it accepts before beginning execution. Unified Modeling Language 2.5.1 Activity, ActivityNode, ExecutableNode, Action, ActivityNode::incoming, ControlFlow
INFO Execution of the test section may precede or follow execution of the bodyPart, depending on whether isTestFirst is true or false, respectively. ... If the bodyPart is executed first (isTestFirst=false), it is always executed at least once ... Unified Modeling Language 2.5.1 Activity, Activity Diagram, LoopNode, LoopNode::test, LoopNode::bodyPart, LoopNode::isTestedFirst
INFO Exit points are the inverse of entry points. That is, Transitions originating from a Vertex within the composite State can terminate on the exit point. Unified Modeling Language 2.5.1 State, StateMachine, Transition, PseudostateKind, PseudostateKind::exitPoint, Vertex