CppDepend licensing is moving to a yearly subscription model.
We now plan 3 to 4 important releases per year instead of one major release every 18 months. This will provide more value, more often to users.
When purchasing this annual subscription, you will get a perpetual fallback license for the exact version available at the time of purchase. This perpetual license will allow you to continue to use the software even after the subscription ends, but without support.
The user will receive up to 40% discount for continuous subscription.
All version 6 licenses will be entitled to a 40% upgrade discount.
Licenses purchased before 2015 are also eligible for an upgrade discount.
CppDepend analysis can be started after a build to automatically refresh CppDepend results.
New settings are provided to avoid starting the CppDepend analysis
when the builds purpose is to provide up-to-date compiled bits for a run session, a debug session or a unit-test session.
In such a situation, it might be preferable to avoid starting the CppDepend analysis to avoid both consuming CPU cycles and distracting the developer's focus.
Minimal interval between CppDepend results being refreshed automatically after a build in VS which can now also be expressed in minutes.
Thanks to the new queryable domains QualityGates, Issues, IssuesInBaseline, Rules queries can be written to match IQualityGate, IIssue, IRule objects according to any criteria (rule violated or not, quality gate status that went from pass to fail, issues added since baseline, issues severity or debt...).
New syntax to write quality gates.
A new button lets you run the currently edited code query against the baseline.
A code query can now return code elements of various kinds such as assemblies, namespaces, types, methods and fields.
Thanks to this, new queryable domains are available including CodeElementsANTMF ; CodeElementParentsANT ; TypesAndMembersTMF ; MembersMF ; CodeContainersANTM ; AttributeTargetsATMF ; where Assemblies, Namespaces, Types, Methods, Fields.
A query can now return values of technical debt through new types Debt, AnnualInterest, DebtRating, Severity, TrendIcon and can also return System.Version and System.TimeSpan values.
A colour scale is now shown on query result metric values making it easier to compare them at a glance.
You can now write very simple queries like Methods or JustMyCode.CodeElements or codebase.PercentageCoverage. This syntax simplifies writing quality gates and trend metrics queries.
Trend metrics used to only be defined with queries that return a scalar. A trend metric can now also be defined with a query that returns rows.
In such situation the trend metric value is equals to the row count.
Improved query edit experience including:
- PageUp/PageDown and dot supported on completion items list
An CppDepend rule can now assign a technical debt and annual interest values to its issues.
The technical-debt is the estimated man-time that would take to fix the issue.
The annual-interest is the estimated man-time consumed per year if the issue is left unfixed. This provides an estimate of the business impact of the issue.
Issues of a rule now have a severity level in the blocker, critical, major, minor, info range.
The annual-interest is a measure of an issues severity. The severity and the annual-interest represent the same concept where the annual-interest is a continuous measure while the severity is a discrete measure.
For example the rule below matches methods which are too complex. The technical debt is linear to the methods excessive complexity and the annuel-interest is linear to the methods code coverage by tests (10 minutes per year for 100% coverage, 2 hours per year for 0% coverage).
All default rules now have these debt/interest formulas which offer real-world estimations, out of the box. If needed, these formulas can be easily customized.
The dashboard now shows estimated Debt values and evolution since baseline.
This dashboard is available in the CppDepend UI in Visual Studio and in generated reports.
Many facilities are proposed from the dashboard to query/sort/filter/group... the debt estimated values and the issues set.
These facilities include sorting debt and issues per rule or per code element, focusing on new and fixed debt since baseline and issues to fix by priority heuristics.
Customizable Quality Gates are now available to define excessive thresholds over debt estimations that might induce build failure and prevent checkin.
Customizable trend metrics are now available to measure debt trending.
The key is to offer comprehensive sets of actionable results.
The CppDepend project properties now has a Debt and Issues panel to customize all technical debt computation aspects.
This includes estimated Debt and Interest values conversion from man-time to cost estimation.
This also includes Debt Ratio and SQALE Debt Rating on a code element (as defined by the SQALE method). These are expressed in percentage of the estimated technical-debt compared to the estimated effort it would take to rewrite the code element from scratch.
Debt settings can also be shared among different CppDepend projects.
CQLinq can now be used to write quality gates.
Technically a quality gate is like a trend metric. It's a code query that returns a scalar or rows (in which case the value is the row count).
In practice a quality gate is used to fail a build when some thresholds are violated.
A warn threshold, a fail threshold and a unit can be provided.
Thanks to the new CQLinq capabilities, quality gates can be use to measure and monitor any fact concerning code, but also any fact concerning technical-debt, rules and issues.
Quality gates can also rely on differences since baseline (diff), which means that they can monitor progression like new technical debt since baseline or % code coverage on new code written since baseline.
11 quality gates are provided per default and LINQ queries can be written to query the quality gates status.
In previous CppDepend versions, a build used to fail upon critical rules failures. Now the build fails upon any quality gate failure.
The critical rule concept has been kept and the default quality gate Critical Rules Violated mimics the build fail behavior of previous CppDepend versions.