The following example describes the usage of a DSM. The example is based on the Spring JPetstore example. In this DSM both the Java code and the Spring context XML files are shown.
Since the DSM is partitioned automatically, providing sub-systems and classes are shown in the lower triangular.
Since the DSM is partitioned automatically, providing sub-systems and classes are shown in the lower triangular.
Well-structured (hierarchical) systems only show dependencies (shown by the numbers in a cell) below the diagonal. Creating a DSM like this only takes a few minutes.
The loaded files that comprise the system must be rearranged in modules and layers before a valuable matrix is created. Based on this matrix one can detected dependecies (interfaces) that break the hierarchical calling sequence.
In the DSM it is possible to zoom in to class-method/attribute level. Tools provide more in-depth information when cells are selected.
No comments:
Post a Comment