Overview of Modeling Verification Messages

AcceptEventActions may have no input pins.

Finds elements which are part of an existence prerequisite cycle. An existence prerequisite cycle of entities is built by mandatory relationships or generalizations.

Finds elements which are part of an existence prerequisite cycle. An existence prerequisite cycle of DB tables is build by not null foreign keys.

The structure is checked for the configured relationships. If a relationship was not configured, a message appears. Non-configurable relationships are ignored. The set filter is also checked here. For troubleshooting either the documentation structure or the configuration of relationships needs customizations. The used filter has to be corrected.

The structure is checked for the configured relationships. If a relationship was not configured, a message appears. Non-configurable relationships are ignored. For troubleshooting either the documentation structure or the configuration of relationships needs customizations.

File extensions may be configured for stereotypes of artifacts.

At composite structure diagrams attributes are shown as part nodes within structured classifier or part nodes. These attributes have to be reachable for the surrounding classifier or the classifier type of the surrounding attribute.

In deployment diagrams the nesting of nodes within a node should represent a owner relationship.

The configuration of display options may contain invalid values. These might be invalid stereotypes within rules or values of properties. Values can become invalid if the structure of stereotypes or their configured relations are changed.

If a verification routine is called from a selected diagram in the model browser and a message appears for this diagram, the following occurs: instead of all messages appearing, only 'Is inconsistent' appears. If you then click on the message, you jump to the diagram, it is opened and the verification routine is then run in the diagram. All messages which lead to inconsistencies then appear in the diagram. Therefore it is necessary that a verification routine which will cause a message within the model browser exists as menu command within the diagram editor, too.

A maximum file size may be specified for each configured file extension.

isUnmarshall must be true for an AcceptCallAction.

It is not possible to calculate the foreign key side for a 1:1 relationship.

A dimension may not be contained by another partition.

Ad-Hoc subprocesses may not own start or end events.

Associations with role multiplicity '1..1' lead to problems during mapping to data models because it is not possible to calculate the foreign key side.

Verifies that the tokens in the object node are ordered for selection if a selection behavior assigned to this object node.

In deployment diagrams the nesting of artifacts within a node should represent a deployment.

The connected instance specifications of a link specify a combination of classifiers. These classifiers may have different associations. The association of the link must be from this set of associations.

The task has at least one data input/output which is not connected to another data object via a data association.

A parameter set may not be empty.

A decision input behavior has zero or one input parameters and one output parameter. Any input parameter must be the same as or a supertype of the type of object tokens coming along the incoming edge.

The behavior of the behavior execution specification is not available.

The behavior execution specification has no behavior.

The documentation structure is searched for chapters that require a filter but don' t have one set yet.

In composite structure diagrams the nesting of classifiers within a component should represent a component realization.

A non-abstract stereotype may only be used for an element if all preconditions are configured as relationship roles. The stereotypes are owned by one profile but the relationship roles may be owned by any other profile. The specified relationship role should be configured or the stereotype deleted to fix this problem. Deleting of root stereotypes is not possible.

A non-abstract stereotype may only be used for an element if all preconditions are configured as relationship roles. Some element types have special constraints which may lead to additional messages. Some relationship roles have to be configured to fix this problem.

All menus included are checked to see whether they have at least one menu command. If a menu doesn't have a menu command, it is selected. Empty menus are not available in any interfaces and are, therefore, superfluous. For troubleshooting delete empty menu or assign menu commands.

A classifier which contains abstract operations should be abstract, too.

This foreign key references a key in another model.

This from clause references an attribute set in another model.

This from clause references a column set in another model.

The entities of this generalization are not part of the same model.

The entities of this relationship are not part of the same model.

This property is assigned to a type of another model.

The data store reference and its assigned data store have ambigous business objects.

There is no data store definition assigned to this data store reference.

The classifier of the instance owning the slot must contain the defining feature directly as owned element or by inheritance. For troubleshooting the slot has to be deleted or the defining feature must be reachable.

A slot may only have values if the defining feature has a valid type. Valid types are enumerations, classifiers or primitive types with specified kind of type. Modifications for the defining feature or the used type lead to a correction of the used values.

