Discover amazing details
you never thought about
your C\C++ projects

Trend charts are displayed on the CppDepend dashboard. Some trend charts are available per default to show:

• Lines of Code
• Number of Code Rules Violated and number of Code Rules Violations
• Code Coverage per Tests
• Max and Average values for various Code Quality Metrics
• Third-Party Usage

CppDepend's DSM comes with numerous options to try:

• It has numerous facilities to dig into dependency exploration (a parent column/row can be opened, cells can be expanded...)
• It can deal with squared symmetric DSM and rectangular non-symmetric DSM
• Rows and columns can be bound, to constantly have a squared symmetric matrix
• It comes with the option Indirect usage, where cell shows direct and indirect usage
• The rows can contain third-party code elements

A Quality Gate is a check on a code quality fact that must be enforced before releasing and eventually, before committing to source control. A Quality Gate can be seen as a PASS/FAIL criterion for software quality.

A dozen of default Quality Gates are proposed by CppDepend related to measures like technical debt amount, code coverage or amount of issues with particular severity.

Notice that special red / yellow / green losange icons shows Quality Gates status: fail / warn / pass.

CppDepend can analyze source code and C++ Projects through CppDepend.Console.exe. Each time it analyzes a code base, CppDepend yields a report that can inform you about the status of your development. You can customize sections shown in the report and you can even provide your own XSL sheet for full customization.

You can also build your own set of CQLinq constraints that will be checked at each analysis. The report will warn you each time a constraint is violated. This feature makes automatic design and quality regression test a reality.

• Code maintainability improves. This positively impacts the productivity of development teams.
• Over time, developers get educated about rules to follow and their skills improve.
• Architects can anticipate the impact of code changes. The right decisions are taken early.
• Since quality is checked automatically and continuously with a strong focus on recent changes, both in Visual Studio and in the DevOps, the team builds better code.
• Executives gain control over costs and risks thanks to light being shed on development facts and trends that matter most.

CppDepend is the only Visual Studio extension that is able to tell the developer that over the past hour, the code just written has introduced debt that would cost for example about 30 minutes should it have to be repaid later. Knowing this, the developer can fix the code before even committing it to the source control.

With CppDepend code rules are C# LINQ queries that can be created and customized in a matter of seconds. These queries contain C# formulas to compute accurate technical debt estimations.

The default rule-set offers over a hundred code rules that detect a wide range of code smells including entangled code, dead-code, API breaking changes and bad OOP usage.

As a static analyzer, CppDepend will likely find hundreds or even thousands of issues affecting a real-world code base. Stopping work to attempt to fix all issues for weeks would be quite unproductive.

This is why CppDepend is the only tool that offers a baseline in Visual Studio. The tool estimates the Technical Debt progress since the baseline.

Recent code smells that should be fixed before committing any code to source control are highlighted in Visual Studio. They can then be fixed even before reaching the source server.

As a consequence the Code Quality remains under control with no major upfront investment.