7 UML Diagram Requirements

32.1563GPPFixed Mobile Convergence (FMC) model repertoireRelease 17Telecommunication managementTS

Classes and their relationships shall be presented in class diagrams.

It is recommended to create:

 An overview class diagram containing all object classes related to a specific management area (Class Diagram).

 The class name compartment should contain the location of the class definition (e.g., "Qualified Name")

 The class attributes should show the "Signature". (see subclause 7.3.44 of [2] for the signature definition);

 A separate inheritance class diagram in case the overview diagram would be overloaded when showing the inheritance structure (Inheritance Class Diagram);

 A class diagram containing the user defined data types (Type Definitions Diagram);

 Additional class diagrams to show specific parts of the specification in detail;

 State diagrams for complex state attributes.

Annex A (informative):
Examples of using <<ProxyClass>>