At diagrams the local defined display options are checked. Within the Edit/Display Options dialog all display options with errors are delivered in the Verify Messages tab (or root tab for elements which are similar to diagrams); these can then be jumped to using an icon.

The configured display options are checked for the stereotypes of diagrams. If this produces a verification message, the stereotype is selected within the current profile. The profile is listed as name. For troubleshooting select the stereotype and open the Edit/Display Options dialog box. All display options with errors are delivered in the Verify Messages tab (or root tab for elements which are similar to diagrams); these can then be jumped to using an icon.

There should be either further groups nested in the group or it should contain nodes and edges.

An exception handler must have at least one exception type.

Verifies if the interruptible activity region does have at least one activity edge considered to be an interrupting edge. It does not verify if the activity edge does fulfill all requirements of an interrupting edge.

The node must have exactly one incoming edge.

The node must have exactly one outgoing edge.

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 supertype of the upstream object node type.

During the configuration elements of different profiles are used. For example a stereotype is used as base for a create template which is used as menu command. It has to be ensured, that all used elements are reachable by imports of their profiles.

The valid content of diagrams is restricted by the configuration of relationship roles. By version import, modification of the owner or the modification of the configuration the display diagram content may be invalid.

All elements which are represented as lifeline at an interaction use should be represented as lifeline at this interaction, too.

Generalizations are transitive. A direct generalization from one classifier to another is superfluous, if a transitive generalization leads to the same classifier.

This model element was created by a mapping action but the requirement element no longer exists. If you decided to keep this element for other reasons, you should reset the property 'Created by Mapping'.

This element has no mapping implementation.

The entity contains no attributes.

The entity contains no primary key.

The entity does not participate in a relationship or a generalization.

The compartments of classifier nodes show in most cases contained elements. These contents are always maintained correctly. For other compartment (e.g. realized and used interfaces, artifacts and realizations) the displayed contents depend on additional conditions. Depending on the complexity of these conditions it is not possible to maintain these contents always correctly. Invalid contents have to be corrected manually.

The entry point of the sub state machine should be use within this state.

All literals of an enumeration type may have an enumeration value. These values have to be unique for all literals owned by the same enumeration.

Exactly one link-end data specification (the 'open end') must not have an end object input pin.

If the deployment target of a deployment is an execution environment the deployed artifact should have manifestations only of components.

The exit point of the sub state machine should be use within this state.

The expression contains '??'. Probably a used feature has been deleted and the expression is not proper any more.

'AddStructuralFeatureValue' actions adding a value to ordered structural features must have a single input pin for the insertion point, otherwise the action has no input pin for the insertion point.

Actions removing a value from ordered nonunique structural features must have a single removeAt input pin if 'Remove Duplicates' is false. Otherwise, the action has no removeAt input pin.

At least one data input/output of the call activity has no matching data input/output at the called process or the called global task, where matching means that they have to be assigned to the same business object, hence also having the same structure.

This attribute or table column is part of a foreign key but has a default value.

Reports foreign key properties (attributes or table columns) typed by an own type with different data type definition as the referenced unique key property. That means that different semantic data type is allowed but a different type system type is not.

The foreign key has neither a relationship nor a generalization assigned as relationship element.

Reports foreign key properties (attributes or table columns) with ambiguous origin properties.

This attribute or table column is part of a foreign key but is explicitly typed. A type change of the referenced feature will not effect the type of this feature.

Adjusting of gates deletes obsolete gates and creates necessary gates.

This generalization is assigned to a foreign key as a relationship element. This foreign key either has no attributes assigned to it or contains a nullable attribute.

This generalization has no foreign key.

Join/fork segments must not have guards.

The value of a derived property is computed from other information which should be specified by a constraint.

A specialization of a classifier marked as leaf is not allowed.

An abstract classifier should be specialized.

A generalization set should contain at least two generalization relationships.

The key owns no elements.

The section has no elements.

The behavior has no content.

None of the relationship roles is marked as foreign key role.

A generalization set without a contained generalization relationship is superfluous and might be deleted.

An icon may be used for some elements (stereotypes, values of stereotype properties, create templates, verification routines, engineering sequences, documentation commands, menus). The permissible icons are read from the $INODIR/icons directory. The file names might be invalid due to typing errors in dialogs or migration from older versions. Check whether the file name has a typing error or whether the icon file exists to fix this problem. Note that server and client might use different icon directories.

