apache / tuscany-sdoSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

xsd

txt

wsdl

10 extensions are included in analyses: java, xsd, xml, txt, html, htm, wsdl, bat, sh, json
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/bin/.*" (Binaries for distribution) (3 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).

The source code folder contains 484 files:

438 files are included in analyses.
46 files are excluded from analyses:

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.

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

wsdl

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

172 files match defined criteria (31,348 LOC, 100.0% vs. main code):

153 *.java files (30,878 LOC)
16 *.xml files (393 LOC)
1 *.wsdl files (37 LOC)
1 *.htm files (21 LOC)
1 *.html files (19 LOC)

" *.java" is biggest, containing 98.5% of LOC.
" *.html" is smallest, containing 0.06% of LOC.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]est/.*".
files with paths like ".*_test[.].*".

143 files match defined criteria (14,181 LOC, 45.2% vs. main code):

112 *.java files (13,770 LOC)
31 *.xml files (411 LOC)

" *.java" is biggest, containing 97.1% of LOC.
" *.xml" is smallest, containing 2.9% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/pom[.]xml".
files with paths like ".*/assembly/src[.]xml".
files with paths like ".*[.]bat".
files with paths like ".*[.]sh".

11 files match defined criteria (1,262 LOC, 4.0% vs. main code). All matches are in *.xml files.

Other Code

xsd

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/resources/.*[.]xsd".
files with paths like ".*[.]txt".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/LICENSE[.][a-z0-9]+".
files with paths like ".*[.]json".
files with paths like ".*/[Ss]amples/.*".

112 files match defined criteria (5,986 LOC, 19.1% vs. main code):

20 *.java files (2,360 LOC)
73 *.xsd files (2,145 LOC)
13 *.txt files (1,105 LOC)
6 *.html files (376 LOC)

" *.java" is biggest, containing 39.43% of LOC.
" *.html" is smallest, containing 6.28% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.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

*.wsdl 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

*.htm files are analyzed with HtmlAnalyzer:

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

*.html files are analyzed with HtmlAnalyzer:

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

2023-08-10 13:35