Audits & Assessments
We provide a comprehensive and neutral assessment of the most important quality criteria of software systems.
Quality Improvement
We select, introduce and execute the most modern quality assurance methods.
Teamscale is an enterprise tool for continuous quality control. It’s novel incremental analysis engine provides real-time quality analysis results to project managers and developers via browser-based dashboards as well as integrations with development environments. The seamless integration with version control and issue tracking systems supports a workflow that goes beyond the mere measurement of quality and helps teams to effectively improve the quality of their systems.
ConQAT is a highly configurable software quality analysis engine that is designed for the rapid development of specialized quality analyses. It implements the most sophisticated algorithms for clone detection and architecture analysis. Furthermore, ConQAT is able to integrate the results produced by other quality analysis tools and provides advanced visualizations. It supports a multitude of programming languages, from modern languages like Java or C# to old languages like Cobol. Using its plug-in mechanism ConQAT is easily extensible.
Android Code Quality: Redundancy
Posted on 03/05/2014 by Dr. Nils Göde To comments
This is the second part of our quality audit of the Android core component’s source code. In my previous post we have looked at the structure of the code. In this post we will analyze the redundancy found in the code. Redundant code fragments—so-called clones— cause a variety of problems. The system is larger than it needs to be, defects are duplicated, changes have to be done multiple times, and individual copies may be overlooked when a bug is fixed (this is not a myth since many clone-related bugs have already been found in production software). Consequently, it is advisable to keep the redundancy as low as possible.
Apple's #gotofail bug: The Code Quality Perspective
Posted on 02/24/2014 by Dr. Florian Deißenböck To comments
On Friday, February 21st Apple published an update for iOS that fixed a serious security issue. What makes this issue interesting, is not only its severity but also the fact that the issue can be nicely pinned down two a single line of code. Conveniently, this code is open-source and available for analysis! In this post I’ll explain why this major security issue is, after all, the result of a number of quality issues, which are often undervalued as minor flaws.