If 'is Unmarshalling' is set to false, for each signal event there must be one output pin.

If is Unmarshalling is true, there must be exactly one trigger for events of type SignalEvent. The number of result output pins must be the same as the number of attributes of the signal. The type of each result output pin must be the same as the corresponding attribute of the signal.

If 'is Unmarshalling' is true, there must be exactly one trigger of type signal event.

There are no output pins if the trigger events are only ChangeEvents, or if they are only CallEvents when this class is AcceptEventAction and not one of its children.

If the trigger events are all TimeEvents, there is exactly one output pin.

If the property 'is Control Pin' is set then the property 'is Control Type' has to be set, too.

The menu commands are given unique names internally but the name shown is localized and not automatically given a unique name. The menu commands could also have been adopted in various profiles in menus of the same name. The verify option picks all menu commands as if they were offered for one diagram. Menu commands of menus with the same name are combined into one menu. If there are then various menu commands in a menu with the same name, a message appears for each menu command assigned in this profile and the menu command is selected. The verify option checks both the English and German menu commands in the interface, regardless of which language is being used in the configuration editor. For troubleshooting either rename the menu command so that it is unique or remove the menu command.

The union select has not the same number of attributes as the union view.

The union select has not the same number of attributes as the union view.

An index without columns is superfluous.

An unique key is insufficient regarding a relationship in the following situation: The relationship allows many entity instances on foreign key side for the same referenced entity instance on unique key side, but the foreign key of this relationship is using the same set of attributes as this unique key.

An interaction without an interaction use may not have a gate.

The interaction should contain a gate with the same name.

The interaction use should contain a gate with the same name.

The message of the gate at the interaction should exist for the corresponding gate at the interaction use, too.

The message of the gate at the interaction use should exist for the corresponding gate at the interaction, too.

In diagrams ports may show the realized and used interfaces as socket/ball node. The calculation of these interfaces depends on several conditions. Therefore it is not possible to maintain the presentations always correctly. Invalid presentations have to be corrected manually.

The interface is not specialized or realized.

Verifies the correctness of the activity edge connection. - input pin and final node are invalid source nodes for the edge - output pin, initial node and value pin are invalid target nodes for the edge - object flow may only connect object node and control node - initial node is an invalid source node for a object flow - On object flow the properties 'isMulticast' and 'isMultireceive' cannot both be true - control flow may only connect activity node (except object node) or object node with the property 'is Control Type' set.

No node of a partition in a dimension may be in another partition in the same dimension.

The verification of diagrams checks all diagram contents, too. Messages for these contents may only be corrected within the diagram. If the verification of the diagram is called within the model browser or within another diagram the troubleshooting of these messages is not possible. Therefore the message 'Is inconsistent' is delivered and the diagram is opened for troubleshooting.

A node without a send and received message might be superfluous.

A join/fork pseudostate should have more than one incoming or outgoing transitions.

A constraint is used to specify conditions for elements. Therefore the constraints has to be connected to these elements.

Checks, if a state is left within the state machine deterministic.

Checks, if a state is left within the state machine.

Checks, if a state is reached within the state machine.

The event is not used as trigger or as occurrence specification.

The menu commands of all create menus are checked to see whether they are allowed as menu contents. If this is not the case, the problematic menu command is selected. The message may appear because a menu command is no longer allowed due to a change in the contents configuration.

Relationships can be configured for a selected stereotype in every profile. Combining both the stereotypes and relationship roles involved within a profile is unique. If configured relationships are recognized due to the profile import, these are no longer provided when creating within the profile being viewed. Relationships may appear twice if you configure relationships in the current profile and then import another profile. Relationship multiplicities are not evaluated during verification. These values, therefore, vary. Relationships which are configured twice are superfluous; you can delete one of the relationships.

The time of send and receive depends on the y coordinate. The receive should be below the send.

It is not possible to find a unique type for this expression due to multiple assignments to sequence flows and/or data associations.

The node is isolated.

This element has no value for the specified label. The label might be needless for this element.

