UML modeler Release Notes

(C) Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM(R) Corp.

Contents

1.0 Limitations
   1.1 Model validation: sequence diagrams

1.0 Limitations

1.1 Model validation: sequence diagrams

After creating and working with UML sequence diagrams in a model, the following types of validation errors might be reported:

Assembly connector '<Connector>' must only be defined from a role end requiring an interface to a role end providing that interface.

This error/warning occurs because of an inconsistency in the UML 2.1 specification.  The definition of this constraint in the UML spec has the side-effect of prohibiting the creation of a communication diagram for any Sequence Diagram whose lifelines do not represent roles providing and requiring interfaces.  For usability, connectors are created between the represented properties of all created lifelines to enable creation of communication ciagrams.

IRJA0131W Property "operation" of "<Receive Operation Event> ReceiveOperationEvent1" has 0 value(s); requires between 1 and 1.

IRJA0131W Property "operation" of "<Send Operation Event> SendOperationEvent1" has 0 value(s); requires between 1 and 1.

IRJA0131W Property "signal" of "<Receive Signal Event>" has 0 value(s); requires between 1 and 1.

IRJA0131W Property "signal" of "<Send Signal Event>" has 0 value(s); requires between 1 and 1.

These error/warnings occur because the UML specification requires these features to be specified for these UML elements.  However, this would prevent users from using sequence diagrams as "sketches" where they wish to show general flow of messages without actually specifying/defining operations or signals that are sent or received on them.  The product permits such "sketching" that results in these errors/warnings on validation.