guardian/vidispine-monitor
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.

vsmetriccheck255 LOC (21%) 2 files
vsstoragecheck165 LOC (13%) 2 files
pagerduty164 LOC (13%) 2 files
vshealthcheck131 LOC (10%) 2 files
ROOT129 LOC (10%) 1 file
vidispine23 LOC (1%) 2 files
common20 LOC (1%) 2 files

scope details...
  • 13 files, 887 LOC (74.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.
ROOT8 commits (28%)
vsmetriccheck8 commits (28%)
pagerduty6 commits (21%)
vsstoragecheck5 commits (17%)
common4 commits (14%)
vidispine2 commits (7%)
vshealthcheck2 commits (7%)
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
vidispine
2
ROOT
1
7
common
1
3
pagerduty
6
vsmetriccheck
1
7
vsstoragecheck
1
4
vshealthcheck
1
1


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