The element uses a label value which is exactly the default value. You may delete this value and use the default value instead. Changes on the default value only effect elements without values. Values with the same value as the default are not changed.

The entry point of the state should exist in the sub state machine.

The exit point of the state should exist in the sub state machine.

For every value pin a value specification, that will be evaluated as the value of the pin, must be given

Verifies that a specification describing the action is given.

A value specification must be given.

For each chapter verifications might be activated. At these verifications a verify routine has to be defined. If the verify routine is missing the verify chapter is selected. For troubleshooting the verify chapter needs a verify routine or the verify chapter should be deleted.

At diagrams only those display options may change for which the configuration the change has allowed. Not allowed change may set to default value which deletes the value.

A region is allowed to contain maximal one element of type 'deep history'.

A region is allowed to contain maximal one element of type initial state.

A region is allowed to contain maximal one element of type 'shallow history'.

Access operations control the reading and writing of attributes.

Non abstract stereotypes are checked to see if they exist as create template in a profile or not. Stereotypes without templates cannot be used to create new elements of this stereotype. This means that the stereotype might be superfluous. Create a create template to fix this problem. If the stereotype is only used for structuring then it should be marked as abstract.

The partition has not been assigned a model element to be represented by the partition.

Actions sequences are initially created with one engineering action. It is possible to create or delete further actions. The evaluation of a sequence is done by the contained actions. Therefore a sequence without engineering action is superfluous and might be deleted or filled with actions.

No triggers are assigned to this action.

No type is specified for this element although a type is allowed by the configuration.

The configuration of display options needs a value for name property, text property, icon property, stereotype property and all font entries. Properties without a value may be deleted or a value should be added.

Diagrams are used to show the relationships between elements. Therefore each node should have an edge to another node.

An activity node should have at least one connection to another element in the activity, it should not be isolated.

The result pins of the exception handler body must correspond in number and types to the result pins of the protected node.

The semantic data type is not used for typing an element.

Diagrams are used to show the relations between elements. This element may be used in diagrams but it isn't.

All contents of a profile should be used in any way. Otherwise the content might be superfluous and may be deleted. Stereotypes, stereotype properties, labels and text definitions are used, if a value is set. Create templates, verifies, engineering actions and documentation commands should be used at least once as menu command. Especially create templates might be used within dialogs and not as menu command. This usage could not be checked. Engineering actions which are used as finder are not checked.

The configuration contains allowed relationships between pairs of stereotypes. These relationships may restrict the number of allowed elements of each stereotype. A violation of these restrictions produces a verify message. If the number of elements is less than the allowed minimum the structure of element might be incomplete. If the number of elements is greater than the allowed maximum the elements may use another stereotype or may be moved to another container.

The classifiers of the instance specification specify associations which may be instantiated as link. The number of allowed links at one instance specification is restricted by the multiplicities of the association roles.

The number of values for a slot should be between the lower and upper value of the defining feature.

The constraint has 'OCL' specified as language but the condition has not the correct syntax.

An object flow may have a selection behavior only if it has an object node as its source.

The model contains this element only as dummy. Dummy elements are created during the import of version objects. They are needed to create all relations of an element to other elements. For troubleshooting the version object of the dummy element should be imported. In some cases it may be enough to change the dummy property. But be aware, that the element might be incomplete.

The insertion point specified by the input pin, is required for ordered association ends and omitted for unordered ends.

The insertion point specified by the input pin, is required for ordered association ends and omitted for unordered ends.

The used operation must be known within the classifier of the target.

There is no communication via message flow between this and other participants.

The copy dependency adopts the text from the original requirement to the copy requirement. In cyclic dependencies the original and the copy requirement cannot be determined and therefore the text may not be adopted.

Generalization hierarchies must be directed and acyclical. A classifier cannot be both a transitively general and transitively specific classifier of the same classifier.

An use case cannot include use cases that directly or indirectly include it.

The number of defined placeholders and used columns have to be equal.

The number of defined placeholders and used attributes have to be equal.

At composite structure diagrams ports are display on the border of structured classifier or part nodes. These ports have to be reachable for the displayed classifier or the typing classifier of the displayed attribute.

