Managing Constant Flow of Requirements: Screening Challenges in Very Large-Scale Requirements Engineering

  • Sanja Aaramaa
  • Tuomo Kinnunen
  • Jari Lehto
  • Nebojša Taušan
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7983)


Market-driven software development has been the dominant context in Very Large-Scale Requirements Engineering (VLSRE) research. This case reveals screening as a VLSRE practice in the development context which has characteristics both of market- and customer-driven software development. Requirements are received as a continuous high rate flow. The exploratory industrial case study was conducted to clarify a current practice to manage the inflow of requirements. As a result, a description of the requirement screening process (RS) is provided and practical management challenges related to the process are analysed. This case study provides insight into the requirement screening practice beyond the market-driven software development domain and thus extends the current VLSRE literature.


Very Large-Scale Requirements Engineering VLSRE product management industrial case requirement screening 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Aurum, A., Wohlin, C.: The Fundamental Nature of Requirements Engineering Activities as a Decision Making Process. Information and Software Technology 45, 945–954 (2003)CrossRefGoogle Scholar
  2. 2.
    Carlshamre, P.: Release Planning in Market-Driven Software Product Development: Provoking an Understanding. Requirements Engineering 7(3), 139–151 (2002)CrossRefGoogle Scholar
  3. 3.
    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)CrossRefGoogle Scholar
  4. 4.
    Nattoch Dag, J., Regnell, B., Carlshamre, P., Andersson, M., Karlsson, J.: A Feasibility Study of Automated Natural Language Requirements Analysis in Market-Driven Development. Requirements Engineering 7(1), 20–33 (2002)CrossRefGoogle Scholar
  5. 5.
    Bjarnason, E., Wnuk, K., Regnell, B.: Requirements are slipping through the gaps — A case study on causes & effects of communication gaps in large-scale software development. In: 19th IEEE International Requirements Engineering Conference (RE), pp. 37–46 (2011)Google Scholar
  6. 6.
    Regnell, B., Beremark, P., Eklundh, O.: A market-driven requirements engineering process: Results from an industrial process improvement programme. Requirements Engineering 3(2), 121–129 (1998)CrossRefGoogle Scholar
  7. 7.
    Regnell, B., Karlsson, L., Höst, M.: An Analytical Model for Requirements Selection Quality Evaluation in Product Development. In: 11th IEEE International Requirements Engineering Conference, pp. 254–263 (2003)Google Scholar
  8. 8.
    Bjarnason, E., Wnuk, K., Regnell, B.: Are you biting off more you can chew? A case study on causes and effects of overscoping in large-scale software engineering. Information and Software Technology 54(10), 1107–1124 (2012)CrossRefGoogle Scholar
  9. 9.
    Gorschek, T., Gomes, A., Pettersson, A., Torkar, R.: Introduction of a process maturity model for market-driven product management and requirements engineering. J. of Softw. Evol. and Proc. 24(1), 83–113 (2012)CrossRefGoogle Scholar
  10. 10.
    Wnuk, K., Regnell, B., Schrewelius, C.: Architecting and Coordinating Thousands of Requirements – An Industrial Case Study. In: Glinz, M., Heymans, P. (eds.) REFSQ 2009 Amsterdam. LNCS, vol. 5512, pp. 118–123. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  11. 11.
    Soffer, P., Leah, G., Tsvi, K.: A Unified RE Approach for Software Product Evolution: Challenges and research agenda. In: Ralyté, Å.P.J., Kraiem, N. (eds.) Proceedings of Situational Requirements Engineering Processes, Paris (2005)Google Scholar
  12. 12.
    Potts, C.: Invented Requirements and Imagined Customers: Requirements Engineering for Off-The-Shelf Software. In: Proceedings of the Second IEEE International Symposium on Requirements Engineering (1995)Google Scholar
  13. 13.
    Wieringa, R.: Requirements engineering: frameworks for understanding. John Wiley & Sons (1996)Google Scholar
  14. 14.
    Sawyer, P., Sommerville, I., Kotonya, G.: Improving market-driven RE process. In: Oivo, M., Kuvaja, P. (eds.) International Conference on Product Focused Software Process Improvement, Oulu, vol. 195, pp. 222–236 (1999)Google Scholar
  15. 15.
    Bray, I.: An Introduction to Requirements Engineering, 1st edn. Addison Wesley (2002)Google Scholar
  16. 16.
    Barneya, S., Aurum, A., Wohlin, C.: A product management challenge: Creating software product value through requirements selection. Journal of Systems Architecture 5(6) (2008)Google Scholar
  17. 17.
    Runeson, P., Höst, M.: Guidelines for conducting and reporting case study method in software engineering. Empirical Software Engineering 14(22), 131–164 (2009)CrossRefGoogle Scholar
  18. 18.
    Skoglund, M., Runeson, P.: Reference-based search strategies in systematic reviews. In: Proceedings of the 13th International Conference on Evaluation and Assessment in Software Engineering, pp. 31–40 (2009)Google Scholar
  19. 19.
    Bjarnason, E., Wnuk, K., Regnell, B.: Overscoping: Reasons and consequences — A case study on decision making in software product management. In: Fourth International Workshop on Software Product Management (IWSPM), pp. 30–39 (2010)Google Scholar
  20. 20.
    Bjarnason, E., Wnuk, K., Regnell, B.: A case study on benefits and side-effects of agile practices in large-scale requirements engineering. In: Proceedings of the 1st Workshop on Agile Requirements Engineering, New York (2011)Google Scholar
  21. 21.
    Davis, A.: The art of requirements triage. Computer 36(3), 42–49 (2003)CrossRefGoogle Scholar
  22. 22.
    Ebert, C.: Requirements before the requirements: understanding the upstream impacts. In: 13th IEEE International Conference on Requirements Engineering, pp. 117–124 (2005)Google Scholar
  23. 23.
    Martin, S., Aurum, A., Jeffery, R., Paech, B.: Requirements engineering process models in practice. In: Proceedings of the Seventh Australian Workshop in Requirements Engineering, Melbourne (2002)Google Scholar
  24. 24.
    Ruhe, G., Saliu, M.: The Art and Science of Software Release Planning. Software 22, 47–53 (2005)CrossRefGoogle Scholar
  25. 25.
    Karlsson, L., Thelin, T., Regnell, B., Berander, P., Wohlin, C.: Pair-wise comparisons versus planning game partitioning—experiments on requirements prioritisation techniques. Empirical Software Engineering 12(1), 3–33 (2007)CrossRefGoogle Scholar
  26. 26.
    Ruhe, G., Eberlein, A., Pfahl, D.: Trade-Off Analysis for Requirements Selection. International Journal of Software Engineering and Knowledge Engineering 13(4), 345–366 (2004)CrossRefGoogle Scholar
  27. 27.
    Gubrium, J., Holstein, J.: Handbook of Interview Research. Context & Method. Sage Publications, Thousand Oaks (2002)Google Scholar
  28. 28.
    Kelanti, M., Lehto, J., Aaramaa, S., Kuvaja, P.: A Practice for Recording Problem and Solution Domain Requirements in VLSRE. In: 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA), pp. 323–326 (2012)Google Scholar
  29. 29.
    Liang, P., Avgeriou, P., He, K., Xu, L.: From collective knowledge to intelligence: pre-requirements analysis of large and complex systems. In: Proceedings of the 1st Workshop on Web 2.0 for Software Engineering, Cape Town, pp. 26–30 (2010)Google Scholar
  30. 30.
    Boutkova, E.: Experience with Variability Management in Requirement Specifications. In: 15th International Software Product Line Conference (SPLC), pp. 303–312 (2011)Google Scholar
  31. 31.
    Miles, M., Huberman, M.: Qualitative data analysis: a sourcebook of new methods. Sage Publications (1984)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Sanja Aaramaa
    • 1
  • Tuomo Kinnunen
    • 2
  • Jari Lehto
    • 3
  • Nebojša Taušan
    • 1
  1. 1.Department of Information Processing Science, M-GroupUniversity of OuluOuluFinland
  2. 2.Department of Industrial Engineering and ManagementUniversity of OuluOuluFinland
  3. 3.Nokia Siemens NetworksNokia Siemens Networks OyFinland

Personalised recommendations