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
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::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::/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::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::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::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::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::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::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 A Transition represents an arc between exactly one source Vertex and exactly one Target vertex (the source and targets may be the same Vertex). It may form part of a compound transition, which takes the StateMachine from one steady State configuration... Unified Modeling Language 2.5.1 State, StateMachine, Transition, Vertex, compound transition, Transition::source, Transition::target
INFO Regardless of how a State is exited, the StateMachine is deemed to have “left” that State only after the exit Behavior (if defined) of that State has completed execution. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit
INFO When exiting from an orthogonal State, each of its Regions is exited. After that, the exit Behavior of the State is executed. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit, State::/isOrthogonal, orthogonal Region, Region
INFO If the exit occurs through an exitPoint Pseudostate, then the exit Behavior of the State is executed after the effect Behavior of the Transition terminating on the exit point. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit, composite State, State::/isComposite, PseudostateKind::exitPoint, Transition, Transition::effect
INFO When exiting from a composite State, exit commences with the innermost State in the active state configuration. This means that exit Behaviors are executed in sequence starting with the innermost active State. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit, composite State, State::/isComposite, substate, active state configuration
INFO If the State has a doActivity Behavior that is still executing when the State is exited, that Behavior is aborted before the exit Behavior commences execution. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit, State::doActivity
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
INFO ... if a doActivity Behavior is defined for the State, this Behavior commences execution immediately after the entry Behavior is executed. It executes concurrently with any subsequent Behaviors associated with entering the State, such as the entry ... Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::entry, State::doActivity
INFO ... the entry Behavior of the State is executed (if defined) upon entry, but only after any effect Behavior associated with the incoming Transition is completed. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::entry, Transition, Transition::effect
INFO A State may also have an associated doActivity Behavior. This Behavior commences execution when the State is entered (but only after the State entry Behavior has completed) and executes concurrently with any other Behaviors that may be associated ... Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::doActivity
INFO In addition, a State may also have an associated exit Behavior, which, if defined, is executed whenever the State is exited. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::exit
INFO A State may have an associated entry Behavior. This Behavior, if defined, is executed whenever the State is entered through an external Transition. Unified Modeling Language 2.5.1 State, StateMachine, Behavior, State::entry, Transition, external Transition
INFO A State is said to be active if it is part of the active state configuration. Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite, State::/isSimple, state configuration, valid state configuration, active state configuration
INFO StateMachine execution is represented by transitions from one active state configuration to another in response to Event occurrences that match the Triggers of the StateMachine. Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite, State::/isSimple, state configuration, valid state configuration, active state configuration, Event, Trigger, Transition::trigger, Transition
INFO An executing StateMachine instance can only be in exactly one state configuration at a time, which is referred to as its active state configuration. Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite, State::/isSimple, state configuration, valid state configuration, active state configuration
INFO For example, one valid state configuration for an execution of the StateMachine depicted in Figure 14.9 is: <CourseAttempt - Studying – (Studying::Lab2, Studying::TermProject, Studying::FinalTest)>. Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite, State::/isSimple, state configuration, valid state configuration
INFO Similarly, we can talk about such a hierarchy of substates within a composite State. This complex hierarchy of States is referred to as a state configuration (of a State or a StateMachine). Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite, State::/isSimple, state configuration
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
INFO In general, a StateMachine can have multiple Regions, each of which may contain States of its own, some of which may be composites with their own multiple Regions, etc. Unified Modeling Language 2.5.1 State, StateMachine, Region, composite State, State::/isComposite
INFO A SignalEvent represents the receipt of an asynchronous Signal instance. Unified Modeling Language 2.5.1 Event, MessageEvent, SignalEvent, Trigger, Trigger::event, Message, Operation, object, Signal, SignalEvent::signal
INFO A CallEvent models the receipt by an object of a message invoking a call of an Operation. Unified Modeling Language 2.5.1 Event, MessageEvent, CallEvent, Trigger, Trigger::event, Message, Operation, object, CallEvent::operation
INFO A trigger for an AnyReceiveEvent is triggered by the receipt of any message that is not explicitly handled by any related trigger. Unified Modeling Language 2.5.1 Event, MessageEvent, AnyReceiveEvent, Trigger, Trigger::event, Message
INFO A TimeEvent is an Event that occurs at a specific point in time. Unified Modeling Language 2.5.1 Event, TimeEvent, TimeEvent::isRelative, TimeEvent::when time
INFO A ChangeEvent models a change in the system configuration that makes a condition true. Unified Modeling Language 2.5.1 Event, ChangeEvent, ChangeEvent::changeExpression, ValueSpecification, Boolean
INFO An Event is the specification of some occurrence that may potentially trigger effects by an object. Unified Modeling Language 2.5.1 Event, object, Event occurrence, Trigger, Trigger::event, Transition::trigger, ChangeEvent, MessageEvent, TimeEvent
INFO A MessageEvent specifies the receipt by an object of either an Operation call or a Signal instance. Unified Modeling Language 2.5.1 Event, MessageEvent, object, Operation, Signal, CallEvent, SignalEvent, AnyReceiveEvent
INFO A given BehavioredClassifier may implement more than one Interface and that an Interface may be implemented by a number of different BehavioredClassifiers. Unified Modeling Language 2.5.1 BehavioredClassifier, Interface, BehavioredClassifier::interfaceRealization, InterfaceRealization, provided Interface, required Interface
INFO Required Interfaces specify services that a BehavioredClassifier needs in order to perform its function and fulfill its own obligations to its clients. Unified Modeling Language 2.5.1 BehavioredClassifier, Interface, Usage, required Interface
INFO Interfaces may also be used to specify required Interfaces, which are specified by a Usage dependency between the BehavioredClassifier and the corresponding Interfaces. Unified Modeling Language 2.5.1 BehavioredClassifier, Interface, Usage, required Interface
INFO The set of Interfaces realized by a BehavioredClassifier are its provided Interfaces, which represent the services and obligations that instances of that BehavioredClassifier offer to their clients. Unified Modeling Language 2.5.1 BehavioredClassifier, Interface, BehavioredClassifier::interfaceRealization, InterfaceRealization, provided Interface
INFO The receptions compartment contains ownedReceptions ... Unified Modeling Language 2.5.1 Class, symbol, compartment, Reception, receptions compartment, Signal
INFO The operations compartment of a Class contains notation for its ownedOperations ... Unified Modeling Language 2.5.1 Class, symbol, compartment, Operation, Class::ownedOperation, operations compartment
INFO The parametric diagram is a new SysML diagram type that describes the constraints among the properties associated with blocks. This diagram is used to integrate behavior and structure models with engineering analysis models such as performance, ... OMG Systems Modeling Language (SysML) 1.6 Diagram, Constraint SysML Parametric Diagram, constraint parameter, ConstraintBlock Systems Modeling Language, SysML, mathematics, equation, engineering analysis
INFO The requirement diagram is a new SysML diagram type. A requirement diagram provides a modeling construct for text- based requirements, and the relationship between requirements and other model elements that satisfy or verify them. OMG Systems Modeling Language (SysML) 1.6 Diagram SysML Requirement Diagram, Requirement, Satisfy, Verify, TestCase, DeriveReqt, Copy, AbstractRequirement::text Systems Modeling Language, SysML, requirements engineering
INFO Tabular representations, such as the allocation table, are used in SysML but are not considered part of the diagram taxonomy. OMG Systems Modeling Language (SysML) 1.6 Diagram, Activity Diagram SysML Activity Diagram
INFO Activity diagrams have also been modified via the activity extensions. OMG Systems Modeling Language (SysML) 1.6 Diagram, Activity Diagram SysML Activity Diagram
INFO For example, the block definition diagram and internal block diagram are similar to the UML class diagram and composite structure diagram respectively, but include extensions ... OMG Systems Modeling Language (SysML) 1.6 Diagram, Class Diagram, Composite Structure Diagram SysML Block Definition Diagram, SysML Internal Block Diagram
INFO SysML reuses many of the major diagram types of UML. In some cases, the UML diagrams are strictly reused, such as use case, sequence, state machine, and package diagrams, whereas in other cases they are modified so that they are consistent with SysML ... OMG Systems Modeling Language (SysML) 1.6 Diagram, UseCase Diagram, Sequence Diagram, StateMachine Diagram, Package Diagram
INFO In the case of the profile diagram, profile definitions can be captured on a package diagram and the parametric diagram. OMG Systems Modeling Language (SysML) 1.6 Diagram, Object Diagram, Communication Diagram, Interaction Overview Diagram, Timing Diagram, Deployment Diagram, Profile Diagram SysML Package Diagram, SysML Parametric Diagram
INFO SysML does not use all of the UML diagram types such as the object diagram, communication diagram, interaction overview diagram, timing diagram, deployment diagram, and profile diagram. OMG Systems Modeling Language (SysML) 1.6 Diagram, Object Diagram, Communication Diagram, Interaction Overview Diagram, Timing Diagram, Deployment Diagram, Profile Diagram
INFO For example “velocity” can be specified as the product of “length” to the power one times “time” to the power minus one, and subsequently “speed” can be specified as “velocity” to the power one. OMG Systems Modeling Language (SysML) 1.6 DerivedQuantityKind, QuantityKind
INFO A DerivedQuantityKind may also be used to define a synonym kind of quantity for another kind of quantity. OMG Systems Modeling Language (SysML) 1.6 DerivedQuantityKind, QuantityKind
INFO A DerivedQuantityKind is a QuantityKind that represents a kind of quantity that is defined as a product of powers of one or more other kinds of quantity. OMG Systems Modeling Language (SysML) 1.6 DerivedQuantityKind, QuantityKind
INFO For example the measurement unit “metre per second” for “velocity” is specified as the product of “metre” to the power one times “second” to the power minus one. OMG Systems Modeling Language (SysML) 1.6 Unit, DerivedUnit
INFO A DerivedUnit is a Unit that represents a measurement unit that is defined as a product of powers of one or more other measurement units. OMG Systems Modeling Language (SysML) 1.6 Unit, DerivedUnit
CONSTRAINT The only valid use of a Unit instance is to be referenced by the unit property of a ValueType stereotype. 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 The definitionURI of an InstanceSpecification classified by a kind of Unit identifies the particular "measurement unit" [VIM3-1.9] that the InstanceSpecification represents. OMG Systems Modeling Language (SysML) 1.6 InstanceSpecification QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO Modelers specialize Unit as done in SysMLs QUDV model library or in a similar manner in other model libraries. OMG Systems Modeling Language (SysML) 1.6 ModelLibrary 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 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 A unit may also specify less stable or precise ways to express some value, such as a cost expressed in some currency, or a severity rating measured by a numerical scale. OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO A unit often relies on precise and reproducible ways to measure the unit. For example, a unit of length such as meter may be specified as a multiple of a particular wavelength of light. OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO A Unit is a quantity 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 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO The only valid use of a QuantityKind instance is to be referenced by the quantityKind property of a ValueType or Unit. 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 "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 The definitionURI of an InstanceSpecification classified by a kind of QuantityKind identifies the particular "kind-of-quantity" [VIM3-1.2] that the InstanceSpecification represents. OMG Systems Modeling Language (SysML) 1.6 InstanceSpecification QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind, Unit::definitionURI, QuantityKind::definitionURI scientific unit system, VIM3
INFO Modelers specialize QuantityKind as done in SysMLs QUDV model library or in a similar manner in other model libraries. OMG Systems Modeling Language (SysML) 1.6 ModelLibrary QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind scientific unit system, VIM3
INFO ... a SysML value property is understood to correspond to the VIM concept of "quantity" defined as a "property of a phenomenon, body or substance, where the property has a magnitude that can be expressed as a number and a reference" [VIM3-1.1]. OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind scientific unit system, VIM3
INFO QuantityKind, or a specialization of it, classifies an InstanceSpecification to define a particular "kind-of-quantity" in the sense of an "aspect common to mutually comparable quantities" [VIM3-1.2], ... OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind scientific unit system
INFO QuantityKind 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 scientific unit system
INFO A QuantityKind is a kind of quantity that may be stated by means of defined units. For example, the quantity kind of length may be measured by units of meters, kilometers, or feet. OMG Systems Modeling Language (SysML) 1.6 QuantityKind, Unit, Unit::quantityKind, ValueType::quantityKind scientific unit system
INFO Slot::value : ValueSpecification [0..*]{ordered, subsets Element::ownedElement} ... The value or values held by the Slot. Unified Modeling Language 2.5.1 Slot, InstanceSpecification::slot, StructuralFeature, Slot::value, ValueSpecification
INFO Slot::owningInstance : InstanceSpecification [1..1] ... The InstanceSpecification that owns this Slot. Unified Modeling Language 2.5.1 Slot, InstanceSpecification::slot, StructuralFeature, Slot::owningInstance
INFO Slot::definingFeature : StructuralFeature [1..1] ... The StructuralFeature that specifies the values that may be held by the Slot. Unified Modeling Language 2.5.1 Slot, InstanceSpecification::slot, StructuralFeature, Slot::definingFeature
INFO A Slot designates that an entity modeled by an InstanceSpecification has a value or values for a specific StructuralFeature. OMG Systems Modeling Language (SysML) 1.6 Slot, InstanceSpecification::slot, StructuralFeature, Slot::definingFeature, Slot::owningInstance, Slot::value
INFO InstanceSpecification::specification : ValueSpecification [0..1] ... A specification of how to compute, derive, or construct the instance. Unified Modeling Language 2.5.1 instance, InstanceSpecification, InstanceSpecification::classifier, ValueSpecification
INFO InstanceSpecification::slot : Slot [0..*] ... It is not necessary to model a Slot for every StructuralFeature, in which case the InstanceSpecification is a partial description. Unified Modeling Language 2.5.1 instance, InstanceSpecification, InstanceSpecification::slot, Slot, StructuralFeature, Classifier
INFO InstanceSpecification::slot : Slot [0..*] ... A Slot giving the value or values of a StructuralFeature of the instance. An InstanceSpecification can have one Slot per StructuralFeature of its Classifiers, including inherited features. ... Unified Modeling Language 2.5.1 instance, InstanceSpecification, InstanceSpecification::slot, Slot, StructuralFeature, Classifier
INFO InstanceSpecification::classifer : Classifier [0..*] ... The Classifier or Classifiers of the represented instance. If multiple Classifiers are specified, the instance is classified by all of them. Unified Modeling Language 2.5.1 instance, InstanceSpecification, InstanceSpecification::classifier, Classifier
INFO An InstanceSpecification can act as a DeploymentTarget in a Deployment relationship, in the case that it represents an instance of a Node. It can also act as a DeployedArtifact, if it represents an instance of an Artifact. Unified Modeling Language 2.5.1 instance, InstanceSpecification, DeploymentTarget, Node, DeployedArtifact, Artifact
INFO An InstanceSpecification is a model element that represents an instance in a modeled system. Unified Modeling Language 2.5.1 instance, InstanceSpecification
INFO A Complex value type represents the mathematical concept of a complex number. A complex number consists of a real part defined by a real number, and an imaginary part defined by a real number multiplied by the square root of -1 ... OMG Systems Modeling Language (SysML) 1.6 ModelLibrary Complex, ValueType, PrimitiveValueType mathematics
INFO A DataType may be parameterized, bound, and used as TemplateParameters. Unified Modeling Language 2.5.1 Type, DataType, Classifier, structured DataType, TemplateParameter
INFO Instances of a structured DataType are considered to be equal if and only if the structure is the same and the values of the corresponding attributes are equal. Unified Modeling Language 2.5.1 Type, DataType, Classifier, structured DataType
INFO If a DataType has attributes (i.e., Properties owned by it and in its namespace) it is called a structured DataType. Instances of a structured DataType contain attribute values matching its attributes. Unified Modeling Language 2.5.1 Type, DataType, Classifier, structured DataType
INFO A DataType is a kind of Classifier. DataType differs from Class in that instances of a DataType are identified only by their value. All instances of a DataType with the same value are considered to be equal instances. Unified Modeling Language 2.5.1 Type, DataType, Classifier
SEMANTIC A PrimitiveType defines a predefined DataType, without any substructure. A PrimitiveType may have algebra and operations defined outside of UML, for example, mathematically. Unified Modeling Language 2.5.1 Type, DataType, PrimitiveType mathematics
INFO Block::isEncapsulated : Boolean [0..1] ... If false, or if a value is not present, then connections can be established to elements of its internal structure via deep-nested connector ends. OMG Systems Modeling Language (SysML) 1.6 Port Block::isEncapsulated, Block, NestedConnectorEnd
INFO Block::isEncapsulated : Boolean [0..1] If true, then the block is treated as a black box; a part typed by this black box can only be connected via its ports or directly to its outer boundary. OMG Systems Modeling Language (SysML) 1.6 Port Block::isEncapsulated, Block, NestedConnectorEnd
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
INFO A request that arrives at a Port that has a delegation Connector to one or more Properties or Ports on Properties will be passed on to those targets for handling. Unified Modeling Language 2.5.1 Port, Connector, Connector::kind, ConnectorKind, ConnectorKind::delegation
INFO A delegation Connector is a Connector that links a Port to a role within the owning EncapsulatedClassifier. It represents the forwarding of requests (Operation invocations and Signals). Unified Modeling Language 2.5.1 Port, Connector, Connector::kind, ConnectorKind, ConnectorKind::delegation
INFO Such a Port is called a behavior Port. If there is no Behavior defined for this EncapsulatedClassifier, any communication arriving at a behavior Port is lost. Unified Modeling Language 2.5.1 Port::isBehavior, Port, Behavior, EncapsulatedClassifier
INFO A Port has the ability, by setting the property isBehavior to true, to specify that any requests arriving at this Port are handled by the Behavior of the instance of the owning EncapsulatedClassifier, rather than being forwarded to any contained instances Unified Modeling Language 2.5.1 Port::isBehavior, Port, Behavior, EncapsulatedClassifier
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 In contrast to Associations, which specify links between any instance of the associated Classifiers, Connectors specify links between instances playing the connected parts only. Unified Modeling Language 2.5.1 Connector, instance, link, Association, Classifier
INFO A Connector specifies links that enables communication between two or more instances. Unified Modeling Language 2.5.1 Connector, instance, link
INFO A ConnectorEnd is an endpoint of a Connector, which attaches the Connector to a ConnectableElement. Unified Modeling Language 2.5.1 ConnectorEnd, Connector, link, instance, StructuredClassifier, roles, Association, ConnectableElement
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
INFO In contrast to Associations, which specify links between any suitably-typed instance of the associated Classifiers, Connectors specify links between instances playing the connected roles only. Unified Modeling Language 2.5.1 Connector, instance, StructuredClassifier, roles, Association