Source Code Analysis Scope
Files includes and excluded from analyses
properties

scoping details...
  • 9 extensions are included in analyses: java, properties, txt, yml, gradle, xml, md, bat, gitignore
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
    • 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) (1 file).
    • exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
    • exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
    • exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (0 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.
main17197 LOC (71%) 137 files
test5214 LOC (21%) 47 files
generated0 LOC (0%) 0 files
build and deployment398 LOC (1%) 7 files
other1407 LOC (5%) 13 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

java17180 LOC (99%) 136 files
xml17 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 137 files match defined criteria (17,197 LOC, 100.0% vs. main code):
    • 136 java files (17,180 LOC)
    • 1 xml files (17 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

java5200 LOC (99%) 46 files
xml14 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
  • 47 files match defined criteria (5,214 LOC, 30.3% vs. main code):
    • 46 java files (5,200 LOC)
    • 1 xml files (14 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

gradle146 LOC (36%) 2 files
yaml128 LOC (32%) 3 files
gitignore63 LOC (15%) 1 file
bat61 LOC (15%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]github/workflows/.*[.]ya?ml".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*[.]bat".
  • 7 files match defined criteria (398 LOC, 2.3% vs. main code):
    • 2 gradle files (146 LOC)
    • 3 yaml files (128 LOC)
    • 1 gitignore files (63 LOC)
    • 1 bat files (61 LOC)
Other Code
properties
Explore:   circles  |  sunburst

java1286 LOC (91%) 4 files
properties71 LOC (5%) 6 files
md50 LOC (3%) 3 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]properties".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[Dd]emos?/.*".
    • files with paths like ".*[.]txt".
  • 13 files match defined criteria (1,407 LOC, 8.2% vs. main code):
    • 4 java files (1,286 LOC)
    • 6 properties files (71 LOC)
    • 3 md files (50 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.

learn more about used code analyzers...
  • *.java files are analyzed with JavaAnalyzer:
    • 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 package names)
  • *.xml 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