Class diagram hierarchy

As the metamodel matures and the number of entities increases, it becomes difficult to express the entire metamodel in a single class diagram.
Since Next Design allows you to create multiple class diagrams, it is a good idea to divide them as follows.

• Define the relationships between the main classes as a whole
• Define the relationships between entities within a package
• Define a detailed class diagram by extracting a part
• Define class diagrams that show derived relationships separately

It is a good idea to divide class diagrams appropriately according to the scale of the metamodel. When dividing class diagrams, it is effective to use the "Duplicate Class Diagram" function.

For example, as shown in the figure below, place the "Overall Overview" class diagram at the top of the profile navigator to illustrate the package configuration and the relationships between representative entities.

In addition, place a class diagram directly under each package to illustrate the relationships between the entities within the package.