Scertify™ Refactoring Assessment 1.2 i...
Scertify™ Refactoring Assessment 1.2 is available
Posted by Tocea in Release Notes on November 13, 2012 with 1 Comment
Version: 1.2
Release Date: 11.05.2012
Scertify™ Refactoring Assessment 1.2 is available. This new version is a keystone of the upcoming features for Technical Debt benchmark, which will be more accurate and user-oriented thanks to contextual data on projects (ie: open source, business sector, web application, framework, etc.).
Users are now able to attach contextual information to their projects:
- Generic Information (collected once for a user and associated to all his projects):
- Business Sector (ie: Industry, Telecom, Finance, Insurance, etc.)
- Firm Size
- Project Information (collected once for a user):
- Application Type: Business, Embedded, Framework, Mobile, Web applications
- Development Type: Internal (In-House), External (Outsourced), Open Source applications
The next version of the plugin will offer to users the capacity to exploit collected information, in order to improve the benchmark of projects. For example, code metrics of an in-house mobile application developped by a bank will be compared to other in-house mobile applications of other banks.
Fix NullPointerException in evaluation page for projects of non object languages (ie JavaScript)
Fix NullPointerException with manual rules
Fix potential bug with sql server database on sonar initialisation (duplicated metric)
Download Scertify™ Refactoring Assessment 1.2
Tags: application, assessment, business sector, contextual, information, Refactoring Assessment, sector, Technical Debt benchmark 1 Comment
Comments are closed.
Follow us
Yasin on December 6, 2012
Sadly, this doesn’t only apply to legacy code.I’ve wokerd on projects that were pretty much green-field with little technical debt but I’ve still had difficulty getting the team to focus on non technical stories. The problem here was of course that we had a lot of distance between ourselves and our true customer and they didn’t really do the prioritisation. So I.T. were left to do whatever they wanted which was changing the build and cool techie stuff.