we are using traceability metric,
Usage--Mapping the requirement with test cases to check all
the requirement are satisfied.

Hi  Kathiravan,RTM i.e  traceability matrix.i am asking metrics.

plz let me know
thanks

hi i m swapnil uday, 
Its a  mapping document that maps defects with test cases 
and test cases with functional specifications and 
functional specifications with business requirements.In 
order trace back the defects.....
is any doubts plz mail me 
at swapnilingole25@gmail.com
bey thankuuuuuuuuuuuuuuuuu

Hi Uday,

Here what meant by metrics, You collect various data 
related to your project you baseline your project status in 
various activites.... like testcases execution, number of 
tc's passed in a given cycle and so on...

Some of the metrics that you can collect is

Schedule variation : difference b/w planned and actual 
completion of project

Effort Variation

Productivity

Testcases Passes in a project

basically metrics is nothing but an mathematical number 
shows a relation ship between two numbres.in testing there 
are two types of metircs.
1.process metrics
2.product metrics

process metric: a metric used to measure the cheracteristic 
of the methods,technique, and tools employed in 
developing,imlementing,and maintaining the software system.

product metric:metric used to measure the characteristic of 
the documentation and code.

some of the  test metrics are:

1.user paticipation

2.path tested=number os paths tested/total number of paths

3.test cost= test cost Vs total system cost

4.cost to locate defect=test cost/No: of defects located i 
n the testing

5.test automation=cost of manul test effort/total test cost


thnx,
still any doubts mail me ok indu.

Type of matrix depends upon the particulat project.In our 
project(It's a Life Sciences Web based product)following 
quality matrix we use:
(i) Defect Density: Number of defects found per kilo lines 
of code(KLOC)
(ii)MTTR(Mean Time To Repair): Average time required to 
repair a defect after it sis detected.
(iii)Defect Removal Efficiency(DRE): E/(E+D)

 Where, E= Number of errors found before delivery of the 
s/w to the end user
D= Number of defects found after delivery
Ideal value of DRE is 1 i.e. No defects are found in the 
software but in reality D>0

Testing metrics is prepared to track the following 
information for a perticular month/project/release, which 
varies between project and company.

1.Pre-release defect density
2.Post release defect density
3.Individual defect detection 
4.Test review
5.Defect removal efficiency
6.Test case effectiveness
7.Test specification productivity(includes scripting and 
executing)
8.Schedule and effort variance
9.Test progress tracking
Metrics helps to track the above information in 
figures/percentage.