aws / porting-assistant-dotnet-client
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
props
txt
  • 9 extensions are included in analyses: cs, csproj, json, md, props, yml, gitignore, txt, sh
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (8 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.

main5130 LOC (22%) 99 files
test8675 LOC (38%) 46 files
generated0 LOC (0%) 0 files
build and deployment128 LOC (<1%) 8 files
other8531 LOC (37%) 12 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
props
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 99 files match defined criteria (5,130 lines of code, 100.0% vs. main code):
    • 97 *.cs files (5,090 lines of code)
    • 2 *.props files (40 lines of code)
  • " *.cs" is biggest, containing 99.22% of code.
  • " *.props" is smallest, containing 0.78% of code.


*.cs5090 LOC (99%) 97 files
*.props40 LOC (<1%) 2 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]est/.*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*UnitTests/.*".
    • files with paths like ".*TestUtils/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 46 files match defined criteria (8,675 lines of code, 169.1% vs. main code):
    • 17 *.csproj files (4,572 lines of code)
    • 29 *.cs files (4,103 lines of code)
  • " *.csproj" is biggest, containing 52.7% of code.
  • " *.cs" is smallest, containing 47.3% of code.


*.csproj4572 LOC (52%) 17 files
*.cs4103 LOC (47%) 29 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".
  • 8 files match defined criteria (128 lines of code, 2.5% vs. main code):
    • 7 *.csproj files (114 lines of code)
    • 1 *.sh files (14 lines of code)
  • " *.csproj" is biggest, containing 89.06% of code.
  • " *.sh" is smallest, containing 10.94% of code.


*.csproj114 LOC (89%) 7 files
*.sh14 LOC (10%) 1 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]gitignore".
  • 12 files match defined criteria (8,531 lines of code, 166.3% vs. main code):
    • 10 *.json files (8,400 lines of code)
    • 2 *.md files (131 lines of code)
  • " *.json" is biggest, containing 98.46% of code.
  • " *.md" is smallest, containing 1.54% of code.


*.json8400 LOC (98%) 10 files
*.md131 LOC (1%) 2 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)
  • *.props files are analyzed with XmlAnalyzer:
    • 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 15:19