|
 Within a more and more complex and challenging environment, the quality of the applications you are developping, buying or using, becomes critical. If you are a software editor, managing the final quality of your products is essential to preserve your current positions, and to get some decisive advantage on emerging new markets. As a final user, you have to face growing demands about productivity, total quality, and processes security. You must be 100% confident in your software tools reliability, and therefore you have to formalize your software requirements, and to be able to check that they are respected in more and more complex applications. Oour solutions help you ti determine, control and optimize software products quality.
|
  Download documentObjectiveResearch of possible programming errors in source files. JustificationSome uses of the specificities of a language can lead to the introduction of bugs in the code (during the development or the maintenance phase). Their early localization allows to avoid many potential defects and to spare time during the validation and software exploitation phases. Languages C, C++ … ControlsSearch for the following defects:
• Instructions without effect
• Unreachable code
• Empty bloc in a test
• « break » missing in a « switch » branch
• « default » missing in a « switch »
• Use of the return of a procedure
• Confusion between assignment and test
• Comparisons of real numbers for equality or difference Tool used
IBM Rational Logiscope RuleChecker Material
Report identifying all dangerous construction uses in the code. |
|
Download document ObjectiveImplementation of a "measurement" repository in order to ensure that coding practices are improving over time on the projects. JustificationOnly measurements can check that improvement procedures really impacts quality of the final production.
A repository allowing to measure how practices are being respected, and to compare it to the final quality obtained, makes improvement much more efficient. LanguagesC, C++, Ada, Java … Service description
Phase 1 : identification of practices to be improved, and of corresponding measurements
Phase 2 : identification of measurements necessary to evaluate the quality of developments (number of defects for example)
Phase 3 : integration of the repository in the development environment
Phase 4 : assessment after 6 months of use ToolKEYS MaterialIntegrated repository in the development environment User's manual |
|
|
Download document Objective Verifying software element coverage during associated test execution. Justification Software non-regression tests only cover half of the code if coverage measurement is not included. Many tests are redundant and many others are missing. The strict verification of coverage is a good way of improving test sets and their efficiency. Languages C, C++, ADA, Java ... Service description Phase 1 : code instrumentation Phase 2 : test execution Phase 3 : test quality report ToolsIBM Rational Logiscope TestChecker, R-TRT, LDRA Testbed, Pure Coverage MaterialDelivery of a report identifying all code portions non-covered by tests, and redundant tests. |
|
|
|
|
|
Secure your investments
