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 A traction index is calculated every 10 ms, which is the slower of the two signal rates. The accelerometer signals come in continuously, which means the input to Calculate Traction does not buffer values. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, Rate, Rate::rate, Continuous, «continuous»
EXAMPLE, INFO When Monitor Traction is enabled, it begins listening for signals coming in from the wheel and accelerometer, as indicated by the signal receipt symbols on the left, which begin listening automatically when the activity is enabled. OMG Systems Modeling Language (SysML) 1.6 Signal, accept signal action, SignalEvent, AcceptEventAction, AcceptEventAction::isUnmarshall SysML specification figure
EXAMPLE, INFO The activity diagram for Monitor Traction is shown in Figure 11-11. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, SysML Activity Diagram
INFO The rake notations on the control operator and Monitor Traction indicate they are further defined by activities, as shown in Figure 11-11 and Figure 11-12. An alternative notation for this activity decomposition is shown in Figure 11-13. OMG Systems Modeling Language (SysML) 1.6 rake icon, Activity SysML specification figure, ControlOperator, ControlValueKind, ControlValueKind::disable, ControlValueKind::enable
INFO While the monitor is enabled, it outputs a modulation frequency for applying the brakes as determined by the ABS system. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, ControlOperator, ControlValueKind, ControlValueKind::disable, ControlValueKind::enable
INFO When the brake pressure goes to zero, disable control values are emitted from the control operator. The first one disables the monitor, and the rest have no effect. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, ControlOperator, ControlValueKind, ControlValueKind::disable, ControlValueKind::enable
INFO No pins are used on Monitor Traction, so once it is enabled, the continuously arriving enable control values from the control operator have no effect, per UML semantics. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, ControlOperator, ControlValueKind, ControlValueKind::disable, ControlValueKind::enable
INFO Brake pressure information also flows to a control operator that outputs a control value to enable or disable the Monitor Traction behavior. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, ControlOperator, ControlValueKind, ControlValueKind::disable, ControlValueKind::enable
INFO The Driving behavior outputs a brake pressure continuously to the Braking behavior while both are executing, as indicated by the «continuous» rate and streaming properties (streaming is a characteristic of UML behavior parameters that supports ... OMG Systems Modeling Language (SysML) 1.6 Behavior, Parameter::isStreaming, execution SysML specification figure, Continuous, «continuous», Rate
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 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 Figure 11-10 shows a simplified model of driving and braking in a car that has an automatic braking system. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, Continuous, «continuous»
INFO An ObjectFlow is an ActivityEdge that is traversed by object tokens that may hold values. Object flows also support multicast/receive, token selection from object nodes, and transformation of tokens. Unified Modeling Language 2.5.1 ObjectFlow
CONSTRAINT no_executable_nodes ObjectFlows may not have ExecutableNodes at either end. Unified Modeling Language 2.5.1 ObjectFlow
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 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
INFO A control Pin (with isControl=true) must have a control type (isControlType=true), so that they may be used with ControlFlows. Unified Modeling Language 2.5.1 Pin, control Pin, Pin::isControl, ObjectNode::isControlType, control token
INFO object_nodes ControlFlows may not have ObjectNodes at either end, except for ObjectNodes with control type. Unified Modeling Language 2.5.1 ControlFlow, ActivityEdge, token, control token, object token, ObjectNode, ObjectNode::isControlType, Pin::isControl
INFO A ControlFlow is an ActivityEdge traversed by control tokens or object tokens of control type, which are use to control the execution of ExecutableNodes Unified Modeling Language 2.5.1 ControlFlow, ActivityEdge, token, control token, object token
INFO ObjectNode::upperBound : ValueSpecification [0..1] The maximum number of tokens that may be held by this ObjectNode. Tokens cannot flow into the ObjectNode if the upperBound is reached. If no upperBound is specified, then there is no limit on how many ... Unified Modeling Language 2.5.1 ObjectNode, ObjectNode::upperBound, ValueSpecification, token, object token
INFO ObjectNode::selection : Behavior [0..1] ... A Behavior used to select tokens to be offered on outgoing ActivityEdges. Unified Modeling Language 2.5.1 ObjectNode, ObjectNode::selection
INFO ObjectNode::inState : State [0..*] ... The States required to be associated with the values held by tokens on this ObjectNode. Unified Modeling Language 2.5.1 ObjectNode::isControlType, ObjectNodeOrderingKind, ObjectNodeOrderingKind::FIFO
INFO ObjectNode::ordering : ObjectNodeOrderingKind [1..1] = FIFO Indicates how the tokens held by the ObjectNode are ordered for selection to traverse ActivityEdges outgoing from the ObjectNode. Unified Modeling Language 2.5.1 ObjectNode, ObjectNodeOrderingKind, ObjectNodeOrderingKind::FIFO
INFO ObjectNode::isControlType : Boolean [1..1] = false Indicates whether the type of the ObjectNode is to be treated as representing control values that may traverse ControlFlows. Unified Modeling Language 2.5.1 ObjectNode::isControlType
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
INFO The associations may be composition if the intention is to delete instances of the classifier flowing the activity when the activity is terminated. See example in 11.4, Usage Examples. OMG Systems Modeling Language (SysML) 1.6 Association, Classifier, ObjectNode, Variable, Parameter, AggregationKind::composite, AggregationKind Block, ValueType, SysML Block Definition Diagram, AdjunctProperty, AdjunctProperty::principal
INFO Like any association end or property these can be the subject of parametric constraints, design values, units, and quantity kinds. OMG Systems Modeling Language (SysML) 1.6 Association, Classifier, ObjectNode, Variable, Parameter Block, ValueType, SysML Block Definition Diagram, AdjunctProperty, AdjunctProperty::principal
INFO Properties with AdjunctProperty applied, where the principal of the AdjunctProperty is an object node, variable, or parameter, can be used as the end of the associations toward the object node, variable, or parameter type. OMG Systems Modeling Language (SysML) 1.6 Association, Classifier, ObjectNode, Variable, Parameter Block, ValueType, SysML Block Definition Diagram, AdjunctProperty, AdjunctProperty::principal
INFO This supports linking the execution of the activity with items that are flowing through the activity or assigned to variables or parameters, and happen to be contained by an object node or assigned to a variable or parameter at the time the link exists. OMG Systems Modeling Language (SysML) 1.6 Association, Classifier, ObjectNode, Variable, Parameter Block, ValueType, SysML Block Definition Diagram
INFO Associations can be used between activities and classifiers (blocks or value types) that are the type of object nodes, variables, or parameters in the activity, as shown in Figure 11-5. OMG Systems Modeling Language (SysML) 1.6 Association, Classifier, ObjectNode, Variable, Parameter Block, ValueType, SysML Block Definition Diagram
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
NOTATION CallBehaviorActions in activity diagrams may optionally show the action name with the name of the invoked behavior using the colon notation shown in Figure 11-3. OMG Systems Modeling Language (SysML) 1.6 CallBehaviorAction, Action, NamedElement::name, Behavior, Activity SysML Activity Diagram
INFO, NOTATION Stereotypes applied to behaviors may appear on the notation for CallBehaviorAction when invoking those behaviors, as shown in Figure 11-2. OMG Systems Modeling Language (SysML) 1.6 CallBehaviorAction, Behavior, Activity Diagram, Stereotype, «keyword» SysML Activity Diagram secondary stereotype, SysML, Systems Modeling Language, MagicDraw SysML, Cameo Systems Modeler
INFO, NOTATION Activities in block definition diagrams can also appear with the same notation as CallBehaviorAction, except the rake notation can be omitted, if desired. Also see use of activities in block definition diagrams that include ObjectNodes. OMG Systems Modeling Language (SysML) 1.6 CallBehaviorAction, ObjectNode, Activity SysML Block Definition Diagram functional allocation, functional decomposition
INFO Properties with AdjunctProperty applied, where the principal of the AdjunctProperties are call actions, including call behavior actions, can be used as the part end of the associations. See 8.3.2.2 for constraints when AdjunctProperty is used ... OMG Systems Modeling Language (SysML) 1.6 Property, CallBehaviorAction, Association, Association::ownedEnd, Activity SysML Block Definition Diagram, Block, AdjunctProperty functional allocation, functional decomposition
INFO This provides a means for representing activity decomposition in a way that is similar to classical functional decomposition hierarchies. OMG Systems Modeling Language (SysML) 1.6 Activity «activity», SysML Block Definition Diagram, Block functional allocation, functional decomposition
INFO, NOTATION Activities in block definition diagrams appear as regular blocks, except the «activity» keyword may be used to indicate the Block stereotype is applied to an activity, as shown in Figure 11-1. See example in 11.4, Usage Examples. OMG Systems Modeling Language (SysML) 1.6 Activity «activity», SysML Block Definition Diagram, Block
INFO The Sample Problem in Annex D provides definitions of the containing EconomyContext block for which this parametric diagram is shown. OMG Systems Modeling Language (SysML) 1.6 SysML Parametric Diagram, BindingConnector
INFO A parametric diagram is similar to an internal block diagram with the exception that the only connectors that may be shown are binding connectors. OMG Systems Modeling Language (SysML) 1.6 SysML Parametric Diagram, BindingConnector
INFO parametric diagrams can make use of the nested property name notation to refer to multiple levels of nested property containment, as shown in this example. OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock, constraint property, SysML Parametric Diagram, nested Property, multi-level property path
INFO Figure D.32 shows the use of constraint properties on a parametric diagram. This diagram shows the use of nested property references to the properties of the parts; OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock, constraint property, SysML Parametric Diagram, nested Property, multi-level property path
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 The port types have an additional flow property that is not in the nested ports. These are for the flow of the engine, as opposed to its parts. OMG Systems Modeling Language (SysML) 1.6 Connector, InformationFlow::conveyed ItemFlow, AssociationBlock
INFO In Figure 9-17, the item flow classifier (Engine) composes the classifiers of the items flows in the decomposition from Figure 9-17. OMG Systems Modeling Language (SysML) 1.6 Connector, InformationFlow::conveyed ItemFlow, AssociationBlock
INFO The flow properties are all in the types of the nested ports, while the composing item flow summarizes the kinds of items flowing by generalization. OMG Systems Modeling Language (SysML) 1.6 Connector, InformationFlow::conveyed ItemFlow, AssociationBlock
INFO In Figure 9-16, the item flow classifier (EnginePart) is a supertype of the classifiers of the item flows in the decomposition. OMG Systems Modeling Language (SysML) 1.6 Connector, InformationFlow::conveyed ItemFlow, AssociationBlock
INFO Figures 9.16 and 9.17 are examples of item flow decomposition that modelers might choose, but they are not the only possible decompositions and are not required. OMG Systems Modeling Language (SysML) 1.6 Connector ItemFlow, AssociationBlock
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 The item flow does not require the heater to accept any kind of fluid, because the source of flow is still producing water, regardless of the generality of the item flow. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO The connection to the water heater is compatible because it accepts any kind of water, including distilled. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO Item flows can also be more general than the actual flow, as shown by the connector on the right. The water distiller produces distilled water, but the item flow is for any kind of fluid. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO The radiator on the left requires distilled water, and its connection to the water heater is compatible because the item flow narrows the items to distilled water. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO The water heater is fed from a water distiller in this particular usage, so the modeler knows the output will always be distilled water, rather than other kinds of water. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO For example, in Figure 9-15 the connector to the output of the water heater has an item flow indicating distilled water is flowing, even though the out flow property of the water heater indicates it produces water. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO Item flows in internal block diagrams specify flows local to a block. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO The keyword «connector» before a property name indicates the property is stereotyped by ConnectorProperty. OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass ConnectorProperty, AssociationBlock, ParticipantProperty, «connector»
INFO A connector property can optionally be shown in an internal block diagram with a dotted line from the connector line to a rectangle notating the connector property. OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass ConnectorProperty, AssociationBlock, ParticipantProperty
INFO The values of a connector property are instances of the association block created due to the connector referred to by the connector property. OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass ConnectorProperty, AssociationBlock, ParticipantProperty
INFO These connectors specify instances of the association block created within the instances of the block that owns the connector. OMG Systems Modeling Language (SysML) 1.6 ConnectorProperty, Connector, AssociationClass AssociationBlock, ParticipantProperty
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
EXAMPLE, INFO The lower connector shows its connector property explicitly, enabling the pipe it contains to be connected to a mounting bracket (the additional part and connector definitions are omitted for brevity). OMG Systems Modeling Language (SysML) 1.6 Connector AssociationBlock, SysML specification figure
EXAMPLE, INFO Figure 9-14 modifies Figure 9-9 to use Plumbing as a connector type within the Water Delivery association block. OMG Systems Modeling Language (SysML) 1.6 Connector AssociationBlock, SysML specification figure
EXAMPLE, INFO Figure 9-13 shows the internal structure for the Plumbing association block, which includes a pipe and two fittings (the additional part and connector definitions are omitted for brevity). OMG Systems Modeling Language (SysML) 1.6 Connector, part AssociationBlock, part property
EXAMPLE, INFO Figure 9-12 adds a Plumbing association block for the association between Spigot and Faucet Inlet in Figure 9-11. OMG Systems Modeling Language (SysML) 1.6 Association AssociationBlock
EXAMPLE, INFO The composite connector for Water Delivery is reused three times to establish connections between spigots on the water supply and the inlets of faucets on the bath, sink, and shower. OMG Systems Modeling Language (SysML) 1.6 Connector composite connector
EXAMPLE, INFO The top portion of Figure 9-11 shows specializations of the block WaterClient into Bath, Sink, and Shower. These are used as part types in the internal structure of the block House 2 shown in the lower portion of the figure OMG Systems Modeling Language (SysML) 1.6
EXAMPLE The connector in the top view “decomposes” into the subconnectors in the lower view according to the internal structure of Water Delivery. The subconnectors relate the nested ports of :WaterSupply to the nested ports of :WaterClient. OMG Systems Modeling Language (SysML) 1.6 Connector SysML specification figure, ParticipantProperty, AssociationBlock
EXAMPLE Figure 9-10 shows two views of a block House with a connector of type Water Delivery. OMG Systems Modeling Language (SysML) 1.6 Connector SysML specification figure, ParticipantProperty, AssociationBlock
INFO The internal structure connects hot and cold ports of the participants. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock, ParticipantProperty
CONSTRAINT The aggregation of a property stereotyped by ParticipantProperty shall be none OMG Systems Modeling Language (SysML) 1.6 AggregationKind::none, AggregationKind ParticipantProperty
INFO The type of participant properties is shown for clarity, but is always the same as the association end type and can be elided. They are shown with dashed rectangles because they are reference properties. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock, ParticipantProperty
INFO The participant properties identify the spigot bank and faucet being connected. The end property on the stereotype refers to the corresponding association end in Figure 9-8. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock, ParticipantProperty, ParticipantProperty::end
INFO Figure 9-9 shows the internal structure of Water Delivery defining connectors between the spigots in the bank and inlets on the faucet. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock
INFO Figure 9-8 shows an association block Water Delivery between a bank of spigots and a faucet. The «port» keyword indicates which association ends are ports (associations use properties as ends, which can be ports). OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock
INFO Ports appearing in block compartments can have their direction appear textually before the port name as “in,” “out,” or “inout” determined in the same way as the arrow direction. OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind::inout, nested Port
INFO Ports with types that have flow properties in different directions or flow properties that are all in both directions, including have two open arrow heads inside them facing away from each other (<>). This includes the directions of nested and... OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind::inout, nested Port
INFO This includes the direction of flow properties on nested ports, and if the port is full and its type is unencapsulated, ports on parts of the port, recursively. The arrows are perpendicular to the boundary lines they overlap. OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out
INFO Ports with types that have flow properties all in the same direction, either all in or all out, can have an arrow inside them indicating the direction of the properties with respect to the owning block. OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out
INFO The lower and upper properties of the stereotype give the minimum and maximum number of values, respectively, of the property at the bound end of the related bound reference, for each object reached by navigation along its binding path. OMG Systems Modeling Language (SysML) 1.6 EndPathMultiplicity, BoundReference, EndPathMultiplicity::lower, EndPathMultiplicity::upper
INFO The EndPathMultiplicity stereotype can be applied to properties that are related by redefinition to properties that have BoundReference applied. OMG Systems Modeling Language (SysML) 1.6 EndPathMultiplicity, BoundReference
INFO The specialization on the lower right restricts the number of cylinders to between six and eight, rules out any roll bar, and limits lug bolts per wheel to between 6 and 7, by giving the end path upper and lower values. OMG Systems Modeling Language (SysML) 1.6 Generalization, Property::redefinedProperty BoundReference, BindingConnector, nested Property
INFO The specialization on the lower left restricts the number of cylinders to four, requires a light roll bar, and a total of 24 lug bolts over all the wheels. OMG Systems Modeling Language (SysML) 1.6 Generalization, Property::redefinedProperty BoundReference, BindingConnector, nested Property
INFO The general block on the top does not restrict the bound properties, except the total number of lug bolts is required to be between 24 and 32, rather than 24 and 40 as the associations in Figure 8-15 allow. OMG Systems Modeling Language (SysML) 1.6 Generalization, Property::redefinedProperty BoundReference, BindingConnector, nested Property
INFO Figure 8-17 shows specializations for vehicles that restrict aspects of nested parts by redefining bound references. Paths for bound references are based on the property paths of the corresponding binding connectors. OMG Systems Modeling Language (SysML) 1.6 BoundReference, nested Property, BindingConnector
INFO Figure 8-16 shows the same decomposition in an internal block diagram that includes bound references. The binding connectors have nested connector ends, because they link inside the parts of the vehicle. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, SysML Internal Block Diagram, BoundReference, NestedConnectorEnd
INFO Figure 8-15 shows an example decomposition for vehicles in a block definition diagram. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, SysML Block Definition Diagram
INFO The binding path includes the property at the bound end, and before that, the property path of the bound end, if it is a nested connector end. OMG Systems Modeling Language (SysML) 1.6 BoundReference, BindingConnector, BoundReference::/bindingPath
INFO The bound end of the stereotype is a connector end of one of the binding connectors, opposite the stereotyped property. OMG Systems Modeling Language (SysML) 1.6 BoundReference, BindingConnector, BoundReference::boundEnd
INFO The BoundReference stereotype can be applied to properties that have binding connectors, to highlight their usage as constraining other properties. The bound end of the stereotype is a connector end of one of the binding connectors, opposite the .. OMG Systems Modeling Language (SysML) 1.6 BoundReference, BindingConnector
INFO This portion of concrete syntax is the same as may be shown for values within the UML instance specification notation, but this is the only element of UML InstanceSpecification notation that may be shown in an initial values compartment. OMG Systems Modeling Language (SysML) 1.6 compartment initial values, initialValues compartment, context-specific values
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 Initial value compartments may be specified within nested properties, which then apply only in the particular usage context defined by the outermost containing block. OMG Systems Modeling Language (SysML) 1.6 compartment initial values, initialValues compartment, context-specific values
INFO A compartment with a label of “initialValues” may be used to show values of properties belonging to a containing block. These values override any default values that may have been previously specified on these properties on their originally defining block OMG Systems Modeling Language (SysML) 1.6 initial values, initialValues compartment, context-specific values
EXAMPLE, INFO Figure D.40 shows the same allocation relationships shown in Figure D.38, but in a more compact tabular representation. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Allocate, allocation, «allocate»
EXAMPLE, INFO Figure D.41[ ]shows a particular Hybrid SUV (VIN number) satisfying the EPA fuel economy test. Serial numbers of specific relevant parts are indicated. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem
EXAMPLE, INFO Figure D.39 depicts a subset of the PowerSubsystem, specifically showing the allocation relationships generated in Figure D.38. OMG Systems Modeling Language (SysML) 1.6 allocation, Allocate, «allocate»
INFO, NOTATION Multiple arrows coming out of a standalone Pin rectangle is an optional notation for multiple edges coming out of an OutputPin. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow
INFO, NOTATION The standalone Pin in the notation maps to an OutputPin and an InputPin and one ObjectFlow edge between them in the underlying model. This form should be avoided if the Pins are not of the same type. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow
INFO, NOTATION The situation in which the OutputPin of one Action is connected to the InputPin of the same name in another Action via an ObjectFlow may be shown by the optional notations of Figure 16.6. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow