We considered four topologies of code-anomaly agglomeration: (i) intra-boundary, (ii) cross-boundary, (iii) hierarchical, and (iv) concern-based.
Figure 2 shows an example of intra-boundary agglomeration.
A cross-boundary agglomeration always involve two or more components.
Fig. 2 Intra-boundary agglomeration in the OODT system.
Fig. 4 Cross-boundary agglomeration in the OODT system.
As an example of cross-boundary agglomeration, consider the architecture diagram from OODT in Fig. 4.
Analyzing the anomalous elements of the intra-boundary agglomeration, we observed that all of them contribute to the Connector Envy problem.
To illustrate this relation between architectural problems and agglomerations, consider the webgrid component depicted in Fig. 2. As we already discussed, webgrid suffers from the Connector Envy problem (Section 2) and contains an intra-boundary agglomeration (Section 3.1).
Europe-Wide Traffic-Control System "A digital communication network seamlessly integrates traffic info and creates an efficient, accident-preventing transport system in Europe, particularly in trans-boundary agglomeration areas; no more traffic jams.
As both of them are enclosed by the same architectural component (webgrid) and there is an association between them, the createHandler and parse elements form an intra-boundary agglomeration.
