| Prev - Next - Down | SDMetrics - the UML design measurement tool |
| Rule: AggEnds | Category: Correctness |
| Severity: 1-high | Applies to: all areas |
| The binary association has two composite or shared aggregation ends. A binary association may have at most one shared (hollow diamond) or composite (filled diamond) aggregation end. This is a WFR of the UML. | |
| Rule: NaryAggEnds | Category: Correctness |
| Severity: 1-high | Applies to: all areas |
| The n-ary association has a composite or shared aggregation end. Three (or more)- way associations must not indicate shared or composite aggregation.
| |
| Rule: NaryNavEnds | Category: Correctness |
| Severity: 1-high | Applies to: all areas |
| The n-ary association indicates a navigable association end. Three (or more)- way associations must not indicate navigability at any of the association ends.
| |
| Rule: LooseEnd | Category: Completeness |
| Severity: 1-high | Applies to: all areas |
| The association has one or more ends not connected to a model element. Check the ends of the association, and attach the loose end(s) to the proper model element(s), or remove the association from the model. | |
| Rule: NaryAgg | Category: Style |
| Severity: 3-low | Applies to: design |
| The association has three or more association ends. People are often confused by the semantics of n-ary associations. N-ary associations have no representation in common programming languages. The suggestion is therefore to remodel the n-ary association using several plain associations. | |
| Rule: SpecAgg | Category: Style |
| Severity: 3-low | Applies to: all areas |
| The association is a specialization of another association. People are often confused by the semantics of specialized associations. The suggestion is therefore to model any restrictions on the parent association using constraints.
| |
| Prev | Up | Next |
| Appendix C.7 "Package Rules" | Contents | Appendix C.9 "Associationclass Rules" |