guardian/pluto-storagetier
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 8 components.

common2215 LOC (22%) 56 files
online_archive1595 LOC (16%) 17 files
media_remover1434 LOC (14%) 15 files
online_nearline1407 LOC (14%) 14 files
mxs-copy-components1382 LOC (14%) 19 files
project_restorer578 LOC (5%) 12 files
scripts224 LOC (2%) 2 files
restorer-test18 LOC (<1%) 1 file

scope details...
  • 136 files, 8,853 LOC (91.8% 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.
common200 commits (28%)
online_archive198 commits (28%)
media_remover93 commits (13%)
project_restorer83 commits (11%)
online_nearline75 commits (10%)
mxs-copy-components51 commits (7%)
scripts14 commits (1%)
restorer-test2 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
project_restorer
6
2
5
70
common
4
4
11
65
116
media_remover
22
71
online_nearline
5
39
31
restorer-test
2
online_archive
18
34
146
scripts
11
3
mxs-copy-components
19
32


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...

No temporal dependencies found.

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:39