Linux / Arch / Arm64
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.
  • 493 files, 88,378 lines of code (100.0% vs. main code).
  • "kvm" is biggest, containing 27.05% of code.
  • "tools" is smallest, containing 0.04% of code.


kvm23906 LOC (27%) 88 files
kernel22778 LOC (25%) 99 files
include16495 LOC (18%) 205 files
crypto9279 LOC (10%) 38 files
boot6219 LOC (7%) 9 files
mm4566 LOC (5%) 22 files
lib3827 LOC (4%) 26 files
net1032 LOC (1%) 2 files
hyperv141 LOC (<1%) 2 files
xen101 LOC (<1%) 1 files
tools34 LOC (<1%) 1 files
Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2022-02-02 12:22