UMLModelio¶
ModelioR1010¶
The top Partitions of an Activity must not have a Super-Partition.
| paquetage: | UMLModelio |
|---|
ModelioR1020¶
The source and the target of a Flow must be contained in the same Structured Activity Node.
| paquetage: | UMLModelio |
|---|
ModelioR1030¶
The source and the target of a Flow must be owned by the same Activity.
| paquetage: | UMLModelio |
|---|
ModelioR1040¶
An Activity Parameter Node must be represeneted by a Behavior Parameter owned by the same Activity.
| paquetage: | UMLModelio |
|---|
ModelioR1050¶
An Activity Parameter Node cannot have both incoming and outgoing edges.
| paquetage: | UMLModelio |
|---|
ModelioR1060¶
Activity Parameter Nodes with no incoming flow and one or more outgoing flow must have a Behavior Parameter with “In” or “In/Out” parameter passing mode.
| paquetage: | UMLModelio |
|---|
ModelioR1070¶
Activity Parameter Nodes with no outgoing flow and one or more incoming flow must have a Behavior Parameter with “Out” or “In/Out” parameter passing mode.
| paquetage: | UMLModelio |
|---|
ModelioR1080¶
All Partitions of the same nesting level must represent Parts of the same Classifier.
| paquetage: | UMLModelio |
|---|
ModelioR1090¶
If a Sub-Partition is non-external and represents a Classifier then the represented Classifier must be nested in the Classifier represented by its Super-Partition or be the extremity of a Composition with the latter.
| paquetage: | UMLModelio |
|---|
ModelioR1100¶
If a Sub-Partition represents a Part nested in a Classifier then its Super-Partition must represent the Classifier or an instance of the latter.
| paquetage: | UMLModelio |
|---|
ModelioR1110¶
There must be one to one correspondence between: (A) the Pins of a Call Behavior Action, and (B) the In, Out, InOut or Return Behavior Parameters of the called Behaviour.
| paquetage: | UMLModelio |
|---|
ModelioR1130¶
The type and the maximum cardinality of a Call Action’’s Pin must match the type and max multiplicity of the represented Parameter.
| paquetage: | UMLModelio |
|---|
ModelioR1140¶
There must be one to one correspondence between: (A) the Pins of a Call Operation Action, and (B) the In, Inout, Out and Return parameters of the called Operation.
| paquetage: | UMLModelio |
|---|
ModelioR1150¶
The Call Operation Action or Send Signal Action has more than one target Pin.
| paquetage: | UMLModelio |
|---|
ModelioR1160¶
A target Pin can only be owned by Call Operation Actions and Send Signal Actions
| paquetage: | UMLModelio |
|---|
ModelioR1170¶
The type of the target Pin must be the same as the type that owns the Operation.
| paquetage: | UMLModelio |
|---|
ModelioR1180¶
Control Flows may not have Object Nodes at either end, except for Object Nodes with control type.
| paquetage: | UMLModelio |
|---|
ModelioR1190¶
The Decision-Merge Node is used both as a Decision node and as a Merge node at the same time.
| paquetage: | UMLModelio |
|---|
ModelioR1200¶
The edges coming into and out of a Decision Merge Node must be either all Object Flows or all Control Flows.
| paquetage: | UMLModelio |
|---|
ModelioR1250¶
If a Fork/Join Node has an Object Flow in its incoming edges, it must have an Object Flow in its outgoing edges and vice versa. The same applies for Control Flows.
| paquetage: | UMLModelio |
|---|
ModelioR1290¶
Object Nodes connected by an Object Flow, with optionally intervening control nodes, must have compatible types. In particular, the downstream Object Node type must be the same or a super type of the upstream Object Node type.
| paquetage: | UMLModelio |
|---|
ModelioR1300¶
Object Nodes connected by an Object Flow, with optionally intervening control nodes, must have the same upper bounds.
| paquetage: | UMLModelio |
|---|
ModelioR1310¶
An edge with constant weight may not target an Object Node, or lead to an Object Node downstream with no intervening actions and with an upper bound less than the weight.
| paquetage: | UMLModelio |
|---|
ModelioR1320¶
An Object Flow must not be simultaneusly multi-cast and multi-receive.
| paquetage: | UMLModelio |
|---|
ModelioR1350¶
If an Object Node has a ‘’Selection behavior’‘, then the ’‘Ordering’‘ of the Object Node is ordered and vice versa.
| paquetage: | UMLModelio |
|---|
ModelioR1360¶
Input Pins may have outgoing edges only when both the following conditions are met: (1) they are on Actions that are Structured Nodes, and (2) these edges must target a Node contained by the Structured Node.
| paquetage: | UMLModelio |
|---|
ModelioR1370¶
Output Pins may have incoming edges only when both the following conditions are met: (1) they are on Actions that are Structured Nodes, and (2) these edges must come from a node contained by the Structured Node.
| paquetage: | UMLModelio |
|---|
ModelioR1380¶
There must be one to one correspondence between: (A) the Pins of a Send Signal Action, and (B) the attributes of the sent Signal.
| paquetage: | UMLModelio |
|---|
ModelioR1390¶
The max cardinality of an argument Pin must be the same as for the represented Attribute.
| paquetage: | UMLModelio |
|---|
ModelioR1410¶
Only one Association End of an Association can be aggregate or composite.
| paquetage: | UMLModelio |
|---|
ModelioR1430¶
Multiplicities of an AssociationEnd must be consistent: MultiplicityMin cannot be ‘*’ and MultiplicityMin must be inferior to MultiplicityMax.
| paquetage: | UMLModelio |
|---|
ModelioR1450¶
If an association is a composition, then the opposite maximum multiplicity must be 1.
| paquetage: | UMLModelio |
|---|
ModelioR1460¶
A public association oriented from a public Classifier cannot be linked to a private or protected Classifier.
| paquetage: | UMLModelio |
|---|
ModelioR1490¶
In an instance, the type of an instantiated attribute must be in the instantiated class or in its parent classes.
| paquetage: | UMLModelio |
|---|
ModelioR1500¶
In an instance, the name of an instantiated attribute must be the same as the corresponding attribute.
| paquetage: | UMLModelio |
|---|
ModelioR1540¶
A BindableInstance’s RepresentedFeature must not refer itself, directly or indirectly.
| paquetage: | UMLModelio |
|---|
ModelioR1550¶
If a BinbdableInstance has a type and has a represented feature, the type of the instance must be compatible with the type of this feature.
| paquetage: | UMLModelio |
|---|
ModelioR1580¶
Attributes, Associations and Operations cannot simultaneously be abstract and class.
| paquetage: | UMLModelio |
|---|
ModelioR1640¶
A maximum of one ElementImport must exist between a NameSpace and another NameSpace or between an Operation and a NameSpace.
| paquetage: | UMLModelio |
|---|
ModelioR1670¶
EnumlerationLitteral defined in an Enumeration must have an unique name.
| paquetage: | UMLModelio |
|---|
ModelioR1680¶
For a Call-type Event, the ‘Called operation’ field must be defined, whereas the ‘Instanciated signal’ must be empty.
| paquetage: | UMLModelio |
|---|
ModelioR1690¶
The ‘Expression’ field for a Change-type Event must be defined, whereas the ‘Called operation’ and ‘Instanciated signal’ fields must be empty.
| paquetage: | UMLModelio |
|---|
ModelioR1700¶
The ‘Instantiated signal’ field for a signal-type Event must be defined, whereas the ‘Called operation’ and ‘Expression’ fields must be empty.
| paquetage: | UMLModelio |
|---|
ModelioR1710¶
The ‘Expression’ field for a Time-type Event must be defined, whereas the ‘Called operation’ and ‘Instanciated signal’ fields must be empty.
| paquetage: | UMLModelio |
|---|
ModelioR1720¶
An abstract NameSpace should only inherit from an abstract NameSpace.
| paquetage: | UMLModelio |
|---|
ModelioR1730¶
A generalisation must be created between two model elements of the same type, except in the case of a signal, which can specialize a Signal or a Class.
| paquetage: | UMLModelio |
|---|
ModelioR1760¶
There cannot be inconsistency in the multiplicities of an Instance
| paquetage: | UMLModelio |
|---|
ModelioR1790¶
An instance must have a name, or the instantiation association must be defined.
| paquetage: | UMLModelio |
|---|
ModelioR1800¶
If an Operator is of type opt, loop, break or neg, there cannot be more than one Operand.
| paquetage: | UMLModelio |
|---|
ModelioR1810¶
An actual Gate on an InteractionUse must reference a formal Gate contained by the referenced Interaction.
| paquetage: | UMLModelio |
|---|
ModelioR1830¶
A PartDecomposition cannot receive ‘create’ or ‘destroy’ messages.
| paquetage: | UMLModelio |
|---|
ModelioR1870¶
An interface cannot be implemented twice by the same class or the same component.
| paquetage: | UMLModelio |
|---|
ModelioR1910¶
A Link that instantiates an association must be coherent with this association.
| paquetage: | UMLModelio |
|---|
ModelioR1970¶
A TemplateParameterSubstitution must reference a TemplateParameter.
| paquetage: | UMLModelio |
|---|
ModelioR1980¶
The names of a Classifier’s Attributes and AssociationEnds must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR1990¶
The name of a Classifier’s inherited Attributes and Roles must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR2030¶
In a PropertyContainer, the name of each EnumerationPropertyType must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR2100¶
In a EnumerationPropertyType, the name of each PropertyEnumerationLiteral must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR2120¶
In a PropertyContainer, the name of each PropertySet must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR2140¶
In a PropertyContainer, the name of each PropertyType must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR2160¶
In an Analyst Container, the name of each element must be unique.
| paquetage: | UMLModelio |
|---|
ModelioR2190¶
A maximum of one generalization may exist between two namespaces.
| paquetage: | UMLModelio |
|---|
ModelioR2250¶
All operations in a Classifier must have a different signature from inherited public and protected operations. Except for constructor, destructor and redefined operations.
| paquetage: | UMLModelio |
|---|
ModelioR2340¶
A redefined Operation must belong to a parent or an implemented Interface of the owner of the Operation.
| paquetage: | UMLModelio |
|---|
ModelioR2360¶
The visibility of an Operation cannot be greater than that of the Operations it redefines.
| paquetage: | UMLModelio |
|---|
ModelioR2420¶
An Operation must have the same signature as the Operation it redefines.
| paquetage: | UMLModelio |
|---|
ModelioR2470¶
A maximum of one PackageImport link may exist between a NameSpace and a Package.
| paquetage: | UMLModelio |
|---|
ModelioR2520¶
If a Port runs a delegation towards an internal part, it must provide at least one interface.
| paquetage: | UMLModelio |
|---|
ModelioR2530¶
If a Port receives a delegation from an internal part, it must provide at least one interface.
| paquetage: | UMLModelio |
|---|
ModelioR2540¶
The interfaces provided by a port must be implemented by the Class that types the Port.
| paquetage: | UMLModelio |
|---|
ModelioR2550¶
If a Port is a behavior port, its provided interfaces must be implemented by the Class it belongs to.
| paquetage: | UMLModelio |
|---|
ModelioR2570¶
If a Port is a behavior port, the type of the port must be either the Class it belongs to or undefined.
| paquetage: | UMLModelio |
|---|
ModelioR2600¶
A state machine or a state cannot have two states with the same name.
| paquetage: | UMLModelio |
|---|
ModelioR2620¶
Submachine states should not have entry or exit pseudo states defined.
| paquetage: | UMLModelio |
|---|
ModelioR2660¶
A state in a protocol state machine cannot have entry, exit, or do activity actions.
| paquetage: | UMLModelio |
|---|
ModelioR2680¶
The number of parameter of a TaggedValue must be the same as the number of parameter defined in the TaggedValue declaration.
| paquetage: | UMLModelio |
|---|
ModelioR2700¶
A TemplateBinding can only substitute each TemplateParameter of the instantiated element once.
| paquetage: | UMLModelio |
|---|
ModelioR2720¶
A TemplateBinding must be created between two elements of the same type or between a Class and a DataType.
| paquetage: | UMLModelio |
|---|
ModelioR2730¶
A TemplateBinding must substitute all the TemplateParameters of the instanciated template element, and the TemplateParameterSubstitution must be defines in the same order as the TemplateParameters.
| paquetage: | UMLModelio |
|---|
ModelioR2740¶
In a TemplateBinding, the TemplateParameterSubstitution must belong to the instantiated template element.
| paquetage: | UMLModelio |
|---|
ModelioR2750¶
A transition from a fork or join pseudo state should not have guards or triggers.
| paquetage: | UMLModelio |
|---|
ModelioR2780¶
Transitions outgoing pseudostates may not have a trigger (except for those coming out of the initial pseudostate).
| paquetage: | UMLModelio |
|---|
ModelioR2790¶
A transition from one region to another in the same immediate enclosing composite state is not allowed.
| paquetage: | UMLModelio |
|---|
ModelioR2840¶
A transition should have only one of Processed, Effects, or BehaviorEffet defined.
| paquetage: | UMLModelio |
|---|
ModelioR2870¶
There must be no cycle in use cases << extend >> dependency graph.
| paquetage: | UMLModelio |
|---|
ModelioR2880¶
There must be no cycle in use cases << include >> dependency graph.
| paquetage: | UMLModelio |
|---|
ModelioR2890¶
A communication link cannot have the same actor or use case as its source and target.
| paquetage: | UMLModelio |
|---|
ModelioR2900¶
An << extend >> use case dependency must reference at least one extension point.
| paquetage: | UMLModelio |
|---|
ModelioR2910¶
An << extend >> use case dependency can only reference the target’s extension points.
| paquetage: | UMLModelio |
|---|
ModelioR2920¶
Extension points can only be referenced by an << extend >> use case dependency.
| paquetage: | UMLModelio |
|---|
ModelioR2930¶
Message and CommunicationMessage cannot have both Signal and Operation properties defined.
| paquetage: | UMLModelio |
|---|
ModelioR2940¶
All transitions incoming a join vertex must originate in different regions of an orthogonal state.
| paquetage: | UMLModelio |
|---|
ModelioR2950¶
All transitions outgoing a fork vertex must target states in different regions of an orthogonal state.
| paquetage: | UMLModelio |
|---|
ModelioR2960¶
Synonym, antonym, homonym, context, and kind-of dependencies can only link two terms.
| paquetage: | UMLModelio |
|---|
ModelioR2970¶
An Assigned dependency must be from an Actor, an Interface, a Package, or a Process, toward a Goal.
| paquetage: | UMLModelio |
|---|
ModelioR3000¶
Positive influence and Negative influence dependencies must be between two Goals.
| paquetage: | UMLModelio |
|---|
ModelioR3020¶
A related dependency must be must be between two Business Rules or two Terms.
| paquetage: | UMLModelio |
|---|
ModelioR3030¶
A refine dependency must be between either: 1) from a Model Element or a Requirement towards a Requirement 2) from a Business Rule, an Activity or an Operation towards a Business Rule.
| paquetage: | UMLModelio |
|---|
ModelioR3040¶
An implement dependency must be from a Process or a Class towards a Business Rule.
| paquetage: | UMLModelio |
|---|
ModelioR3050¶
A part dependency must be between two Requirements or between two Goals.
| paquetage: | UMLModelio |
|---|
ModelioR3060¶
A satisfy or verify dependency must be from a ModelElement towards a Requirement.
| paquetage: | UMLModelio |
|---|
ModelioR3070¶
A derive dependency must be from a UseCase or a Requirement towards a Requirement.
| paquetage: | UMLModelio |
|---|
ModelioR3080¶
All FlowNodes should be part of a sequence starting with a StartEvent and finishing with an EndEvent.
| paquetage: | UMLModelio |
|---|
ModelioR3090¶
A SequenceFlow cannot have its source or target in different Pools.
| paquetage: | UMLModelio |
|---|
ModelioR3100¶
A SequcneFlow in a SubProcess must have its origin and target in the same SubProcess.
| paquetage: | UMLModelio |
|---|
ModelioR3110¶
A SequenceFlow cannot target a StartEvent nor have an EndEvent as its source.
| paquetage: | UMLModelio |
|---|
ModelioR3130¶
A MessageFlow cannot target a StartEvent or an IntermediateThrowEvent, nor have an EndEvent or an IntermediateCatchEvent as its source.
| paquetage: | UMLModelio |
|---|
ModelioR3140¶
All outgoing SequenceFlow from an EventBasedGateway or a ParallelGateway must have its guard properties empty.
| paquetage: | UMLModelio |
|---|
ModelioR3170¶
Inclusive Gateway,Complex Gateway and Parallel Gateway must have at least two outgoing Sequence Flows.
| paquetage: | UMLModelio |
|---|
ModelioR3180¶
A FlowElement (and respectively a BaseElement) cannot have a SequenceFlow (respectively a MessageFlow) towards itself.
| paquetage: | UMLModelio |
|---|
ModelioR3190¶
A DataAssociation cannot target a DataInput nor have a DataOutput as its source.
| paquetage: | UMLModelio |
|---|
ModelioR3220¶
A SequenceFlow outgoing from an EventBasedGateway must target an IntermediaryCatchEvent.
| paquetage: | UMLModelio |
|---|
ModelioR3230¶
All SequenceFlows outgoing from an ExclusiveGateway must have a guard, except for the default SequenceFlow.
| paquetage: | UMLModelio |
|---|
ModelioR3240¶
There can only be one sequence in a Process, a SubProcess or a Pool.
| paquetage: | UMLModelio |
|---|
ModelioR3250¶
A Process, a SubProcess, or a Pool should have at least one StartEvent and one EndEvent.
| paquetage: | UMLModelio |
|---|