microsoft / ros_azure_iothub
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
launch
txt
cfg
nuspec
gitmodules
  • 14 extensions are included in analyses: cpp, launch, txt, bat, xml, yml, cfg, gitignore, ps1, md, json, nuspec, gitmodules, yaml
  • 5 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 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 ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (2 files).
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.

main660 LOC (66%) 7 files
test85 LOC (8%) 2 files
generated0 LOC (0%) 0 files
build and deployment40 LOC (4%) 3 files
other213 LOC (21%) 3 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
launch
cfg
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 7 files match defined criteria (660 lines of code, 100.0% vs. main code):
    • 2 *.cpp files (567 lines of code)
    • 1 *.yml files (48 lines of code)
    • 2 *.launch files (22 lines of code)
    • 1 *.ps1 files (15 lines of code)
    • 1 *.cfg files (8 lines of code)
  • " *.cpp" is biggest, containing 85.91% of code.
  • " *.cfg" is smallest, containing 1.21% of code.


*.cpp567 LOC (85%) 2 files
*.yml48 LOC (7%) 1 files
*.launch22 LOC (3%) 2 files
*.ps115 LOC (2%) 1 files
*.cfg8 LOC (1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
launch
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 2 files match defined criteria (85 lines of code, 12.9% vs. main code):
    • 1 *.cpp files (72 lines of code)
    • 1 *.launch files (13 lines of code)
  • " *.cpp" is biggest, containing 84.71% of code.
  • " *.launch" is smallest, containing 15.29% of code.


*.cpp72 LOC (84%) 1 files
*.launch13 LOC (15%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
nuspec
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitmodules".
    • files with paths like ".*[.]bat".
    • files with paths like ".*[.]nuspec".
  • 3 files match defined criteria (40 lines of code, 6.1% vs. main code):
    • 2 *.bat files (23 lines of code)
    • 1 *.nuspec files (17 lines of code)
  • " *.bat" is biggest, containing 57.5% of code.
  • " *.nuspec" is smallest, containing 42.5% of code.


*.bat23 LOC (57%) 2 files
*.nuspec17 LOC (42%) 1 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 3 files match defined criteria (213 lines of code, 32.3% vs. main code):
    • 1 *.md files (177 lines of code)
    • 2 *.xml files (36 lines of code)
  • " *.md" is biggest, containing 83.1% of code.
  • " *.xml" is smallest, containing 16.9% of code.


*.md177 LOC (83%) 1 files
*.xml36 LOC (16%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.cpp files are analyzed with CppAnalyzer:
    • 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
  • *.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
  • *.launch 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
  • *.ps1 files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.cfg files are analyzed with CfgAnalyzer:
    • 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-30 15:26