|
Our solutions can bring you significant productivity gains: - development and defect cost reduction by early bug detection - productivity improvement: time spared with defect management can be invested in better code quality and new feature development - a more efficient development effort allows to shorten time to market, giving you a crucial competitive advantage
|
|
  Download document
ObjectiveTo eliminate everything useless in a source file set. JustificationCode evolution results in an increasing number of code lines. More and more important parts of the code are no longer used but they are spared as a precaution. Precious time can be wasted, trying to understand and correct source files that are not used anymore. Time gained thanks to the elimination of all useless components can be reinvested in new developments. LanguagesC, C++ … Controls• Research of useless files
• Research of useless « includes »
• Research of sub programs never called
• Research of unused variables
• Research of dead code
• Research of duplicate code that could be factorized ToolsIBM Rational Logiscope RuleChecker, IBM Rational Logiscope QualityChecker and IBM Rational Logiscope CodeReducer. Material
Delivery of a report identifying all useless parts in the code, and all factorizable components. |
|
Download document ObjectiveAudit of source code of representative applications in order to detect bad programming practices potentially impacting final quality (maintenability, feasability, portability...).
JustificationAn audit of programming practices points out defects common to many developers. It then becomes possible, with the consent of the persons involved, to implement solutions to prevent these defects.
Languages C, C++, ADA, Java …
Controls The following items are examined :
• Sub-program complexity
• Application architecture
• Modularity
• Comments
• Control flow structure
Material
Detailed report about programming habits, with improvement suggestions. |
|
|
Download document ObjectiveResearch of objects not identified by programmers. JustificationDuring the application design phase and especially during maintenance, developers don't always identify the most relevant objects. As a result, we can find the same verifications duplicated in several sub-programs with the same parameter sets. For example, if 10 sub-programs have for parameters "name", "first name" and "age", and if each of them begins with the verification of age validity, then it will be preferable to create an object "person" with the associated attributes "name", "first name" and "age". The application will be more simple. Langages C, C++, ADA, Java, C# Controls• Search of sub-programs with identical parameter sets • Search of identical verifications in several sub-programs. Tool used
IBM Rational Logiscope RuleChecker MaterialReport describing objects to be introduced in the application to simplify it. The list of sub-programs impacted and the description of expected functions for new objects are provided. |
|
|
|
|
|
Boost yout productivity
