Conform [1] The general classifier must be an element stereotyped by Viewpoint.\
Conform [2] The specific classifier must be an element that is stereotyped by View.\

Expose [1] The client must be an element stereotyped by View.\

View [1] A view must only conform to a single viewpoint.\
View [2] The derived value of the viewpoint is the classifier stereotyped by Viewpoint that is the general classifier of the generalization relationship stereotyped by Conform for which the View is the specific classifier.\
View [3] The derived values of the stakeholder attribute are the names of the classifiers stereotyped by Stakeholder that are the values of the stakeholder attribute of the general classifier of the generalization relationship stereotyped by Conform for which the View is the specific classifier.\

Viewpoint [1] The derived values of the method attribute are the names of the methods of the operations stereotyped by the UML Create stereotype on the classifier stereotyped by Viewpoint.\
Viewpoint [2] The property ownedOperation must include at least one operation named «View» with the UML Create stereotype applied.\

Binding Connector [1] The two ends of a binding connector must have either the same type or types that are compatible so that equality of their values can be defined.\

Block [1] For an association in which both ends are typed by blocks, the number of ends must be exactly two.\
Block [2] The number of ends of a connector owned by a block must be exactly two.\
#(In SysML, a binding connector is not typed by an association, so this constraint is not implied entirely by the preceding constraint.)
Block [3] In the UML metamodel on which SysML is built, any instance of the Property metaclass that is typed by a block (a Class with the «block» stereotype applied) and which is owned by an Association may not have a name and may not be defined as a navigable owned end of the association. (While the Property has a «name» property as defined by its NamedElement
inv_BlockPropertyAssociationEnd=Block [4] In the UML metamodel on which SysML is built, a Property that is typed by a block must be defined as an end of an association. (An inverse end of this association, whether owned by another block or the association itself, must always be present so there is always a metamodel element to record the inverse multiplicity of the reference.)
#No Implementation [5] The following constraint under sub clause 9.3.6, «Connector» in the UML 2 Superstructure Specification is removed by SysML: «[3] The ConnectableElements attached as roles to each ConnectorEnd owned by a Connector must be roles of the Classifier that owned the Connector, or they must be ports of such roles.»
Block [6] If a property owned by a SysML Block or SysML ValueType is typed by a SysML ValueType, then the aggregation attribute of the property must be «composite.»\
#TODO[7] Within an instance of a SysML Block, the values of any property with composite aggregation (aggregation = composite) must not contain the block in any of its own properties that also have composite aggregation, or within any unbroken chain of properties that all have composite aggregation.  (Within an instance of a SysML Block, the instances of properties with composite aggregation must form an acyclic graph.)
Block [8] Any classifier that specializes a Block must also have the Block stereotype or one of its specializations applied.
#No Implementation [9] The following constraint under sub clause 9.3.7, «ConnectorEnd» in the UML 2 Superstructure Specification is removed by SysML: «[3] The property held in self.partWithPort must not be a Port.»

BoundReference [1] Properties to which BoundReference is applied must be the role of a connector end of at least one binding connector, or generalized by such a property through redefinition.
BoundReference [2] The value of boundEnd must be a connector end of a binding connector, as identified in constraint BoundReference [1], opposite the property, as identified in constraint BoundReference [1].
#unclear-- [3] The role of boundEnd must be a property accessible by navigation from instances of the block owning the property to which BoundReference is applied, but must not be the property to which BoundReference is applied, or one that it is related to by redefinition.
BoundReference [4] The last value of bindingPath is the role of boundEnd, and the other values are the propertyPath of the NestedConnectorEnd applied to boundEnd, if any.\
BoundReference [5] Properties to which BoundReference is applied must either be a reference properties or value properties.\
BoundReference [6] Properties with BoundReference applied that have an upper multiplicity greater than one must be ordered and non-unique.\
BoundReference [7] BoundReferences must not be applied to properties that are related by redefinition to other properties with BoundReference applied.\
BoundReference [8] The binding connector identified in constraint BoundReference [1] must not have the same property on both ends, or properties related by redefinition.\

ClassifierBehaviorProperty [1] ClassifierBehaviorProperty may only be applied to properties owned (not inherited) by blocks that have classifier behaviors.\
ClassifierBehaviorProperty [2] Properties to which ClassifierBehaviorProperty applied must be composite.
ClassifierBehaviorProperty [3] Properties to which ClassifierBehaviorProperty applied must be typed by the classifier behavior of their owning block or a generalization of the classifier behavior.

ConnectorProperty [1] ConnectorProperty may only be applied to properties of classes stereotyped by Block.
ConnectorProperty [2] The connector attribute of the applied stereotype must refer to a connector owned or inherited by a block owning the property on which the stereotype is applied.
ConnectorProperty [3] The aggregation of a property stereotyped by ConnectorProperty must be composite.
ConnectorProperty [4] The type of the connector referred to by a connector attribute must be an association class stereotyped by Block.
ConnectorProperty [5] A property stereotyped by ConnectorProperty must have the same name and type as the connector referred to by the connector attribute.

DirectedRelationshipPropertyPath [1] source#context must have a value when sourcePropertyPath has a value.
DirectedRelationshipPropertyPath [2] target#context must have a value when targetPropertyPath has a value.
DirectedRelationshipPropertyPath [3] The property in the first position of the sourcePropertyPath list, if any, must be owned by the source#context or one of its generalizations.
DirectedRelationshipPropertyPath [4] The property in the first position of the targetPropertyPath list, if any, must be owned by the target#context or one of its generalizations.
DirectedRelationshipPropertyPath [5] The property at each successive position of the sourcePropertyPath and targetPropertyPath, following the first position, must be owned by the Block or ValueType that types the property at the immediately preceding position, or a generalization of the Block or ValueType.
DirectedRelationshipPropertyPath [6] The type of the property at the last position of the sourcePropertyPath list must own or inherit the source of the stereotyped directed relationship.
DirectedRelationshipPropertyPath [7] The type of the property at the last position of the targetPropertyPath list must own or inherit the target of the stereotyped directed relationship.

DistributedProperty [1] The DistributedProperty stereotype may be applied only to properties of classifiers stereotyped by Block or ValueType.\
ElementPropertyPath [1] The property at each successive position of the propertyPath attribute, following the first position, must be owned by the Block or ValueType that types the property at the immediately preceding position, or a generalization of the Block or ValueType.\

EndPathMultiplicity [1] Properties to which EndPathMultiplicity is applied must be related by redefinition to a property to which BoundReference is applied.\
EndPathMultiplicity [2] endPathLower must be non-negative.\

NestedConnectorEnd [1] The first property in propertyPath must be owned by the block that owns the connector, or one of the block's generalizations.\
NestedConnectorEnd [2] The type of the property at the last position of the propertyPath list must own or inherit the role property of the stereotyped connector end.\
NestedConnectorEnd [3] NestedConnectorEnd may only be applied to connector ends.\

ParticipantProperty [1] ParticipantProperty may only be applied to properties of association classes stereotyped by Block.
ParticipantProperty [2] ParticipantProperty may not be applied to properties that are member ends of an association.
ParticipantProperty [3] The aggregation of a property stereotyped by ParticipantProperty must be none.
ParticipantProperty [4] The end attribute of the applied stereotype must refer to a member end of the association block owning the property on which the stereotype is applied.
ParticipantProperty [5] A property stereotyped by ParticipantProperty must have the same type as the property referred to by the end attribute.
ParticipantProperty [6] The property referred to by end must have a multiplicity of 1.

PropertySpecificType [1] A classifier to which the PropertySpecificType stereotype is applied must be referenced as the type of one and only one property.
PropertySpecificType [2] The name of a classifier to which a PropertySpecificType is applied must be missing.  (The «name» attribute of the NamedElement metaclass must be empty.)

ValueType [1] Any classifier that specializes a ValueType must also have the ValueType stereotype applied.
ValueType[2] The unit of a ValueType, if any, must be an InstanceSpecification classified by SysML's Unit block in the UnitAndQuantityKind model library or a specialization of it.
ValueType[3] The quantityKind of a ValueType, if any, must be an InstanceSpecification classified by SysML's QuantityKind block in the UnitAndQuantityKind model library or a specialization of it.

#AcceptChangeStructuralFeatureEventAction
AcceptChangeStructuralFeatureEventAction [1] The action has exactly one trigger, the event of which must be a change structural feature event.
AcceptChangeStructuralFeatureEventAction[2] The action has two result pins with type and ordering the same as the type and ordering of the structural feature of the trigger event, and multiplicity compatible with the multiplicity of the structural feature.
AcceptChangeStructuralFeatureEventAction[3] The structural feature of the trigger event must be owned by or inherited by the #context of the behavior containing the action. (The #context of a behavior is either its owning block or itself if it is not owned by a block. See definition in the UML 2 Superstructure Specification.)
AcceptChangeStructuralFeatureEventAction[4] Visibility of the structural feature of the trigger event must allow access to the object performing the action.
AcceptChangeStructuralFeatureEventAction[5] The constraint under sub clause 11.3.2, «AcceptEventAction» in the UML 2 Superstructure Specification, «[2] There are no output pins if the trigger events are only ChangeEvents,» is removed for accept event actions that have AcceptChangeStructuralFeatureEventAction applied.

ChangeStructuralFeatureEvent [1] The structural feature must not be static.
ChangeStructuralFeatureEvent [2] The structural feature must have exactly one featuringClassifier.

DirectedFeature [1] DirectedFeature can only be applied to behavioral features, or to properties that do not have FlowProperty applied, including on subsetted or redefined features.
DirectedFeature[2] A non-provided operation cannot be associated with a behavior as its method.

FeatureDirection [1] A FlowProperty is typed by a ValueType, Block, or Signal.

FullPort [1]: Full ports cannot also be proxy ports. This applies even if some of the stereotypes are on subsetted or redefined ports.
FullPort [2] Binding connectors cannot link full ports (either directly or indirectly through other binding connectors) to other composite properties of the block owning the full port (or that block's generalizations or specializations), unless the composite properties are non-full ports.
FullPort [3]: Full ports cannot be behavioral (isBehavior=false).
FullPort [4]: Full ports cannot be conjugated (isConjugated=false).

InterfaceBlock [1] Interface blocks cannot own or inherit behaviors, have classifier behaviors, or methods for their behavioral features.
InterfaceBlock [2] Interface blocks cannot have composite properties that are not ports.
InterfaceBlock [3] Ports owned by interface blocks can only be typed by interface blocks.

InvocationOnNestedPortAction [1] The onPort property of an invocation action must have a value when this stereotype is applied.
InvocationOnNestedPortAction [2] The port at the first position in the onNestedPort list must be owned (directly or via inheritance) by a block that types the target pin of the invocation action, or one of the block\u2019s generalizations.
InvocationOnNestedPortAction [3] The first constraint of ElementPropertyPath applies to onNestedPort.
InvocationOnNestedPortAction [4] The type of the port at the last position of the onNestedPort list must own or inherit the onPort port of the stereotyped invocation action.
InvocationOnNestedPortAction [5] InvocationOnNestedPortAction may only be applied to invocation actions.

ItemFlow [1] A Connector or an Association, or an inherited Association must exist between the source and the target of the InformationFlow.
ItemFlow [2] An ItemFlow itemProperty is typed by a ValueType, Block, or Signal.
ItemFlow [3] itemProperty is a property of the common (possibly indirect) owner of the source and the target.
ItemFlow [4] itemProperty cannot have a value if the item flow is realized by an Association.
ItemFlow [5] If an ItemFlow has an itemProperty, one of the classifiers of conveyed items must be the same as the type of the item property.
ItemFlow [6] If an ItemFlow has an itemProperty, its name should be the same as the name of the  item flow.

ProxyPort [1] Proxy ports cannot also be full ports. This applies even if some of the stereotypes are on subsetted or redefined ports.
ProxyPort [2] Proxy ports can only be typed by interface blocks.
ProxyPort [3] Ports owned by the type of a proxy port must be proxy ports.

TriggerOnNestedPort [1] The port property of the stereotyped trigger must have exactly one value, and the value cannot be a full port.
TriggerOnNestedPort [2] The values of the onNestedPort property must not be full ports.
TriggerOnNestedPort [3] The port at the first position in the onNestedPort list must be owned by a block in which the trigger is used, or one of the block\u2019s generalizations.
TriggerOnNestedPort [4] The first constraint of ElementPropertyPath applies to onNestedPort.
TriggerOnNestedPort [5] The type of the port at the last position of the onNestedPort list must own or inherit the port port of must own or inherit the port port of
TriggerOnNestedPort [6] the stereotyped invocation action the stereotyped invocation action.

Discrete [1] The «discrete» and «continuous» stereotypes cannot be applied to the same element at the same time.

NoBuffer [1] The «nobuffer» and «overwrite» stereotypes cannot be applied to the same element at the same time.

Overwrite [1] The «overwrite» and «nobuffer» stereotypes cannot be applied to the same element at the same time.

Optional [1] Optional parameter lower value has to be 0

Probability [1] The «probability» stereotype can only be applied to activity edges that have decision nodes or object nodes as sources, or to output parameter sets.
Probability [2] When the «probability» stereotype is applied to an activity edge, then it must be applied to all edges coming out of the same source.
Probability [3] When the «probability» stereotype is applied to an output parameter set, it must also be applied to all the parameter sets of the behavior or operation owning the original parameter set. .
Probability [4] When the «probability» stereotype is applied to an output parameter set, all the output parameters must be in some parameter set.

Rate [1] When the «rate» stereotype is applied to a parameter, the parameter must be streaming.
Rate [2] The rate of a parameter must be less than or equal to rates on edges that come into or go out from pins and parameters nodes corresponding to the parameter.

Allocate [1] The Allocate stereotype may only be applied to abstractions.
Allocate [2] A single «allocate» dependency shall have only one client (from) and one supplier (to).
Allocate [3] If subtypes of the «allocate» dependency are introduced to represent more specialized forms of allocation, then they should have constraints applied to supplier and client as appropriate.


AllocateActivityPartition [1] An Action appearing in an «AllocateActivityPartition» will be the /client (from) end of an «allocate» dependency. The element that represents the «AllocateActivityPartition» will be the /supplier (to) end of the same «allocate» dependency. In the «AllocateActivityPartition» name field, Properties are designated by the use of a fully qualified name (including colon, e.g., «part_name:Block_Name»), and Classifiers are designated by a simple name (no colons, e.g., «Block_Name»).
AllocateActivityPartition [2] The «AllocateActivityPartition» maintains the constraints, but not the semantics, of the UML2::ActivityPartition. Classifiers or Properties represented by an «AllocateActivityPartition» do not have any direct responsibility for invoking behavior depicted within the partition boundaries. To depict this kind of direct responsibility, the modeler is directed to the UML 2 Superstructure specification, sub clause 12.3.10, «ActivityPartition,» Semantics topic.

Copy [1] A Copy dependency may only be created between two classes that have the «requirement»stereotype, or a subtype of the «requirement» stereotype applied.
Copy [2] The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement.

DeriveReqt [1] The supplier must be an element stereotyped by «requirement» or one of «requirement» subtypes.
DeriveReqt [2] The client must be an element stereotyped by «requirement» or one of «requirement» subtypes.

Refine [1] The Refine stereotype may only be applied to dependencies.
Refine [2] Dependencies with a Refine stereotype or one of its specializations applied must have exactly one client and one supplier.

Requirement [1] The property «ownedOperation» must be empty.
Requirement [2] The property «ownedAttribute» must be empty.
Requirement [3] Classes stereotyped by  «requirement» may not participate in associations.
Requirement [4] Classes stereotyped by  «requirement» may not participate in generalizations.
Requirement [5] A nested classifier of a class stereotyped by «requirement» must also be stereotyped by «requirement».
Requirement [6] Classes stereotyped by «requirement» may not be used to type any other model element.

TestCase [1] The type of return parameter of the stereotyped model element must be VerdictKind.

Satisfy [1] The supplier must be an element stereotyped by «requirement» or one of «requirement» subtypes.

Trace [1] The Trace stereotype may only be applied to dependencies.
Trace [2] Dependencies with a Trace stereotype or one of its specializations applied must have exactly one client and one supplier.

Verify [1] The supplier must be an element stereotyped by «requirement» or one of «requirement» subtypes.