Field study on requirements engineering: Investigation of artefacts, project parameters, and execution strategies

  • Authors:

  • Daniel Méndez Fernández;Stefan Wagner;Klaus Lochmann;Andrea Baumann;Holger de Carne

  • Affiliations:

  • Software & Systems Engineering, Institut füür Informatik, Technische Universität München, Boltzmannstr. 3, 85748 Garching, Germany;Software Engineering Group, Institute of Software Technology, University of Stuttgart, Universitätsstr. 38, 70569 Stuttgart, Germany;Software & Systems Engineering, Institut füür Informatik, Technische Universität München, Boltzmannstr. 3, 85748 Garching, Germany;Fakultät für Elektrotechnik und Technische Informatik, Universität der Bundeswehr München, Werner-Heisenberg-Weg 39, 85577 Munich, Germany;Capgemini Technology Service Deutschland, Carl-Wery-Str. 42, 81739 Munich, Germany

  • Venue:
  • Information and Software Technology
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

Context: Requirements Engineering (RE) is a critical discipline mostly driven by uncertainty, since it is influenced by the customer domain or by the development process model used. Volatile project environments restrict the choice of methods and the decision about which artefacts to produce in RE. Objective: We aim to investigate RE processes in successful project environments to discover characteristics and strategies that allow us to elaborate RE tailoring approaches in the future. Method: We perform a field study on a set of projects at one company. First, we investigate by content analysis which RE artefacts were produced in each project and to what extent they were produced. Second, we perform qualitative analysis of semi-structured interviews to discover project parameters that relate to the produced artefacts. Third, we use cluster analysis to infer artefact patterns and probable RE execution strategies, which are the responses to specific project parameters. Fourth, we investigate by statistical tests the effort spent in each strategy in relation to the effort spent in change requests to evaluate the efficiency of execution strategies. Results: We identified three artefact patterns and corresponding execution strategies. Each strategy covers different project parameters that impact the creation of certain artefacts. The effort analysis shows that the strategies have no significant differences in their effort and efficiency. Conclusions: In contrast to our initial assumption that an increased effort in requirements engineering lowers the probability of change requests or project failures in general, our results show no statistically significant difference between the efficiency of the strategies. In addition, it turned out that many parameters considered as the main causes for project failures can be successfully handled. Hence, practitioners can apply the artefact patterns and related project parameters to tailor the RE process according to individual project characteristics.