For many years, the software industry has been applying different types of reviews on their requirements documents to identify and remove defects that would otherwise propagate in the development life cycle, leading to rework and extra cost to fix at later phases. An inspection is a review technique known to be efficient at identifying defects but, like any other review technique, it does not guarantee that all defects are found. Requirements documents are also used as input for the measurement of the software size for estimation purposes; when carrying this measurement process, practitioners have often noticed defects in the requirements.
This paper reports on a research project investigating the contribution of the measurers in finding defects in requirements documents. More specifically, this paper describes an experiment where the same requirements document was inspected by a number of inspectors as well as by a number of measurers; the number and types of defects found by both inspectors and measurers are compared and discussed. For this experiment, the measurers used the COSMIC --- ISO 19761 to measure the functional size and find defects. Results show significant increase in defects identification when both inspection and functional size measurement are used to find and report defects.
[1]
Marc Roper,et al.
Software inspections
,
2003,
Adv. Comput..
[2]
Thomas Gilb,et al.
Software Inspection
,
1994
.
[3]
David Mason.
UML and the Unified Process
,
2004
.
[4]
Karl E. Wiegers,et al.
Peer Reviews in Software: A Practical Guide
,
2001
.
[5]
Kevin Barraclough,et al.
I and i
,
2001,
BMJ : British Medical Journal.
[6]
J. M. Singer,et al.
IEEE Recommended Practice for Software Requirements SpeciÞcations
,
1993
.
[7]
Jim Arlow,et al.
UML 2.0 and the Unified Process: Practical Object-Oriented Analysis and Design (2nd Edition)
,
2005
.