# Thread: How to analyse metrics.

1. ## How to analyse metrics.

Hi,

Can anyone explain how to analyze the metrics collected on Peer Reviews,Code Walkthroughs and Unit testing ,which represents the Measurement & Analysis Process Area in CMMI.

Is there any range value to predict the analysis like 2 defects/KLOC etc...Kindly help me.

Saritha.

2. ## Re: How to analyse metrics.

Hi,

Well..this ques of urs needs a lot of explanation to do..but i can give u small scenario...

Peer Review - U can gather various information during this phase...as far as testing is concerned..our role would be limited with that of the PS Review, TestCase Review, Test Plan Review, Test Script Review, Test Data Review etc...Soo on doing an peer review of such docs u can measure and gather the quality of the item by way of detecting defects...

Code Walkthrough - Whitebox Testing as it is known as ..would help us to detect a lot of defects in the early part of the SDLC...it may also be done in the Unit Testing phase by the development team...

Well speaking of formulas..I know that we do have a lot but am unable to recall the same..

Hope the above may solve ur query to an extent!

3. ## Re: How to analyse metrics.

Hi Saritha,

The following is the table that they have given in the SEI site regarding the Quality Profile Dimentions.

In that they have given some details about avg defets/KLOC in a Quality Product check this out.

Design/Code Time
The ratio of detailed design to coding time - when engineers do not take the time to produce a thorough design, they generally make more design errors. To reduce this risk, design time should equal at least 100% of coding time.

/Ct >= 1.0: P1 = 1, Dt/Ct < 1.0, P1 = Dt/Ct

Code Review Time
The time spent in code review, compared with coding time - by doing a personal code review before they compile, engineers can find a large percentage of their defects. A thorough code review should take 50% or more of coding time.

CRt/Ct >= 0.5: P2 = 1, CRt/Ct < 0.5: P2 = CRt/Ct

Compile Defects/ KLOC

The defects per KLOC found in compile - even with good review times and rates, the review still could have missed a lot of defects. For quality products, compile defects should be less than 10 defects/KLOC.

CompD <= 10, P3 = 1, CompD > 10: P3 = 20/(CompD+10)

Design Review Time
Detailed design review time, related to detailed design time - a thorough detailed design review should take 50% or more of the time spent in detailed design. Anything less generally indicates an inadequate review.

DRt/Dt >=0.5: P4 = 1, DRt/Dt < 0.5: P4 = DRt/Dt

Unit Test Defects/ KLOC
The defects per KLOC found in unit test - the number of defects found in unit test is one of the best indicators of the number that will later be found. When the unit test defects/KLOC exceed 5, subsequent problems are likely.

UTD <= 5: P5 = 1, UTD > 5: P5 = 10/(UTD+5)

http://www.sei.cmu.edu/publications/...ch/tables.html
http://www3.telus.net/ssolie/psp-glossary.html

Hope it helps.

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.