A post-processing command is not possible for the preview window and docu repository output formats. For troubleshooting delete post-processing command or change the output format.

Profiles may import other profiles. Through the import all contents of the imported profile are known within the importing profile. The import is transitive. Therefore is is not necessary to import one profile directly if it is already imported transitively.

The element has an invalid value for the named property. The value has to be corrected.

The property 'is Behavior' of a port may be activated if the classifier owning this port owns a behavior.

An unique key is redundant regarding a relationship in the following situation: The relationship allows at most one entity instance on foreign key side for the same referenced entity instance on unique key side and the foreign key of this relationships uses a subset of the attributes as this unique key.

The foreign key role has a minimum greater than 0, but the foreign key contains no attributes or one of the attributes is nullable.

The foreign key role has a minimum of 0, but the foreign key contains only not nullable attributes.

The primary key role has a minimum of 1 or more.

This relationship has no foreign key.

The represented element of the lifeline has to be known within the classifier which owns the interaction.

The connector ends are connected to roles and ports. These roles and ports have to be reachable within the classifier which owns the connector.

Same interaction constraint in different interaction operands.

The parameter set assigned to the call action' 'Selected Input Parameter Set' property may only contain input and inout parameters.

The parameter set assigned to the property 'Selected Output Parameter Set' of the call action may only contain output and inout parameters.

Sequence flows are not valid at a subprocess with a set property 'is triggered by event'.

The node is isolated - no sequence flow, data association, compensation, message flow.

The node isn't integrated into the sequence flow.

There are no sequence flows going into this node.

There are no sequence flows going out of this node.

Source and target of the data association differ with respect to their business object assignments.

Transition should not connect state of orthogonal regions.

If the transition has an exit point as target the source has to be within the state of the exit point.

If the transition is a join/fork segment the other side should be connected to a state.

Sources and targets should be in orthogonal regions.

Sources and targets should be in different regions.

If an exit point for a state exists a sub state machine should exist, too.

If an entry point for a state exists a sub state machine should exist, too.

This element has no value for the specified stereotype property. The stereotype property might be needless for this element.

The element uses a stereotype property value which is exactly the default value. You may delete this value and use the default value instead. Changes on the default value only effect elements without values. Values with the same value as the default are not changed.

Properties and stereotype properties might be invisible for dialogs. The element still has a value for the named stereotype property although this property is invisible.

Subprocesses with a set property 'is triggered by event' may not contain unspecified start events.

Subprocesses with a set property 'is triggered by event' must contain exactly one triggered start event.

A property cannot be subset by a property with the same name.

The DB table contains no table columns.

The DB table contains no primary key.

If the transition has an entry point as source the target has to be within the state of the entry point.

By stepping down the task's call hierarchy, the call activity is found within one of the called processes.

Not every data input/output of the call activity is mapped uniquely to a data input/output at the called process or the called global task.

Not every data input/output of the called process or called global task is mapped to a data input/output at this call activity.

This element has no value for the specified text. The text might be needless for this element.

The element uses a text value which is exactly the default value. You may delete this value and use the default value instead. Changes on the default value only effect elements without values. Values with the same value as the default are not changed.

This element has no value for the specified text. The text might be needless for this element.

The element uses a text value which is exactly the default value. You may delete this value and use the default value instead. Changes on the default value only effect elements without values. Values with the same value as the default are not changed.

This element has no value for the specified text. The text might be needless for this element.

The element uses a text value which is exactly the default value. You may delete this value and use the default value instead. Changes on the default value only effect elements without values. Values with the same value as the default are not changed.

Requirements may have a text value. Through the copy dependency this text is adopted from the original to the copy requirement. If the copy requirement has already a text value before the copy dependency is created this text value has to be deleted.

The declaration of all elements has to be syntactically correct.

Mapping between two type system types is always stored for the type which is lower down in the profile's import hierarchy. If this procedure is not adhered to, a message appears. For troubleshooting reverse import relationship.

Mapping between two type system types can only connect types which have profiles which are linked using import hierarchy. For troubleshooting delete mapping or extend erroneous profile import.

The type of an argument pin is derived from the corresponding parameter of the behavior.

The type of an argument pin is derived from the corresponding owned parameter of the operation.

