|
| |
Possible warnings:
- " No Association for Message" - This warning checks whether associations exists between client and supplier classes that participate in a message. Displays a list of messages without associated associations.
- " Association not correctly navigable" - The association for this message is not navigable in that direction.
- " No Class for ObjectInstance" - This ObjectInstance does not have a type or class.
- " No Operation for Message" - Receiving class does not have an operation to accept this message.
- " Broken Associations" - These associations are broken. One or both endpoint elements of these associations do not exist. This can happen if you use controlled units and one endpoint element is deleted when the association was not loaded or read-only. In such a case, Rose cannot remove the association and it will be ‘broken’.
- " Broken Generalizations" - These generalize relationships are broken. The superclasses of these generalize relationships do not exist. This can happen if you use controlled units and a superclass is deleted when the subclass was not loaded or read-only. In such a case, Rose cannot remove the generalize relationship and it will be ‘broken’.
- " Broken Has Relationships" - These has relationships are broken. The suppliers of these has relationships do not exist. This can happen if you use controlled units and a supplier is deleted when the client was not loaded or read-only. In such a case, Rose cannot remove the “has” relationship and it will be ‘broken’.
- " Broken Dependency Relationships" - These dependency relationships are broken. The suppliers of these dependency relationships do not exist. This can happen if you use controlled units and a supplier is deleted when the client was not loaded or read-only. In such a case, Rose cannot remove the dependency relationship and it will be ‘broken’.
- " Broken Instantiates Relationships" - These instantiates relationships are broken. The instantiated classes of these instantiates relationships do not exist. This can happen if you use controlled units and a parameterized class is deleted when the instantiated class was not loaded or read-only. In such a case, Rose cannot remove the instantiates relationship and it will be ‘broken’.
This list contains broken instantiates relationships between instantiated and parameterized classes and between instantiated class utilities and parameterized class utilities.
- " Broken Realize Relationships" - These realize relationships are broken. The suppliers of these realize relationships do not exist. This can happen if you use controlled units and a supplier is deleted when the client was not loaded or read-only. In such a case, Rose cannot remove the realize relationship and it will be ‘broken’.
This list contains broken realize relationships between classes (including interfaces and actors).
- " Broken diagram icons" - These diagram icons do not have associated elements, but they should have them. The associated elements are missing. This can happen if you use controlled units and an element is deleted when the diagram(s) it was shown on were not loaded or read-only. In such a case, Rose cannot remove the icon(s) from the diagram(s) and they will be ‘broken’. In general, Rose marks these icons with a small octagon containing the letter "M" with a slash through it (unless the AdornUnresolvedReferences option is disabled).
This list contains all broken diagram icons. The diagram icons that are reported are:
 | Class icon |
| Use Case icon |
| Component icon |
| Package icon |
| Device icon |
| Processor icon |
| Association icon |
| Has Relationship icon |
| Dependency Relationship icon |
| Instantiates Relationship icon |
| Generalization icon |
| Realize Relationship icon |
| ObjectInstance icon |
| Message icon |
| Connection icon |
| Link icon |
|
