A Framework for Evaluating System and Software Requirements Specification Approaches

A controlled experiment for evaluating a metric-based reading technique for requirements inspection

“…Based on the recommendations proposed in [13] to use the GQM template in experimentation in requirements engineering, the goal definition of our experiment can be summarised as: Analyse the Checklist and MBR techniques for the purpose of evaluating with respect to their efficiency and effectiveness from the point of view of the researcher in the context of Undergraduate Computer Science students enrolled in the fifth-year at the Computer Science School at the University of Seville.…”

“…As Kamsties and Rombach commented in [13], empirical researches can contribute to requirements engineering by evaluating the effectiveness of techniques, methods and tools. In this sense, some empirical researches have been done in the requirements inspection area, all of them designed to compare two or more reading techniques in order to know which of them is better than the other.…”

“…The convenience of early detection of problems in requirements is widely recognized to improve the quality in the software development process [13]. One of the first studies in this sense was that presented in [6], in which Boehm concludes that the later a defect is identified in the life-cycle the more expensive it will be to repair it.…”