awslabs / aws-embedded-metrics-dotnet
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
csproj
txt
  • 8 extensions are included in analyses: cs, json, csproj, md, sh, yml, gitignore, txt
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*[.]txt" (Text files) (0 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main1878 LOC (48%) 44 files
test1247 LOC (32%) 20 files
generated0 LOC (0%) 0 files
build and deployment145 LOC (3%) 6 files
other563 LOC (14%) 20 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 44 files match defined criteria (1,878 lines of code, 100.0% vs. main code):
    • 41 *.cs files (1,827 lines of code)
    • 3 *.yml files (51 lines of code)
  • " *.cs" is biggest, containing 97.28% of code.
  • " *.yml" is smallest, containing 2.72% of code.


*.cs1827 LOC (97%) 41 files
*.yml51 LOC (2%) 3 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*[.][Tt]ests/.*".
    • files with paths like ".*[.][Tt]ests[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 20 files match defined criteria (1,247 lines of code, 66.4% vs. main code):
    • 17 *.cs files (1,183 lines of code)
    • 3 *.csproj files (64 lines of code)
  • " *.cs" is biggest, containing 94.87% of code.
  • " *.csproj" is smallest, containing 5.13% of code.


*.cs1183 LOC (94%) 17 files
*.csproj64 LOC (5%) 3 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]csproj".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
  • 6 files match defined criteria (145 lines of code, 7.7% vs. main code):
    • 4 *.sh files (101 lines of code)
    • 2 *.csproj files (44 lines of code)
  • " *.sh" is biggest, containing 69.66% of code.
  • " *.csproj" is smallest, containing 30.34% of code.


*.sh101 LOC (69%) 4 files
*.csproj44 LOC (30%) 2 files
Other Code
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]gitignore".
  • 20 files match defined criteria (563 lines of code, 30.0% vs. main code):
    • 6 *.cs files (210 lines of code)
    • 6 *.md files (208 lines of code)
    • 5 *.json files (110 lines of code)
    • 3 *.csproj files (35 lines of code)
  • " *.cs" is biggest, containing 37.3% of code.
  • " *.csproj" is smallest, containing 6.22% of code.


*.cs210 LOC (37%) 6 files
*.md208 LOC (36%) 6 files
*.json110 LOC (19%) 5 files
*.csproj35 LOC (6%) 3 files
Analyzers
Info about analyzers used for source code examinations.
  • *.cs files are analyzed with CSharpAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on namespace heuristics)
  • *.yml files are analyzed with YamlAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-01-31 19:33