guardian/atom-workshop
Logical Components
An overview of source code logical components.

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
Component Sizes (Lines of Code)
The "primary" logical decomposition has 7 components.

public7564 LOC (87%) 173 files
app894 LOC (10%) 24 files
utils54 LOC (<1%) 2 files
project35 LOC (<1%) 1 file
conf29 LOC (<1%) 1 file
ROOT17 LOC (<1%) 1 file
nginx5 LOC (<1%) 1 file

scope details...
  • 203 files, 8,598 LOC (100.0% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
public522 commits (47%)
app253 commits (23%)
project47 commits (4%)
ROOT30 commits (2%)
conf13 commits (1%)
nginx7 commits (<1%)
utils5 commits (<1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024 2023 2022 2021 2020 2019 2018 2017
app
14
4
19
5
20
3
4
16
31
137
project
7
3
28
6
3
public
8
17
15
5
2
16
84
45
330
ROOT
2
8
4
4
2
3
7
nginx
2
5
utils
5
conf
8
2
3


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report... 

flowchart TB
    n0["app"]
    n1["project"]
    n0 ---|"6"| n0
    n1 ---|"4"| n0
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0B7,stroke-width:6px
    linkStyle 1 stroke:#00688b93,stroke-width:4px
About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-07 12:33