microsoft / MSLab
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 (43 components)

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure (relative to the source code root), with automatically defined folder depth to have at least 10 components.

Bubble Chart | Tree Map
Components
The "primary" logical decomposition has 43 components.
  • 94 files, 22,898 lines of code (43.7% vs. main code).
  • "Scripts" is biggest, containing 15.09% of code.
  • "Docs" is smallest, containing 0.03% of code.


Scripts3455 LOC (6%) 6 files
Tools1694 LOC (3%) 8 files
Scenarios/AzSHCI and MDT1537 LOC (2%) 2 files
Scenarios/Exploring new features in 21H21182 LOC (2%) 2 files
Scenarios/StorageReplica1150 LOC (2%) 8 files
Scenarios/AzSHCI Deployment989 LOC (1%) 2 files
Scenarios/S2D and Grafana866 LOC (1%) 4 files
Scenarios/S2D Converged827 LOC (1%) 2 files
Scenarios/S2D Hyperconverged802 LOC (1%) 2 files
Scenarios/Securing LDAP756 LOC (1%) 2 files
Scenarios/SDNExpress with SCVMM746 LOC (1%) 2 files
Scenarios/AzSHCI and Kubernetes722 LOC (1%) 2 files
Scenarios/AzSHCI and Bare Metal with SCVMM717 LOC (1%) 2 files
Scenarios/S2D and Bare Metal with SCVMM715 LOC (1%) 1 files
Scenarios/S2D and SDN649 LOC (1%) 2 files
Scenarios/AzSHCI and Stretch Cluster575 LOC (1%) 2 files
Scenarios/AzSHCI and AVD549 LOC (1%) 1 files
Scenarios/AzSHCI and Migration from Windows Server484 LOC (<1%) 2 files
Scenarios/AzSHCI and Azure Benefits467 LOC (<1%) 2 files
Scenarios/SDNExpress with Windows Admin Center414 LOC (<1%) 2 files
Scenarios/S2D and Cloud Services Onboarding360 LOC (<1%) 2 files
Scenarios/Rolling Cluster Upgrade332 LOC (<1%) 1 files
Scenarios/AzSHCI and Arc-enabled VMs324 LOC (<1%) 2 files
Scenarios/Hyper-V with Shared Storage310 LOC (<1%) 2 files
Scenarios/TestingCSVRedirection255 LOC (<1%) 2 files
Scenarios/Securing Admin Workstation247 LOC (<1%) 2 files
Scenarios/Azure Arc for Servers245 LOC (<1%) 2 files
Scenarios/S2D and Azure Arc234 LOC (<1%) 2 files
Scenarios/S2D and SCVMM in large Datacenters205 LOC (<1%) 1 files
Scenarios/BitLocker on S2D cluster180 LOC (<1%) 2 files
Scenarios/Azure Image Builder174 LOC (<1%) 1 files
Scenarios/S2D and Direct Connectivity161 LOC (<1%) 2 files
Scenarios/AzSHCI and VMFleet122 LOC (<1%) 1 files
Scenarios/Running WSLab in Azure92 LOC (<1%) 2 files
Scenarios/StorageMigrationService87 LOC (<1%) 2 files
Scenarios/FSLogix53 LOC (<1%) 2 files
Scenarios/AppAttach50 LOC (<1%) 2 files
Scenarios/S2D on AWS and VMware47 LOC (<1%) 2 files
ROOT45 LOC (<1%) 1 files
Scenarios/S2D and Validate-DCB30 LOC (<1%) 1 files
Scenarios/Testing Nano performance25 LOC (<1%) 1 files
Scenarios/LAPS on Nano18 LOC (<1%) 2 files
Docs6 LOC (<1%) 1 files
Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2022-01-30 13:35