Conference Paper

Improving Quality of Functional Requirements by Measuring Their Functional Size

DOI: 10.1007/978-3-540-89403-2_24 Conference: Software Process and Product Measurement, International Conferences: IWSM 2008, Metrikon 2008, and Mensura 2008, Munich, Germany, November 18-19, 2008. Proceedings
Source: DBLP


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.

Download full-text


Available from: Alain Abran
  • [Show abstract] [Hide abstract]
    ABSTRACT: The complexity of today's software systems is constantly increasing. As a result, requirements for these systems become more comprehensive and complicated. In this setting, requirements engineers struggle to capture consistent and complete requirements of high quality. We propose a feedback-centric requirements editor to help analysts controlling the information overload. Our HeRA tool provides analysts with important data from various feedback facilities. The feedback is directly given based on the input to the editor. On the one hand, it is based on heuristic rules, on the other hand, on automatically derived models. Thus, when new requirements are added, the analyst gets important information on how consistent these requirements are with the existing ones.
    No preview · Conference Paper · Jan 2009
  • [Show abstract] [Hide abstract]
    ABSTRACT: Nowadays, is widely accepted that functional size measurement is essential to manage and control software projects. In order to obtain early indicators for software projects, many functional size measurement procedures have been developed to measure the functional size of conceptual models. To do this, the measurement procedures assume that models do not present defects. However, this is an unreal assumption because, in practice, the conceptual models can have defects that may affect the implementation of final applications. This is especially important for software production processes based on MDD technology, where the conceptual models are key artifacts used as inputs in the process of code generation. Therefore, this paper presents how a functional size measurement procedure (which has been developed for the measurement of conceptual models of a specific MDD environment) can help in the detection of defects in conceptual models.
    No preview · Conference Paper · Jan 2009
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: This paper discusses the challenges of inexperienced measurers in measuring the functional size measurement method of software requirements. More specifically, this paper describes an experiment with the same requirements document measured independently by several inexperienced measurers using the COSMIC method – ISO 19761. Detailed measurement data is analyzed to identify challenges faced by measurers through observed differences, including an analysis of the defects found in the requirements documents and a discussion of the impact of these defects on the measurement results.
    Full-text · Conference Paper · Nov 2009
Show more