Validation Rules
Generated from the sysml-rs language pack — see the Language Reference index for provenance, licensing, and the raw JSON. 76 cards.
At Most One Return Parameter
KerML — kerml.validation.at-most-one-return-parameter
A function can have at most one return parameter
Normative clauses: KerML §8.3.4.7.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Function
Behavior Not Specialize Structure
KerML — kerml.validation.behavior-not-specialize-structure
A behavior cannot specialize a structure
Normative clauses: KerML §8.3.4.6.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Behavior
Binary Connector Two Ends
KerML — kerml.validation.binary-connector-two-ends
A binary connector must have exactly two end features
Normative clauses: KerML §8.3.4.5.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Binding Connector Two Ends
KerML — kerml.validation.binding-connector-two-ends
A binding connector must have exactly two end features
Normative clauses: KerML §8.3.4.5.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Class Not Specialize Datatype
KerML — kerml.validation.class-not-specialize-datatype
A class cannot specialize a data type or association
Normative clauses: KerML §8.3.4.2.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Class
Connector Owned By Type
KerML — kerml.validation.connector-owned-by-type
A connection must be owned by a type (part, action, etc.), not a package
Normative clauses: KerML §8.3.4.5.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Connection Usage, Flow Connection, Interface Usage
Datatype Not Specialize Class
KerML — kerml.validation.datatype-not-specialize-class
A data type cannot specialize a class or association
Normative clauses: KerML §8.3.4.1.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Data Type
Model Element Must Be Owned
KerML — kerml.validation.model-element-must-be-owned
Every non-root model element is owned by (a member of) a namespace; a bare top-level usage/def that is not a package is an orphan.
Normative clauses: KerML §8.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
No Inherited Name Conflict
KerML — kerml.validation.no-inherited-name-conflict
Member name ‘{name}’ conflicts with inherited member
Normative clauses: KerML §8.3.2.4.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Namespace
No Name Alias Conflict
KerML — kerml.validation.no-name-alias-conflict
Member name ‘{name}’ duplicates an alias
Normative clauses: KerML §8.3.2.4.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Namespace
Parameter Membership Owning Type
KerML — kerml.validation.parameter-membership-owning-type
Parameter membership is only allowed in behaviors and steps
Normative clauses: KerML §8.3.4.6.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Result Expression In Function Or Expression
KerML — kerml.validation.result-expression-in-function-or-expression
Result expression membership is only allowed in functions and expressions
Normative clauses: KerML §8.3.4.7.7
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Return Parameter Membership Owning Type
KerML — kerml.validation.return-parameter-membership-owning-type
Return parameter membership is only allowed in functions and expressions
Normative clauses: KerML §8.3.4.7.8
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Structure Not Specialize Behavior
KerML — kerml.validation.structure-not-specialize-behavior
A structure cannot specialize a behavior
Normative clauses: KerML §8.3.4.3.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Structure
Succession Two Ends
KerML — kerml.validation.succession-two-ends
A succession must have exactly two end features
Normative clauses: KerML §8.3.4.5.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Unique Owned Member Names
KerML — kerml.validation.unique-owned-member-names
Duplicate owned member name ‘{name}’
Normative clauses: KerML §8.3.2.4.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Namespace
Accept Action Has Payload
SysML — sysml.validation.accept-action-has-payload
An accept action must have a payload parameter
Normative clauses: SysML §8.3.17.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Accept Action
Action Typed By Behavior
SysML — sysml.validation.action-typed-by-behavior
An action must be typed by action definitions
Normative clauses: SysML §8.3.17.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Action Usage
Actor Membership In Req Or Case
SysML — sysml.validation.actor-membership-in-req-or-case
Only requirements and cases can have actors
Normative clauses: SysML §8.3.21.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Actor
Allocation Has Ends
SysML — sysml.validation.allocation-has-ends
An allocation must have at least two end features
Normative clauses: SysML §8.3.15.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Allocation Usage
Allocation Typed By Allocation Defs
SysML — sysml.validation.allocation-typed-by-allocation-defs
An allocation must be typed by allocation definitions
Normative clauses: SysML §8.3.15.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Allocation Usage
Analysis Case At Most One Subject
SysML — sysml.validation.analysis-case-at-most-one-subject
An analysis case can have at most one subject
Normative clauses: SysML §8.3.23.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Analysis Case, Analysis Case Definition
Assignment Action Has Target
SysML — sysml.validation.assignment-action-has-target
An assignment action must have a target feature
Normative clauses: SysML §8.3.17.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Assignment Action
At Most One Objective
SysML — sysml.validation.at-most-one-objective
A case definition can have at most one objective
Normative clauses: SysML §8.3.22.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Case Definition, Case Usage
At Most One State Subaction
SysML — sysml.validation.at-most-one-state-subaction
A state definition may have at most one entry, one do, and one exit action
Normative clauses: SysML §8.3.18.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: State Definition, State Usage
At Most One Subject
SysML — sysml.validation.at-most-one-subject
A requirement definition can have at most one subject
Normative clauses: SysML §8.3.21.8
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Case Definition, Case Usage, Requirement Definition, Requirement Usage
At Most One View Rendering
SysML — sysml.validation.at-most-one-view-rendering
A view definition may have at most one view rendering
Normative clauses: SysML §8.3.26.7
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: View Definition, View Usage
Attribute Def Not Specialize Item Def
SysML — sysml.validation.attribute-def-not-specialize-item-def
An attribute definition cannot specialize an item definition
Normative clauses: SysML §8.3.7.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Attribute Definition
Attribute Must Not Be Composite
SysML — sysml.validation.attribute-must-not-be-composite
An AttributeUsage must not be composite
Normative clauses: SysML §8.3.7.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Attribute Definition, Attribute Usage
Attribute Typed By Datatypes
SysML — sysml.validation.attribute-typed-by-datatypes
An attribute must be typed by attribute definitions
Normative clauses: SysML §8.3.7.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Attribute Usage
Calculation Typed By One Calc Def
SysML — sysml.validation.calculation-typed-by-one-calc-def
A calculation must be typed by one calculation definition
Normative clauses: SysML §8.3.19.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Calculation Usage
Case Typed By One Case Def
SysML — sysml.validation.case-typed-by-one-case-def
A case must be typed by one case definition
Normative clauses: SysML §8.3.22.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Case Usage
Concern At Most One Subject
SysML — sysml.validation.concern-at-most-one-subject
A concern can have at most one subject
Normative clauses: SysML §8.3.21.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Concern Definition, Concern Usage
Connection Has Ends
SysML — sysml.validation.connection-has-ends
A connection must have at least two end features
Normative clauses: SysML §8.3.13.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Connection Usage
Connection Typed By Association
SysML — sysml.validation.connection-typed-by-association
A connection must be typed by connection definitions
Normative clauses: SysML §8.3.13.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Connection Usage
Constraint Typed By Predicate
SysML — sysml.validation.constraint-typed-by-predicate
A constraint must be typed by one constraint definition
Normative clauses: SysML §8.3.20.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Constraint Usage
Decision Node One Incoming
SysML — sysml.validation.decision-node-one-incoming
A decision node must have at most one incoming succession
Normative clauses: SysML §8.3.17.7
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Decision Node
Enumeration Typed By One Enum Def
SysML — sysml.validation.enumeration-typed-by-one-enum-def
An enumeration must be typed by one enumeration definition
Normative clauses: SysML §8.3.8.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Enumeration Usage
Exhibit State One Type
SysML — sysml.validation.exhibit-state-one-type
An exhibit state must be typed by exactly one state definition
Normative clauses: SysML §8.3.18.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Exhibit State Usage
Flow Typed By Interaction
SysML — sysml.validation.flow-typed-by-interaction
A flow connection must be typed by flow connection definitions
Normative clauses: SysML §8.3.16.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Flow Connection
Fork Node One Incoming
SysML — sysml.validation.fork-node-one-incoming
A fork node must have at most one incoming succession
Normative clauses: SysML §8.3.17.8
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Fork Node
Interface Has Ends
SysML — sysml.validation.interface-has-ends
An interface must have at least two end features
Normative clauses: SysML §8.3.14.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Interface Usage
Interface Typed By Interface Defs
SysML — sysml.validation.interface-typed-by-interface-defs
An interface must be typed by interface definitions
Normative clauses: SysML §8.3.14.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Interface Usage
Item Def Not Specialize Attribute Def
SysML — sysml.validation.item-def-not-specialize-attribute-def
An item definition cannot specialize an attribute definition
Normative clauses: SysML §8.3.10.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Item Definition
Item Typed By Item Defs
SysML — sysml.validation.item-typed-by-item-defs
An item must be typed by item definitions
Normative clauses: SysML §8.3.10.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Item Usage
Join Node One Outgoing
SysML — sysml.validation.join-node-one-outgoing
A join node must have at most one outgoing succession
Normative clauses: SysML §8.3.17.11
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Join Node
Merge Node One Outgoing
SysML — sysml.validation.merge-node-one-outgoing
A merge node must have at most one outgoing succession
Normative clauses: SysML §8.3.17.13
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Merge Node
Objective Membership In Case
SysML — sysml.validation.objective-membership-in-case
Only cases can have objectives
Normative clauses: SysML §8.3.22.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Objective
Occurrence Typed By Occurrence Defs
SysML — sysml.validation.occurrence-typed-by-occurrence-defs
An occurrence must be typed by occurrence definitions
Normative clauses: SysML §8.3.9.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Occurrence Usage
Parallel State No Transitions
SysML — sysml.validation.parallel-state-no-transitions
A parallel state cannot have transitions
Normative clauses: SysML §8.3.18.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: State Definition, State Usage
Part Typed By Part Defs
SysML — sysml.validation.part-typed-by-part-defs
A part must be typed by at least one part definition
Normative clauses: SysML §8.3.11.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Part Usage
Perform Action One Type
SysML — sysml.validation.perform-action-one-type
A perform action must be typed by exactly one action definition
Normative clauses: SysML §8.3.17.14
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Perform Action
Port Definition Owned Usages Referential
SysML — sysml.validation.port-definition-owned-usages-referential
The non-port owned usages of a port definition must be referential (non-composite)
Normative clauses: SysML §8.3.12.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Port Definition
Port Typed By Port Defs
SysML — sysml.validation.port-typed-by-port-defs
A port must be typed by port definitions
Normative clauses: SysML §8.3.12.6
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Port Usage
Port Usage Nested Usages Referential
SysML — sysml.validation.port-usage-nested-usages-referential
The non-port nested usages of a port usage must be referential (non-composite)
Normative clauses: SysML §8.3.12.6
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Port Usage
Requirement Constraint In Requirement
SysML — sysml.validation.requirement-constraint-in-requirement
Only requirements can have assumed or required constraints
Normative clauses: SysML §8.3.21.7
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Requirement Constraint (assume / require)
Requirement Constraints Composite
SysML — sysml.validation.requirement-constraints-composite
Assumed constraints must be composite
Normative clauses: SysML §8.3.21.8
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Requirement Definition, Requirement Usage
Requirement Typed By One Req Def
SysML — sysml.validation.requirement-typed-by-one-req-def
A requirement must be typed by one requirement definition
Normative clauses: SysML §8.3.21.9
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Requirement Usage
Satisfy Req One Type
SysML — sysml.validation.satisfy-req-one-type
A satisfy requirement must be typed by one requirement definition
Normative clauses: SysML §8.3.21.10
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Requirement Satisfaction
Send Action Has Payload
SysML — sysml.validation.send-action-has-payload
A send action must have a payload parameter
Normative clauses: SysML §8.3.17.15
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Send Action
Stakeholder Membership In Requirement
SysML — sysml.validation.stakeholder-membership-in-requirement
Only requirements can have stakeholders
Normative clauses: SysML §8.3.21.12
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Stakeholder
State Subaction Owned By State
SysML — sysml.validation.state-subaction-owned-by-state
Entry, do, and exit actions can only appear in state definitions or usages
Normative clauses: SysML §8.3.18.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
State Typed By State Defs
SysML — sysml.validation.state-typed-by-state-defs
A state must be typed by state definitions
Normative clauses: SysML §8.3.18.6
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: State Usage
Subject Is First Parameter
SysML — sysml.validation.subject-is-first-parameter
The subject must be the first parameter (input) of a requirement definition
Normative clauses: SysML §8.3.21.8
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Case Definition, Case Usage, Requirement Definition, Requirement Usage
Subject Membership In Req Or Case
SysML — sysml.validation.subject-membership-in-req-or-case
Only requirements and cases can have subjects
Normative clauses: SysML §8.3.21.11
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Subject
Transition Feature In Transition
SysML — sysml.validation.transition-feature-in-transition
Transition feature membership is only allowed in transitions
Normative clauses: SysML §8.3.18.8
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Transition Has Source
SysML — sysml.validation.transition-has-source
A transition must have a source
Normative clauses: SysML §8.3.18.9
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Transition Usage
Transition Owned By State Or Action
SysML — sysml.validation.transition-owned-by-state-or-action
A transition must be owned by a state or an action
Normative clauses: SysML §8.3.18.9
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Transition Usage
Usage Typed By Definitions
SysML — sysml.validation.usage-typed-by-definitions
A usage must be typed by definitions
Normative clauses: SysML §8.3.6.4
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Use Case At Most One Subject
SysML — sysml.validation.use-case-at-most-one-subject
A use case can have at most one subject
Normative clauses: SysML §8.3.25.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Use Case Definition, Use Case Usage
Variant Membership In Variation
SysML — sysml.validation.variant-membership-in-variation
A variant must be an owned member of a variation
Normative clauses: SysML §8.3.6.5
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Variation Members Are Variants
SysML — sysml.validation.variation-members-are-variants
An owned usage of a variation must be a variant
Normative clauses: SysML §8.3.6.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Variation Must Be Abstract
SysML — sysml.validation.variation-must-be-abstract
A variation definition must be abstract
Normative clauses: SysML §8.3.6.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Variation No Chain
SysML — sysml.validation.variation-no-chain
A variation must not specialize another variation
Normative clauses: SysML §8.3.6.2
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Verification Case At Most One Subject
SysML — sysml.validation.verification-case-at-most-one-subject
A verification case can have at most one subject
Normative clauses: SysML §8.3.24.3
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown
Related: Verification Case, Verification Case Definition
View Rendering In View
SysML — sysml.validation.view-rendering-in-view
Only views can have view renderings
Normative clauses: SysML §8.3.26.10
Support (sysml-rs): parse unknown · resolve unknown · elaborate unknown · execute unknown