aws-samples / automating-livestream-video-monitoring
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 (29 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 29 components.
  • 88 files, 6,027 lines of code (31.9% vs. main code).
  • "broadcast-monitoring-ui/src/components" is biggest, containing 21.06% of code.
  • "broadcast-monitoring/src" is smallest, containing 0.02% of code.


broadcast-monitoring-ui/src/components1269 LOC (6%) 15 files
broadcast-monitoring/src/sharedlib825 LOC (4%) 9 files
broadcast-monitoring/infrastructure717 LOC (3%) 4 files
broadcast-monitoring-ui/amplify/backend573 LOC (3%) 3 files
broadcast-monitoring/scripts428 LOC (2%) 2 files
broadcast-monitoring/infrastructure/elemental347 LOC (1%) 4 files
broadcast-monitoring/src/logo_detect244 LOC (1%) 7 files
broadcast-monitoring/src/consolidate_frame_results192 LOC (1%) 4 files
broadcast-monitoring-ui/src141 LOC (<1%) 3 files
broadcast-monitoring/src/expected_program132 LOC (<1%) 4 files
broadcast-monitoring/src/consolidate_results127 LOC (<1%) 2 files
broadcast-monitoring/src/frame_extractor114 LOC (<1%) 3 files
broadcast-monitoring/src/team_detection103 LOC (<1%) 4 files
broadcast-monitoring-ui/src/graphql95 LOC (<1%) 2 files
broadcast-monitoring/src/audio_detect91 LOC (<1%) 4 files
broadcast-monitoring/src/appsync_notify85 LOC (<1%) 3 files
broadcast-monitoring/src/reuse_detections75 LOC (<1%) 1 files
broadcast-monitoring-ui/src/router69 LOC (<1%) 1 files
broadcast-monitoring/src/crop_detection61 LOC (<1%) 1 files
broadcast-monitoring-ui/src/store59 LOC (<1%) 1 files
broadcast-monitoring/src/sports_detect55 LOC (<1%) 1 files
broadcast-monitoring/src/manifest_parser54 LOC (<1%) 1 files
broadcast-monitoring/src/start_sfn_execution39 LOC (<1%) 1 files
ROOT32 LOC (<1%) 1 files
broadcast-monitoring-ui29 LOC (<1%) 2 files
broadcast-monitoring-ui/src/assets25 LOC (<1%) 1 files
broadcast-monitoring24 LOC (<1%) 2 files
broadcast-monitoring-ui/public21 LOC (<1%) 1 files
broadcast-monitoring/src1 LOC (<1%) 1 files
Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2022-01-31 16:37