deck.gl
Components & Dependencies

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 (7 components)
Logical Decomposition #1: PRIMARY
The decompositions is based on folder structure at level 1 (relative to the source code root).
Components
The "primary" logical decomposition has 7 components.
  • 489 files, 38,562 lines of code (100.0% vs. main code).
  • "modules" is biggest, containing 65.4% of code.
  • "bindings" is smallest, containing 0.03% of code.


modules25218 LOC (65%) 304 files
examples6798 LOC (17%) 86 files
website3254 LOC (8%) 55 files
showcases3103 LOC (8%) 38 files
scripts128 LOC (<1%) 3 files
ROOT48 LOC (<1%) 2 files
bindings13 LOC (<1%) 1 files
Alternative Visuals
Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2020-09-11 22:21