Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Static Dependencies
Dependencies among components are static code dependencies among files in different components.
  • Analyzed system has 18 links (arrows) between components.
  • The number on the arrow represents the number of files from referring component that depend on files in referred component.
  • These 18 links contain 30 dependencies.
flowchart TB
    n0["iep-spring-leader-redis-cluster"]
    n1["iep-service"]
    n2["iep-spring-leader-dynamodb"]
    n3["iep-spring-atlas"]
    n4["iep-admin"]
    n5["iep-spring-aws2"]
    n6["iep-spring-sbhealth"]
    n7["iep-dynconfig"]
    n8["iep-launcher"]
    n9["project"]
    n10["iep-ses"]
    n11["iep-servergroups"]
    n12[".github"]
    n13["iep-spring"]
    n14["iep-spring-spectatord"]
    n15["iep-spring-userservice"]
    n16["iep-spring-dynconfig"]
    n17["iep-spring-leader"]
    n18["iep-spring-admin"]
    n19["iep-leader-api"]
    n13 -->|"3"| n1
    n15 -->|"3"| n1
    n16 -->|"3"| n7
    n18 -->|"3"| n4
    n0 -->|"2"| n19
    n2 -->|"2"| n19
    n15 -->|"2"| n4
    n16 -->|"2"| n4
    n2 -->|"1"| n5
    n3 -->|"1"| n1
    n4 -->|"1"| n7
    n4 -->|"1"| n1
    n6 -->|"1"| n1
    n11 -->|"1"| n1
    n14 -->|"1"| n1
    n16 -->|"1"| n1
    n17 -->|"1"| n1
    n18 -->|"1"| n1
    classDef default fill:#808080,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    class n0,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,n13,n14,n15,n16,n17,n18,n19 highlighted;
    linkStyle 0 stroke:#00688b82,stroke-width:3px
    linkStyle 1 stroke:#00688b82,stroke-width:3px
    linkStyle 2 stroke:#00688b82,stroke-width:3px
    linkStyle 3 stroke:#00688b82,stroke-width:3px
    linkStyle 4 stroke:#00688b70,stroke-width:2px
    linkStyle 5 stroke:#00688b70,stroke-width:2px
    linkStyle 6 stroke:#00688b70,stroke-width:2px
    linkStyle 7 stroke:#00688b70,stroke-width:2px
    linkStyle 8 stroke:#00688b5E,stroke-width:1px
    linkStyle 9 stroke:#00688b5E,stroke-width:1px
    linkStyle 10 stroke:#00688b5E,stroke-width:1px
    linkStyle 11 stroke:#00688b5E,stroke-width:1px
    linkStyle 12 stroke:#00688b5E,stroke-width:1px
    linkStyle 13 stroke:#00688b5E,stroke-width:1px
    linkStyle 14 stroke:#00688b5E,stroke-width:1px
    linkStyle 15 stroke:#00688b5E,stroke-width:1px
    linkStyle 16 stroke:#00688b5E,stroke-width:1px
    linkStyle 17 stroke:#00688b5E,stroke-width:1px




Explore: 2D force graph | 3D force graph

Show more details about dependencies...
From Component
 --> To Component
From Component
(files with dependencies)
Details
iep-spring
  --> iep-service
3 files, 177 LOC (84%)
3 source files
iep-spring-userservice
  --> iep-service
3 files, 139 LOC (43%)
3 source files
iep-spring-dynconfig
  --> iep-dynconfig
3 files, 160 LOC (100%)
3 source files
iep-spring-admin
  --> iep-admin
3 files, 211 LOC (100%)
3 source files
iep-spring-leader-redis-cluster
  --> iep-leader-api
2 files, 214 LOC (77%)
2 source files
iep-spring-leader-dynamodb
  --> iep-leader-api
2 files, 329 LOC (100%)
2 source files
iep-spring-userservice
  --> iep-admin
2 files, 78 LOC (24%)
2 source files
iep-spring-dynconfig
  --> iep-admin
2 files, 60 LOC (37%)
2 source files
iep-spring-leader-dynamodb
  --> iep-spring-aws2
1 file, 21 LOC (6%)
1 source file
iep-spring-atlas
  --> iep-service
1 file, 100 LOC (75%)
1 source file
iep-admin
  --> iep-dynconfig
1 file, 29 LOC (1%)
1 source file
iep-admin
  --> iep-service
1 file, 29 LOC (1%)
1 source file
iep-spring-sbhealth
  --> iep-service
1 file, 29 LOC (100%)
1 source file
iep-servergroups
  --> iep-service
1 file, 93 LOC (8%)
1 source file
iep-spring-spectatord
  --> iep-service
1 file, 62 LOC (78%)
1 source file
iep-spring-dynconfig
  --> iep-service
1 file, 100 LOC (62%)
1 source file
iep-spring-leader
  --> iep-service
1 file, 123 LOC (81%)
1 source file
iep-spring-admin
  --> iep-service
1 file, 84 LOC (39%)
1 source file
About This Analysis

Static code dependencies refer to the relationships between different modules, libraries, or components in a software system that are established at compile-time rather than at runtime. These dependencies are determined by the code itself, meaning that one module directly references another through imports, includes, or explicit references in the code. Examples include:

  • Library and Module Imports
  • Class Dependencies (Inheritance & Composition)
  • Function and Method Calls
  • Dependency Injection Without Runtime Resolution
Learn more...
  • To learn more about good practices on componentization and dependencies, Sokrates recommends the following resources:


2026-10-07 17:31