Increase the code quality of your software project - and thus effectively lower maintenance effort.
Quickly track down the source code spots with the most technical debt (i.e. the highest risk for causing defects in the future).
Correlate quality metrics with project-specific figures (e.g. bug frequency or project revenue).
Uncover historical trends that lie within your project - and thereby form a solid basis for qualified business decisions.
An exhaustive quality report provides valuable insights both for software developers (code metrics) and project managers (related accounting data).
Easy to use: no implementation hassle, no maintenance expenditures, no up-front expertise required.
-- As of now, .CQ is in a very early development phase. A first version (for C#) will be available around the middle of 2014. --
Quickly pinpoint problematic source code locations for taking selective action on
them and thus systematically and effectively raise the value of your codebase.
Correlate your company-specific data with the code's quality measurements to better
control business success and to fine-tune your development process.
Controlling and raising the intrinsic quality of your software project means lowering
its maintenance costs (in the long run) as well as lowering the danger of defects
(on the short-term side).
In sum: It will significantly axe costs, reduce risk, and thus raise ROI.
.CQ will widely incorporate customer and community feedback to build a product that
is really useful to you. So tell us about your problems, about your experiences
(good or bad), and about everything else that might seem relevant to you. It's highly
appreciated. You can do this in various different ways: By commenting directly on
the respective page, by joining the discussion in the message forum, or by doing
a quick survey.