Linux / Arch / Sparc
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.
  • 601 files, 98,142 lines of code (100.0% vs. main code).
  • "kernel" is biggest, containing 51.56% of code.
  • "power" is smallest, containing 0.13% of code.


kernel50598 LOC (51%) 153 files
include17334 LOC (17%) 291 files
lib11126 LOC (11%) 82 files
mm8656 LOC (8%) 19 files
crypto4505 LOC (4%) 18 files
net2195 LOC (2%) 5 files
prom1416 LOC (1%) 16 files
vdso1036 LOC (1%) 10 files
math-emu978 LOC (<1%) 4 files
boot175 LOC (<1%) 1 files
power123 LOC (<1%) 2 files
Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2022-02-02 12:45