UML22 — UML 2 Super / Conformance / inconsistencies

Summary:

There are two fundamental inconsistencies in the way that conformance is defined:
· BasicActions and BasicInteractions, which are defined at L1, both reference Signal and Event, defined in CommonBehaviors::Communications, which is defined at L2.
· Profiles are defined as L2 but Appendix C defines a profile for level L1. Clearly, if L1 is to support profiles, the definition of profiles needs to be defined at that level as well or a lower level.

Recommendation:

For the first item, move CommonBehaviors::Communications from L2 to L1

For the second item, a minimal impact resolution is to retain the L1 system as such, but to include it as part of compliance level L2. In general, the standard profiles should be specified explicitly as belonging to the appropriate compliance levels in section 2.4

see pages 335 - 336 of ptc/2006-04-01