azure / tattler
Components

An overview of source code logical components.

Intro

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.

Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

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 5 components.
  • 17 files, 1,835 LOC (80.0% vs. main code).
  • "readers" is biggest, containing 35.91% of LOC.
  • "ROOT" is smallest, containing 8.5% of LOC.


readers659 LOC (28%) 3 files
internal548 LOC (23%) 8 files
data259 LOC (11%) 4 files
batching213 LOC (9%) 1 file
ROOT156 LOC (6%) 1 file
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
readers22 commits (30%)
internal19 commits (26%)
data15 commits (20%)
batching10 commits (13%)
ROOT9 commits (12%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2025 2024
readers
40
internal
36
data
26
batching
10
ROOT
9


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.



2025-05-06 23:11