An Industrial Case Study on Measuring the Quality of the Requirements Scoping Process

  • Krzysztof WnukEmail author
  • Markus Borg
  • Sardar Muhammad Sulaman
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10027)


Decision making and requirements scoping occupy central roles in helping to develop products that are demanded by the customers and ensuring company strategies are accurately realized in product scope. Many companies experience continuous and frequent scope changes and fluctuations but struggle to measure the phenomena and correlate the measurement to the quality of the requirements process. We present the results from an exploratory interview study among 22 participants working with requirements management processes at a large company that develops embedded systems for a global market. Our respondents shared their opinions about the current set of requirements management process metrics as well as what additional metrics they envisioned as useful. We present a set of metrics that describe the quality of the requirements scoping process. The findings provide practical insights that can be used as input when introducing new measurement programs for requirements management and decision making.


Requirements engineering Software metrics Process improvement 



This work is supported by the IKNOWDM project from the Knowledge Foundation in Sweden (20150033).


  1. 1.
    Ambriola, V., Gervasi, V.: Process metrics for requirements analysis. In: Conradi, R. (ed.) EWSPT 2000. LNCS, vol. 1780, pp. 90–95. Springer, Heidelberg (2000). doi: 10.1007/BFb0095017 CrossRefGoogle Scholar
  2. 2.
    Costello, R.J., Liu, D.-B.: Metrics for requirements engineering. J. Syst. Softw. 29(1), 39–63 (1995)CrossRefGoogle Scholar
  3. 3.
    Feyh, M., Petersen, K.: Lean software development measures and indicators - a systematic mapping study. In: Fitzgerald, B., Conboy, Kieran, Power, K., Valerdi, R., Morgan, L., Stol, K.-J. (eds.) LESS 2013. LNBIP, vol. 167, pp. 32–47. Springer, Heidelberg (2013). doi: 10.1007/978-3-642-44930-7_3 CrossRefGoogle Scholar
  4. 4.
    Hood, C., Wiedemann, S., Fichtinger, S., Pautz, U.: Requirements Management: The Interface Between Requirements Development and All Other Systems Engineering Processes. Springer, Heidelberg (2007)Google Scholar
  5. 5.
    Höst, M., Regnell, B., Natt och Dag, J., Nedstam, J., Nyberg, C.: Exploring bottlenecks in market-driven requirements management processes with discrete event simulation. J. Syst. Softw. 59(3), 323–332 (2001)CrossRefGoogle Scholar
  6. 6.
    Landis, J.R., Koch, G.G.: The measurement of observer agreement for categorical data. Biometrics 33, 159–174 (1977)MathSciNetCrossRefzbMATHGoogle Scholar
  7. 7.
    Mujtaba, S., Feldt, R., Petersen, K.: Waste and lead time reduction in a software product customization process with value stream maps. In: 21st Australian Software Engineering Conference (ASWEC), pp. 139–148 (2010)Google Scholar
  8. 8.
    Petersen, K., Wohlin, C.: Measuring the flow in lean software development. Softw. Pract. Exp. 41, 975–996 (2010)CrossRefGoogle Scholar
  9. 9.
    Pohl, K., Böckle, G., van der Linden, F.J.: Software Product Line Engineering: Foundations, Principles and Techniques. Springer, New York (2005)CrossRefzbMATHGoogle Scholar
  10. 10.
    Regnell, B., Svensson, R.B., Wnuk, K.: Can we beat the complexity of very large-scale requirements engineering? In: Paech, B., Rolland, C. (eds.) REFSQ 2008. LNCS, vol. 5025, pp. 123–128. Springer, Heidelberg (2008). doi: 10.1007/978-3-540-69062-7_11 CrossRefGoogle Scholar
  11. 11.
    Runeson, P., Höst, M., Rainer, A., Regnell, B.: Case Study Research in Software Engineering Guidelines and Examples. John Wiley & Sons, Hoboken (2012)CrossRefGoogle Scholar
  12. 12.
    The interview instrument can be accessed at
  13. 13.
    Wnuk, K., Gorschek, T., Callele, D., Karlsson, E.-A., Regnell, B., Ahlin, E.: Supporting scope tracking and visualization for very large-scale requirements engineering-utilizing FSC+, decision patterns, and atomic decision visualizations. IEEE Trans. Softw. Eng. 42, 47–74 (2016)CrossRefGoogle Scholar
  14. 14.
    Wnuk, K., Regnell, B., Karlsson, L.: What happened to our features? Visualization and understanding of scope change dynamics in a large-scale industrial setting. In: 17th IEEE International Requirements Engineering Conference, RE 2009, pp. 89–98 (2009)Google Scholar
  15. 15.
    Wnuk, K., Pfahl, D., Callele, D., Karlsson, E.A.: How can open source software development help requirements management gain the potential of open innovation: an exploratory study. In: ACM-IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM), pp. 271–279 (2012)Google Scholar

Copyright information

© Springer International Publishing AG 2016

Authors and Affiliations

  • Krzysztof Wnuk
    • 1
    Email author
  • Markus Borg
    • 2
  • Sardar Muhammad Sulaman
    • 3
  1. 1.Software Engineering Research Lab, Department of Software EngineeringBlekinge Institute of TechnologyKarlskronaSweden
  2. 2.SICS Swedish ICT ABLundSweden
  3. 3.Department of Computer ScienceLund UniversityLundSweden

Personalised recommendations