TiCS dashboards

TiCS is a multi-project, multi-language and multi-site solution for automating quality and security analysis of source codes, based on the ISO/IEC 25010 (SQUARE) standard.

We propose you to browse the main dashboards.

Let's go for 2 minutes of reading.

The TiCS 'Dashboard' – 1: Projects are analyzed with a quality model, shared by more than 4,500 projects around the world and representing 1.1 billion lines of code analyzed every day. This model is public and is updated regularly.

(Click on the image to enlarge it)

The TiCS 'Dashboard' – 2: the 'Dashboard' allows you to go very quickly from high-level metrics to the bugs details in the code.

(Click on the image to enlarge it)

The TiCS 'Dashboard' – 3: Investigating the level 1 coding standard violations is very fast: just select the corresponding metric.

(Click on the image to enlarge it)

The TiCS 'Dashboard' – 4: It also provides the 'Root Cause Analysis' on projects. In general, an analysis of all metrics is available between two dates of your choice.

The 'Root Cause Analysis' gives the reason of changes occurring in the project: size modification (addition/removal of a library, new files,…), improvement/degradation of a KPI (modified files, fixed bugs, addition of new codes,…),…

(Click on the image to enlarge it)

The TiCS 'annotated code': TiCS unifies the interfaces regardless of the analyzers used such as Pclint, C++Test, cppcheck, PMD, etc. (list of supported analyzers (extract)). Teams don't have to learn how to launch the tools or how to interpret the different reports. Whatever the tools, the interfaces are identical.

(Click on the image to enlarge it)

The TiCS 'to-do list': The 'to-do list' below gives the order of importance of the anomalies detected in the code. The model provides the impact of a fix on the quality of the code, which allows the most serious bugs to be fixed first.

(Click on the image to enlarge it)

The TiCS 'client': Developers run their code analysis using the plug-in in their IDE or from the command line. Settings are retrieved from the server and are identical to those used for the project analysis.