Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword or section
Like this
1Activity
P. 1
How statical analysis can help you reduce testing process for Java software

How statical analysis can help you reduce testing process for Java software

Ratings: (0)|Views: 90 |Likes:
Published by julien_liabeuf
Source code analysis usually help you improve software quality, but it can also allow you to reduce the validation process thanks to more efficient risk based testing
Source code analysis usually help you improve software quality, but it can also allow you to reduce the validation process thanks to more efficient risk based testing

More info:

Published by: julien_liabeuf on Mar 01, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/01/2011

pdf

text

original

 
 
This document is a sample audit report produced automaticallyfrom the results of the analysis of the application on the Kalistick platform.It does not include any specific comments on the results. Its purpose is to serve as a model to build custom reports,it illustrates the ability of the platform to render a clearand comprehensible quality of an application.  
This document is confidential and is the property of Kalistick.
It should not be circulated or modified without permission.Kalistick
13 av Albert EinsteinF-69100 Villeurbanne+33 (0) 486 68 89 42contact@kalistick.com
I
CE
S
CRUM
 Application I
CE
S
CRUM
2 Audit Report
2010-02-10
 
 
Code audit of 
IceScrum2
application         2010-02-10
 
 
Confidential 
– 
This document is the property of Kalistick   2/58
 
1
 
Executive Summary
The Quality Cockpit uses static analysis techniques: it does not execute the application, but analyzes theelements that compose it (code, test results, architecture ...). The results are correlated, aggregated andcompared within the project context to identify risks related to quality. This report presents the results.  
Variation compared to the objective
  This chart compares the current status of the project to the objectives set for each quality factor. The goal, set at the initialization of the audit,represents the importance of each quality factor. It is intended to define the rules to follow duringdevelopment and the accepted tolerance.
 
 
 
Rate of overall non-compliance 
This gauge shows the overall level of quality of theapplication compared to its objective. It displays thepercentage of the application (source code)regarded as not-compliant. According to the adopted configuration, a ratehigher than 15% indicates the need for further analysis.
 
 
 
Origin of non-compliances
 This graph identifies the technical origin of detected non-compliances, and the main areas of improvement. According to elements submitted for the analysis,some quality domains may not be evaluated.
 
 
Code audit of 
IceScrum2
application         2010-02-10
 
 
Confidential 
– 
This document is the property of Kalistick   3/58
 
Report Organization
This report presents the concepts of Quality Cockpit, the goal and the associated technical requirementsbefore proceeding with the summary results and detailed results for each technical area.
 
............................................................................................................................... 42.2 The analytical ........................................................................................................................................ 43 Quality objective........................................................................................................................................... 73.1 The quality profile ................................................................................................................................ 73.2 The technical requirements ................................................................................................................. 74 Summary of results ..................................................................................................................................... 104.1 Project status ...................................................................................................................................... 104.2 Benchmarking ..................................................................................................................................... 134.3 Modeling application .......................................................................................................................... 175 Detailed results ........................................................................................................................................... 195.1 Detail by quality factors...................................................................................................................... 195.2 Implementation .................................................................................................................................. 205.3 Structure ............................................................................................................................................. 245.4 Test ..................................................................................................................................................... 315.5 Architecture ........................................................................................................................................ 385.6 Duplication ......................................................................................................................................... 395.7 Documentation ................................................................................................................................... 416 Action Plan .................................................................................................................................................. 437 Glossary ...................................................................................................................................................... 458 Annex .......................................................................................................................................................... 478.1 Cyclomatic complexity ........................................................................................................................ 478.2 The coupling ....................................................................................................................................... 498.3 TRI and TEI .......................................................................................................................................... 508.4 Technical Requirements ..................................................................................................................... 52  

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->