The type of an argument pin must be the same as the corresponding attribute of the signal.

The type of an argument pin must be the same as the corresponding attribute of the signal.

The 'exception' input pin may not have incoming activity edges.

The type of an exception pin is derived from the corresponding parameter of the behavior.

The 'first' input pin of the 'test identity' action has no type.

The fromAction of an action input pin cannot have control or data flows coming into or out of it or its pins.

The fromAction of an action input pin must have exactly one output pin.

The fromAction of an action input pin must only have action input pins as input pins.

The 'input' pins of the action must be the same as the pins of the link end data, the qualifier values and insertion pins.

The type of the 'object' input pin must be the same as the type of at least one of the association ends of the association.

The 'removeAt' input pin must have type 'UnlimitedNatural'.

The type of the 'replyValue' pin is derived from the type of the corresponding parameter of the operation that belongs to the trigger.

The type a result pin is derived from the corresponding parameter of the behavior.

The type of a result pin is derived from the corresponding owned parameter of the operation.

The type of the 'result' pin is derived from the corresponding structural feature of the classifier.

The type of the 'result' output pin of the 'ReadStructuralFeature' action is the same as the type of the structural feature.

The result pins must match the in and inout parameters of the operation specified by the trigger event in type.

The 'result' type of the 'test identity' action is Boolean.

The 'second' input pin of the 'test identity' action has no type.

The 'target' input pin of the 'destroy object' action has no type.

A parameter of type InOut can only be used in a parameter set if it is used both in an input and an output parameter set. If used in a call action then both of these parameter set have to be assigned as usages.

The classifier specializes another classifier which contains abstract operations. The specializing classifier should redefine the abstract operations of the general classifier.

The feature 'is abstract' implicates that the element needs to be specialized. The feature 'is leaf' implicates that no specialization is allowed. Therefore a conflict exists between the activation of these two features.

Reentrant behaviors cannot have stream parameters. Since only the parameters at an activity can be streaming, the verify is not implemented for all behaviors but only for activities.

The owner of the event implictly enters the activity to be compensated for boundary events or events triggering a subprocess. If an assigned event definition still specifies a compensating activity then this activity has to be equal to the owner activity.

The pin needs a special assign kind, depending on the action that it is assigned to and depending on the role it has.

The association cannot be an abstract classifier.

The association ends of the link end data must not be static.

Checks if the behavior is needed in the model. This is the case if it either is set the classifier behavior of its classifier or is a method of an operation or if it is referenced by elements like call behavior actions. The behavior may also be used to specify token selection for object nodes or object flows or to specify the token transformation for object flows.

If the owner of the activity is a use case, then the behavior of all contained call behavior actions has be assigned as an extending or including use case to the owner use case.

If the use case owns a behavior this behavior should be called as action within activity diagrams owned by the extending/included use cases.

The class realizes an interface. The class doesn't implement all attributes and operations of the interface.

The structure of the business object is not defined.

The business object is not used; this means it isn't assigned to an item aware element, a message, an error, an escalation or a signal.

Data type definitions may use data types from known type systems. For troubleshooting the data type definition may be deleted or a profile application makes the type system known.

Elements may use data base option from known type systems. For troubleshooting the option may be deleted or a profile application makes the type system known.

The deployment target of a deployment specification is a kind of execution environment.

Activity parameter nodes with no outgoing edges and one or more incoming edges must have a parameter with out, inout, or return direction. Activity parameter nodes with no incoming edges and one or more outgoing edges must have a parameter with in or inout direction.

Verifies for an interrupting edge (an activity edge which is meant to interrupt an interruptible region) if the edge leaves the interruptible region.

The edges coming into and out of a decision, fork and merge node must be either all object flows or all control flows.

If an element is represented by more than one partition in the same activity, it may be considered a modeling error.

If an attribute or a parameter is typed by an enumeration then the specified default value should name an enumeration literal of this type.

The error has no business object assigned.

A business object must be assigned to an escalation.

An event definition needs the specification of an event definition type.

The event assigned to the trigger must be a CallEvent.

The valid event type depends on the context of the event.

The exception handler body must have exactly one exception input pin.

The exception handler body may not have any explicit input or output edges.

