PhSVariable: [3] isConserved may be true only when isContinuous is true and the stereotyped property is on a block specialized from ConservedQuantityKind (see Subclause 11.2.2). Source SysPhS-1.1
PhSVariable: [2] isContinuous may be true only when the stereotyped property is typed by Real or one of its specializations. Source SysPhS-1.1
PhSVariable: [1] The stereotyped property must be typed by Real, Integer, or Boolean, or one of their specializations. Source SysPhS-1.1
PhSConstant: [3] Properties stereotyped by PhSConstant must not redefine more than one other property, which must have the same name and type and must be stereotyped by PhSVariable or PhSConstant. Source SysPhS-1.1
PhSConstant: [2] Properties stereotyped by PhSConstant must have multiplicity 1, unless they are also stereotyped by MultidimensionalElement (see Subclause 11.5). Source SysPhS-1.1
PhSConstant: [1] Properties stereotyped by PhSConstant must be typed by Real, Integer, or Boolean, or one of their specializations. Source SysPhS-1.1
Block::6_valueproperties_composite: If a property owned by a SysML Block or SysML ValueType is typed by a SysML ValueType, then the aggregation attribute of the property shall be "composite." Source OMG Systems Modeling Language (SysML) 1.6
BoundReference::7_cannot_redefine_boundreference BoundReferences shall not be applied to properties that are related by redefinition to other properties with BoundReference applied. Source OMG Systems Modeling Language (SysML) 1.6
Block:8_specializations_are_blocks: Any classifier that specializes a Block shall also have the Block stereotype or one of its specializations applied. Source OMG Systems Modeling Language (SysML) 1.6
When the «probability» stereotype is applied to output parameter sets, it gives the probability the parameter set will be given values at runtime. These shall be between zero and one inclusive, and add up to one for output parameter sets of the same ... Source OMG Systems Modeling Language (SysML) 1.6
When the «probability» stereotype is applied to edges coming out of decision nodes and object nodes, it provides an expression for the probability that the edge will be traversed. These shall be between zero and one inclusive, and add up to one ... Source OMG Systems Modeling Language (SysML) 1.6
1_lower_is_0 A parameter with the «optional» stereotypes applied shall have multiplicity.lower equal to zero, otherwise multiplicity.lower shall be greater than zero Source OMG Systems Modeling Language (SysML) 1.6
If a JoinNode does not have a joinSpec, then this is equivalent to a joinSpec Expression with the Boolean operator “and.” That is, the implicit default joinSpec condition is that there is at least one token offered on each incoming ActivityEdge. Source Unified Modeling Language 2.5.1
Alternatively, the joinSpec may consist of an Expression with the name of a single Boolean operator and no operands specified. In this case, the value of the joinSpec shall be given by applying the given operator to Boolean values indicating ... Source Unified Modeling Language 2.5.1
If the joinSpec ValueSpecification is given by a textual expression, then the names of the incoming edges may be used to denote ... the value associated with an object token offered from an ObjectFlow (if any). Source Unified Modeling Language 2.5.1
If the joinSpec ValueSpecification is given by a textual expression, then the names of the incoming edges may be used to denote a Boolean value indicating the presence (true) or absence (false) of an offer from a ControlFlow ... Source Unified Modeling Language 2.5.1
joinSpec ... This evaluation shall not be interrupted by any new tokens offered during the evaluation, nor shall concurrent evaluations be started when new tokens are offered during an evaluation. The ValueSpecification shall evaluate to a Boolean value. Source Unified Modeling Language 2.5.1
Join nodes may have a joinSpec, which is a ValueSpecification that determines the condition under which the join will emit a token. If a JoinNode has a joinSpec, then this ValueSpecification is evaluated whenever a new token is offered to the JoinNode ... Source Unified Modeling Language 2.5.1
A DecisionNode accepts tokens on its primary incoming edge and offers them to all its outgoing edges. However, each token offered on the primary incoming edge shall traverse at most one outgoing edge. Tokens are not duplicated. Source Unified Modeling Language 2.5.1
All tokens offered on the incoming edges of a MergeNode are offered to the outgoing edge. There is no synchronization of flows or joining of tokens. Source Unified Modeling Language 2.5.1
If the outgoing edge of a MergeNode is a ControlFlow, then all incoming edges must be ControlFlows, and, if the outgoing edge is an ObjectFlow, then all incoming edges must be ObjectFlows. Source Unified Modeling Language 2.5.1
A MergeNode shall have exactly one outgoing ActivityEdge but may have multiple incoming ActivityEdges. Source Unified Modeling Language 2.5.1
If any of the incoming edges of a JoinNode are ObjectFlows, the outgoing edge shall be an ObjectFlow. Otherwise the outgoing edge shall be a ControlFlow. Source Unified Modeling Language 2.5.1
The only valid use of a Unit instance is to be referenced by the unit property of a ValueType stereotype. Source OMG Systems Modeling Language (SysML) 1.6
Viewpoint::2_create_view_operation The property ownedOperation shall include at least one operation named "View" with the UML Create stereotype applied. Source OMG Systems Modeling Language (SysML) 1.6
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. Source OMG Systems Modeling Language (SysML) 1.6
A stereotype must be contained, directly or indirectly, in a profile. Source Unified Modeling Language 2.5.1
AllocateActivityPartition::1_actions_on_client_ends An Action appearing in an "AllocateActivityPartition" shall be the /client (from) end of an "allocate" dependency. The element that represents the "AllocateActivityPartition" shall be the /supplier ... Source OMG Systems Modeling Language (SysML) 1.6
Two UseCases specifying the same subject cannot be associated as each of them individually describes a complete usage of the subject. Source Unified Modeling Language 2.5.1
«physicalRequirement»: satisfied by a structural element. Source OMG Systems Modeling Language (SysML) 1.6
«performanceRequirement»: satisfied by a value property. Source OMG Systems Modeling Language (SysML) 1.6
«interfaceRequirement»: satisfied by a port, conector, item flow, and/or constraint property. Source OMG Systems Modeling Language (SysML) 1.6
«functionalRequirement»: satisfied by an operation or behavior Source OMG Systems Modeling Language (SysML) 1.6
FullPort::3_not_behavioral Full ports shall not be behavioral (isBehavior=false). Source OMG Systems Modeling Language (SysML) 1.6
FullPort::2_not_bound_to_fullport Binding connectors shall not link full ports (either directly or indirectly through other binding connectors) to other composite properties of the block owning the full port (or that blocks generalizations or specializati Source OMG Systems Modeling Language (SysML) 1.6
FullPort::1_not_proxy Full ports shall not also be proxy ports. This applies even if some of the stereotypes are on subsetted or redefined ports. Source OMG Systems Modeling Language (SysML) 1.6
Internal connectors to proxy ports can be typed by association blocks, including when the connector is binding. Association Source OMG Systems Modeling Language (SysML) 1.6
This aggregate is not a separate element of the system, and only groups the internal parts for purposes of binding to the proxy port. Source OMG Systems Modeling Language (SysML) 1.6
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... Source OMG Systems Modeling Language (SysML) 1.6
(the value of the proxy port and the connected internal part are the same; links of associations typing the connector are between all objects and themselves, and no others) Source OMG Systems Modeling Language (SysML) 1.6
BindingConnector::1_compatible_types The two ends of a binding connector shall have either the same type or types that are compatible so that equality of their values can be defined. Source OMG Systems Modeling Language (SysML) 1.6
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 ... Source OMG Systems Modeling Language (SysML) 1.6
ProxyPort::3_subports_are_proxyports Ports owned by the type of a proxy port shall be proxy ports. Source OMG Systems Modeling Language (SysML) 1.6
ProxyPort::2_interfaceblock Proxy ports shall only be typed by interface blocks. Source OMG Systems Modeling Language (SysML) 1.6
ProxyPort::1_not_fullport Proxy ports shall not also be full ports. This applies even if some of the stereotypes are on subsetted or redefined ports. Source OMG Systems Modeling Language (SysML) 1.6
InterfaceBlock::2_no_part Interface blocks composite properties are either ports, value properties or flow properties. Source OMG Systems Modeling Language (SysML) 1.6
InterfaceBlock::isconjugated_not_used Any port typed by an InterfaceBlock shall have its isConjugated property set to false. Source OMG Systems Modeling Language (SysML) 1.7beta1
InterfaceBlock::3_interfaceblock_typed_ports Ports owned by interface blocks shall only be typed by interface blocks. Source OMG Systems Modeling Language (SysML) 1.6
InterfaceBlock::1_no_behavior Interface blocks shall not own or inherit behaviors, have classifier behaviors, or methods for their behavioral features. Source OMG Systems Modeling Language (SysML) 1.6
Interface blocks cannot have behaviors, including classifier behaviors or methods, or internal parts. Source OMG Systems Modeling Language (SysML) 1.6
ItemFlow::2_type_restricted An ItemFlow itemProperty shall be typed by a ValueType, Block, or Signal. Source OMG Systems Modeling Language (SysML) 1.6
FlowProperty::1_restricted_types A FlowProperty shall be typed by a ValueType, Block, or Signal. Source OMG Systems Modeling Language (SysML) 1.6
TestCase::1_return_verdictkind The type of return parameter of the stereotyped model element shall be VerdictKind. (note this is consistent with the UML Testing Profile). Source OMG Systems Modeling Language (SysML) 1.6
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 Source OMG Systems Modeling Language (SysML) 1.6
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 Source OMG Systems Modeling Language (SysML) 1.6
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. Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::1_supplier_is_requirement The supplier shall be an element stereotyped by any subtype of «AbstractRequirement». Source OMG Systems Modeling Language (SysML) 1.6
DeriveReqt::2_client_is_requirement The client shall be an element stereotyped by a subtype of AbstractRequirement. Source OMG Systems Modeling Language (SysML) 1.6
DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement. Source OMG Systems Modeling Language (SysML) 1.6
2_same_name Properties to which AdjunctProperty [is] applied shall have the same name as the principal, if the principal is a NamedElement. Source OMG Systems Modeling Language (SysML) 1.6
no_executable_nodes ObjectFlows may not have ExecutableNodes at either end. Source Unified Modeling Language 2.5.1
The aggregation of a property stereotyped by ParticipantProperty shall be none Source OMG Systems Modeling Language (SysML) 1.6
1_streaming When the «rate» stereotype is applied to a parameter, the parameter shall be streaming. Source OMG Systems Modeling Language (SysML) 1.6
Rate::rate - In particular, the denominator for units used in the rate property shall be time units. Source OMG Systems Modeling Language (SysML) 1.6
A Stakeholder stereotype can only be applied to UML::Actor or UML::Class which are not a UML::Association. Source OMG Systems Modeling Language (SysML) 1.6
If the primary incoming edge of a DecisionNode is a ControlFlow, then all outgoing edges shall be ControlFlows and, if the primary incoming edge is an ObjectFlow, then all outgoing edges shall be ObjectFlows. Source Unified Modeling Language 2.5.1
A decisionInput Behavior has no out parameters, no inout parameters, and one return parameter. Source Unified Modeling Language 2.5.1
incoming_control_one_input_parameter If the DecisionNode has a decisionInputFlow and an incoming ControlFlow, then any decisionInput Behavior has one in Parameter ... Source Unified Modeling Language 2.5.1
DecisionNode::incoming_outgoing_edges A DecisionNode has one or two incoming ActivityEdges and at least one outgoing ActivityEdge. Source Unified Modeling Language 2.5.1
two_input_parameters If the DecisionNode has a decisionInputFlow and a second incoming ObjectFlow, then any decisionInput has two in Parameters ... Source Unified Modeling Language 2.5.1
decision_input_flow_incoming The decisionInputFlow of a DecisionNode must be an incoming ActivityEdge of the DecisionNode. Source Unified Modeling Language 2.5.1
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. Source Unified Modeling Language 2.5.1
zero_input_parameters If the DecisionNode has no decisionInputFlow and an incoming ControlFlow, then any decisionInput Behavior has no in parameters. Source Unified Modeling Language 2.5.1
7.11.2.7 LoopNode [1] fuml_loop_node_no_setup_part no setupParts in fUML self.setupPart->isEmpty() Source Semantics of a Foundational Subset for Executable UML Models 1.4
trigger_with_ports: If a Trigger specifies one or more ports, the event of the Trigger must be a MessageEvent. Source Unified Modeling Language 2.5.1
Held object tokens are offered to outgoing flows according to the general ordering rules for ObjectNodes. When an offer for a token is accepted by a downstream object node, that token is removed from the CentralBufferNode and moved to the accepting ... Source Unified Modeling Language 2.5.1
An inout Parameter shall be associated with at most one input ActivityParameterNode and at most one output ActivityParameterNode. Source Unified Modeling Language 2.5.1
An in Parameter shall not be associated with an output ActivityParameterNode and an out or return Parameter shall not be associated with an input ActivityParameterNode (though either may be associated with an ActivityParameterNode that does not have .. Source Unified Modeling Language 2.5.1
The substrings are given as either a list of LiteralString operands or as a list of StringExpression subExpressions (but it is not allowed to mix the two). Source Unified Modeling Language 2.5.1
If the insertAt InputPin is present, it has type UnlimitedNatural and multiplicity 1..1 Source Unified Modeling Language 2.5.1
The value to be added is given on the value InputPin, which is required. This InputPin has the same type as the StructuralFeature and a multiplicity of 1..1 (that is, a single value is added). Source Unified Modeling Language 2.5.1
terminate – Entering a terminate Pseudostate implies that the execution of the StateMachine is terminated immediately. The StateMachine does not exit any States nor does it perform any exit Behaviors. Any executing doActivity Behaviors are ... aborted Source Unified Modeling Language 2.5.1
shallowHistory Pseudostate can only be defined for composite States and, at most one such Pseudostate can be included in a Region of a composite State. Source Unified Modeling Language 2.5.1
shallowHistory – ... A single outgoing Transition from this Pseudostate may be defined terminating on a substate of the composite State. This substate is the default shallow history state of the composite State. Source Unified Modeling Language 2.5.1
shallowHistory – ... this type of Pseudostate is a kind of variable that represents the most recent active substate of its containing Region, but not the substates of that substate. A Transition terminating on this Pseudostate implies rest Source Unified Modeling Language 2.5.1
A deepHistory Pseudostate can only be defined for composite States and, at most one such Pseudostate can be contained in a Region of a composite State. Source Unified Modeling Language 2.5.1
exitPoint – ... If multiple Transitions from orthogonal Regions within the State terminate on this Pseudostate, then it acts like a join Pseudostate. Source Unified Modeling Language 2.5.1
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). Source Unified Modeling Language 2.5.1
exitPoint – An exitPoint Pseudostate is an exit point of a StateMachine or composite State that provides encapsulation of the insides of the State or StateMachine. Source Unified Modeling Language 2.5.1
entryPoint – ... NOTE. ... If multiple Regions are involved, the entry point acts as a fork Pseudostate. Source Unified Modeling Language 2.5.1
entryPoint – ... NOTE. If the owning State has an associated entry Behavior, this Behavior is executed before any behavior associated with the outgoing Transition. Source Unified Modeling Language 2.5.1
In each Region of the StateMachine or composite State owning the entryPoint, there is at most a single Transition from the entry point to a Vertex within that Region. Source Unified Modeling Language 2.5.1
The Transitions outgoing from a fork Pseudostate cannot have a guard or a trigger. Source Unified Modeling Language 2.5.1
Transitions terminating on a join Pseudostate cannot have a guard or a trigger. Source Unified Modeling Language 2.5.1
initial - ... It is the source for at most one Transition, which may have an associated effect Behavior, but not an associated trigger or guard. Source Unified Modeling Language 2.5.1
Any guards associated with these entry point Transitions must evaluate to true in order for the specification to be well formed. Source Unified Modeling Language 2.5.1
If the triggers of an AcceptEventAction are all for ChangeEvents and/or CallEvents, then the AcceptEventAction has no result OutputPins (unless the AcceptEventAction is an AcceptCallAction ...) Source Unified Modeling Language 2.5.1
7.10.2.2 ActivityEdge [1] fuml_activity_edge_allowed_guards A guard is only allowed if the source of the edge is a DecisionNode. Source Semantics of a Foundational Subset for Executable UML Models 1.4
NOTE. Operation referenced in the CallEvent of an AcceptCallAction should not have an associated method Behavior. Otherwise, a call to the Operation will have the immediate effect of executing the method and will not be placed into the event pool ... Source Unified Modeling Language 2.5.1
