korosuke613 / playground
Components & Dependencies

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.

  • 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.
Learn more...
Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

  • primary (11 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
Components
The "primary" logical decomposition has 11 components.
  • 72 files, 1,261 lines of code (5.7% vs. main code).
  • "terraform" is biggest, containing 33.7% of code.
  • "deno" is smallest, containing 0.48% of code.


terraform425 LOC (1%) 15 files
kubernetes372 LOC (1%) 15 files
java103 LOC (<1%) 6 files
javascript92 LOC (<1%) 10 files
aws71 LOC (<1%) 2 files
zx63 LOC (<1%) 9 files
rust48 LOC (<1%) 5 files
go32 LOC (<1%) 3 files
docker29 LOC (<1%) 1 files
earthly20 LOC (<1%) 4 files
deno6 LOC (<1%) 2 files
Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2022-05-14 00:22