Model element relationship issues

You can view a list of problematic traceability relationship for all open models.

Broken trace relationships

A broken trace relationship is generated when the target or source of a trace dependency cannot be found or accessed. You can view broken element trace relationships and their causes in the Model Report view.

A trace relationship is broken if the trace relationship meets one or more of the following criteria:

Circular trace relationships

Circular trace relationships occur when one or more model elements have abstraction dependencies on each other. Circular traces occur if the following abstraction relationships exist:

  • Class A has an abstraction relationship to class B.
  • Class B has an abstraction relationship to class C.
  • Class C has an abstraction relationship to class A.

Access violations between model elements with implied dependency relationships

An implied dependency between two UML elements occurs if any of the following situations are true:

Note: If one of the above situations is not true, an access violation error is listed in the Problems view. A model element that accesses a model element in another package without a Permission, Import Package, or Import Element relationship to the package of the target model element is an access violation that might not be resolvable.
Related tasks
Viewing model element relationship issues
Terms of use | Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.