The structured activity node, being both a group and a node, may contain nodes and may be assigned to groups. This may result in a cyclic assignment.

If the extending use case owns an activity diagram the connected extension points should be displayed as decision nodes.

The insertion point must have type 'UnlimitedNatural'.

The item aware element has no business object assigned.

The foreign key should have the same number of features as the referenced key.

The association ends of the link end data must all be from the same association and include all and only the association ends of that association.

If the behavior implements a behavioral feature the parameters of both have to match.

Both roles have a maximum greater than 1.

The message has no business object assigned.

The multiplicity of each 'result' output pin must be compatible with the multiplicity of the corresponding structural features of the unmarshall classifier.

The number of argument pins and the number of parameters of the behavior of type in and in-out must be equal.

The number of argument pins and the number of owned parameters of the operation of type in and in-out must be equal.

The number of argument pins must be the same as the number of attributes in the signal.

The number of argument pins must be the same as the number of attributes in the signal.

The number of 'replyValue' input pins must be equal to the 'return', 'out' or 'inout' parameters of the operation corresponding to the trigger.

The result pins must match the in and inout parameters of the operation specified by the trigger event.

The number of result pins and the number of owned parameters of the behavior of type return, out, and in-out must be equal.

The number of result pins and the number of owned parameters of the operation of type return, out, and in-out must be equal.

The number of 'result' pins must be equal to the structural features of the classifier.

The number of 'result' pins must be equal to the number of attributes in the signal.

The number of exception pins and the number of parameters of the behavior of type in and in-out must be equal.

Verifies the number of input pins with regard to the given action.

Verifies the number of output pins with regard to the given action.

The open end must be navigable.

If the 'ReadSelf' action is contained in an behavior that is acting as the body of a method, then the operation of the method must not be static.

If a behavior has input parameters that are in a parameter set, then any inputs that are not in a parameter set must be streaming. Same for output parameters.

The parameters in a parameter set must all be inputs or all be outputs of the same parameterized entity.

If a non-external partition represents a classifier and is contained in another partition, then the containing partition must represent a classifier, and the classifier of the subpartition must be nested in the classifier represented by the containing partition, or be at the contained end of a strong composition association with the classifier represented by the containing partition.

A dimension typically serves to group other partitions along the dimension. If it does not contain any partition, this may be not desired.

The properties 'upper value' and 'lower value' differ from the default values of this pin.

A procedure expression may use known type systems. For troubleshooting the procedure expression may be deleted or a profile application makes the type system known.

An element may redefine an existing element. Both elements must have the same element type. The owner of the redefining element has to specialize the owner of the redefined element. For some element types further conditions have to be fulfilled, e.g. the types of attributes have to be compatible. For troubleshooting a detailed look on the elements is necessary or the redefinition has to be deleted.

A selection behavior has one input parameter and one output parameter.

A selection behavior has one input parameter and one output parameter.

A business object must be assigned to a signal.

The features used by the foreign key should have the same sort order as in the referenced primary key.

Verifies for an interrupting edge (an activity edge, which is meant to interrupt an interruptible region) if the source node of the edge does belong to the same interruptible region as the edge itself.

The behavioral feature must be owned by the classifier that owns the behavior or be inherited by it.

The structural feature of the action must not be static.

In accordance with UML, a transformation behavior has one input parameter and one output parameter.

The trigger event must be a CallEvent.

A combined input and output parameter has two parameter nodes. The nodes have to be used one as an input and the other as an output parameter node, e.g. it is not allowed for both to have outgoing flows.

The type of the object input pin must be the same as the classifier of the object passed on this pin.

The type of the result output pin is the same as the type of the open association end.

The type of the result output pin of the 'ReadSelf' action is the host classifier.

The type of the result pin must be the same as the classifier of the action.

The type of the target pin must be the same as the type that owns the operation.

The type of the 'value' input pin must be the same as the classifier of the structural feature.

The types of exception objects that the exception handler is able to catch must be compatible to the type of the 'exception' input pin.

The type of the object input pin must be the same as the unmarshall classifier.

The type of the value specification must be compatible with the type of the 'result' output pin.

