guardian/manual-media-backup
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.

common2589 LOC (50%) 49 files
manual-media-backup1258 LOC (24%) 17 files
remove-archived482 LOC (9%) 9 files
backup-estimate-tool313 LOC (6%) 7 files
upload-estimate263 LOC (5%) 1 file
show-mxs-checksum115 LOC (2%) 3 files
inspect-oid74 LOC (1%) 2 files
find-filename28 LOC (<1%) 2 files

scope details...
  • 90 files, 5,122 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.
common66 commits (32%)
manual-media-backup61 commits (30%)
remove-archived23 commits (11%)
backup-estimate-tool17 commits (8%)
upload-estimate15 commits (7%)
inspect-oid8 commits (3%)
show-mxs-checksum4 commits (1%)
find-filename2 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
manual-media-backup
2
26
33
common
6
35
25
show-mxs-checksum
4
backup-estimate-tool
17
upload-estimate
13
2
find-filename
2
inspect-oid
3
5
remove-archived
11
12


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