A connector may be typed by an association. As precondition the number of association roles and connector ends must be equal. The combination of connected classifiers of association roles and connected roles of the connector ends must match. The connector ends are mapped to the defining association role by the order of ends and roles. For troubleshooting the order of the connector ends has to be modified.

The type of an activity parameter node is the same as the type of its parameter.

The unmarshall classifier must have at least one structural feature.

An object flow with constant weight may not target an object node, or lead to an object node downstream with no intervening actions, that has an upper bound less than the weight.

The value of the property 'Is Collection' is not equal to the corresponding value of the business object assigned.

It is not possible to configure and get this message. The message is needed to catch not examined verify messages.

There may only be one ClearAssociationAction for an Association.

If two or more trigger of this action are using the same event, then the verify will drop a message.

Role binding is a mapping between features of the collaboration type and features of the owning classifier. This mapping indicates which connectable element of the classifier plays which role(s) in the collaboration. A connectable element may be bound to multiple roles in the same collaboration use (that is, it may play multiple roles). But each role of the collaboration use may only used once.

More than one default sequence flow is leaving this node.

There must be at least one trigger assigned to the action.

There may be only one call event assigned as trigger event.

Finds elements which are not part of any model section.

Join/fork segments must not have triggers. Transitions outgoing pseudostates may not have a trigger (except for those coming out of the initial pseudostate).

A subsetting property may strengthen the type of the subsetted property.

The values of the parameters for the data type of the specified target system are out of the valid range.

The semantic data type should contain a data type definition for each known target system.

The input parameter must be a bag of elements of the same as or a supertype of the type of the source object node. The output parameter must be the same or a subtype of the type of the object node.

The input parameter must be a bag of elements of the same as or a supertype of the type of source object node. The output parameter must be the same or a subtype of the type of source object node. The behavior cannot have side effects.

The input parameter must be the same as or a supertype of the type of object token coming from the source end. The output parameter must be the same or a subtype of the type of object token expected downstream.

Untriggered subprocesses may only contain unspecified start events.

The upper bound of a subsetting property may be less the upper bound of the subsetted property.

Include relationships are transitive. A direct include of an use case is superfluous, if a transitive include leads to the same use case.

Options can be created in create templates of option capable element types, e.g. DB tables. Only options which are also defined within the profile of the template are allowed. Moving a create template into another profile means you can no longer access the options. You can either delete the options used or make the type system accessible.

A view attribute should only use attributes from entities and views to which the own view contains a from clause.

A view column should use only columns from table and views to which the own view contains a from clause.

The values of a slot have to be conform to the type of the defining feature. Modifications for the defining feature or the used type lead to a correction of the used values.

The defining feature has an enumeration or a classifier as type. The values of the slot have to be enumeration literals or instance specifications of the classifier. Modifications for the defining feature or the used type lead to a correction of the used values.

Value pins must not be connected to an edge.

The view attribute uses no attributes.

The view column uses no columns.

The ER view contains no view attributes.

The DB view contains no view columns.

The DB view contains no from clause.

The ER view contains no from clause.

Constraints may be defined for all names and the ID of requirements. The value has to be corrected if it violates a defined constraint.

Label definitions of type 'string' or 'integer' might have constraints. The actual value violates such a constraint and should be corrected.

Stereotype properties of type 'string' or 'integer' might have constraints. The actual value violates such a constraint and should be corrected.

Text definitions might have constraints. The actual value violates such a constraint and should be corrected.

Extend relationships are used to extend use cases through extension points.

The semantic data type should be implemented by a data type definition.

Instance specification may have classifiers assigned. Without a classifier slots are not possible.

Diagrams are used to show the relations between elements. Empty diagrams are needless.

The enumeration contains no literals although they are allowed by the configuration.

The classifier contains no attributes although they are allowed by the configuration.

The classifier contains no operations although they are allowed by the configuration.

An XSL stylesheet is only required for the XML output format in a documentation command. For troubleshooting delete stylesheet or adapt output format.

An abstract stereotype shouldn't be used for a real element. This means that there are also no templates for an abstract stereotype. All menus below abstract stereotypes are also superfluous as a diagram shouldn't exist for this stereotype. The element should use a valid stereotype. Within the configuration the registered elements should be deleted or stereotype marked as not abstract.