Requirements Engineering

  • Stefan WiesnerEmail author
  • Margherita Peruzzini
  • Jannicke Baalsrud Hauge
  • Klaus-Dieter Thoben


Requirements engineering (RE) is the key to success or failure of every product, service or system development project, understanding the development results as the implementation of the specific set of requirements. A good requirements definition is thus the prerequisite for high-quality solutions and reduces the cost of change, both of prototypes and production tools, and ultimately the warranty costs. However, RE for system development is more and more challenged by two interrelated trends: the increasing complexity of systems and the responsibility of the provider for the whole system life cycle. Thus, from a systems engineering point of view, RE has to define requirements for a rising amount of tangible and intangible components from a growing number of different stakeholders. Additionally, RE has to take into account requirements from every stage of the system life cycle and feed the results back to the development process. Many organizations are still missing effective practices and a documented RE process to tackle the upcoming challenges in systems engineering. This chapter aims at giving an overview on the RE context and challenges for systems engineering and subsequently describes the state-of-the-art for structuring and processing requirements. Furthermore, two case studies illustrate the current situation and methods for resolution in industry and show how the identified challenges can be met by IT support. Finally, future trends and needs for RE research and its further integration with concurrent engineering and life cycle management approaches are outlined.


Requirements engineering Systems engineering Life cycle management 


  1. 1.
    Corsetti A, Ribeiro EA, Garbi GP, Zanta K, Medeiros M, Loureiro G (2013) Complex systems developed with system concurrent engineering. In: Stjepandić J, Rock G, Bil C (eds) Concurrent engineering approaches for sustainable product development in a multi-disciplinary environment. Proceedings of the 19th ISPE international conference on concurrent engineering. Springer, London, pp 1057–1068Google Scholar
  2. 2.
    Chang W, Yan W, Chen CH (2013) Customer requirements elicitation and management for product conceptualization. In: Stjepandić J, Rock G, Bil C (eds) Concurrent engineering approaches for sustainable product development in a multi-disciplinary environment. Proceedings of the 19th ISPE international conference on concurrent engineering. Springer, London, pp 957–968Google Scholar
  3. 3.
    Kossiakoff A, Sweet WN, Seymour S, Biemer SM (2011) Systems engineering principles and practice, 2nd edn. Wiley, HobokenCrossRefGoogle Scholar
  4. 4.
    Blanchard BS (2012) System engineering management, 4th edn. Wiley, HobokenGoogle Scholar
  5. 5.
    Sage AP, Rouse WB (2009) Handbook of systems engineering and management, 2nd edn. Wiley, HobokenGoogle Scholar
  6. 6.
    Elgh F (2007) Modelling and management of manufacturing requirements in design automation systems. In: Loureiro G et al (eds) Complex systems concurrent engineering. Springer, London, pp 321–328CrossRefGoogle Scholar
  7. 7.
    Nilsson P, Fagerström B (2006) Managing stakeholder requirements in a product modelling system. Comput Ind 57(2):167–177CrossRefGoogle Scholar
  8. 8.
    Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. In: Proceedings of the conference on the future of software engineering, LimerickGoogle Scholar
  9. 9.
    Hauksdóttir D, Mortensen NH, Nielsen PE (2013) Identification of a reusable requirements structure for embedded products in a dynamic market environment. Comput Ind 64(4):351–362CrossRefGoogle Scholar
  10. 10.
    Boehm B, Basili B (2001) Software defect reduction top 10 list. In: IEEE Computer, vol 34(1). IEEE Computer Society, Los Alamitos, pp 135–137Google Scholar
  11. 11.
    Hull E, Jackson K, Dick J (2011) Requirements engineering, 3rd edn. Springer, LondonCrossRefzbMATHGoogle Scholar
  12. 12.
    Royce WW (1970) Managing the development of large software systems. In: Proceedings of IEEE WESCON, vol 26(8)Google Scholar
  13. 13.
    Baxter D, Gao J, Case K, Harding J, Young B, Cochrane S, Dani S (2008) A framework to integrate design knowledge reuse and requirements management in engineering design. Robot Comput-Integr Manuf 24(4):585–593CrossRefGoogle Scholar
  14. 14.
    Christopher DFX, Chnadra E (2012) Analyzing the efficacy of requirements stability based on function point modeling. Int J Eng 1(9)Google Scholar
  15. 15.
    Taheri F, An Duong N (2010) Introducing requirement stability metrics for test case success prediction in RUAG space AB. Rep/Dept Appl Inf Technol 2010:63Google Scholar
  16. 16.
    Fuxin F (2005) Configurable product views based on geometry user requirements. Comput Aided Des 37(9):957–966CrossRefGoogle Scholar
  17. 17.
    Laporti V, Borges MR, Braganholo V (2009) Athena: a collaborative approach to requirements elicitation. Comput Ind 60(6):367–380CrossRefGoogle Scholar
  18. 18.
    Azadegan A, Papamichail KN, Sampaio P (2013) Applying collaborative process design to user requirements elicitation: a case study. Comput Ind 64(7):798–812CrossRefGoogle Scholar
  19. 19.
    Mallek S, Daclin N, Chapurlat V (2012) The application of interoperability requirement specification and verification to collaborative processes in industry. Comput Ind 63(7):643–658CrossRefGoogle Scholar
  20. 20.
    Pohl K (2008) Requirements engineering; Grundlagen, Prinzipien, Techniken. 2. Auflage. dpunkt Verlag, HeidelbergGoogle Scholar
  21. 21.
    Rausch A; Broy M (2007) Das V-Modell XT—Grundlagen, Erfahrungen, Werkzeuge. dpunkt.verlag, HeidelbergGoogle Scholar
  22. 22.
    IEEE Standard 830 (1998) Recommended practice for software requirements specifications. IEEE Press, New YorkGoogle Scholar
  23. 23.
    Versteegen G (2004) Einführung in Anforderungsmanagement. In: Anforderungsmanagement. Springer, Heidelberg, pp 1–37Google Scholar
  24. 24.
    Rupp C (2009) Requirementsengineering und –management; Professionelle, Iterative Anforderungsanalyse für die Praxis, 5th edn. Carl Hanser, München, WienGoogle Scholar
  25. 25.
    Wallmüller E (2001) Software-Qualitätsmanagement in der Praxis – Software-Qualität durch Führung und Verbesserung von Software-Prozessen. Carl Hanser, München, WienGoogle Scholar
  26. 26.
    Liu X, Akinci B, Bergés M, Garrett JH Jr (2013) Extending the information delivery manual approach to identify information requirements for performance analysis of HVAC systems. Adv Eng Inform 27(4):496–505CrossRefGoogle Scholar
  27. 27.
    Hass KB, Wessels DJ, Brennan K (2007) Getting it right: business requirement analysis tools and techniques. Management Concepts Press, ViennaGoogle Scholar
  28. 28.
    Barnes RJ, Gause DC, Way EC (2008) Teaching the unknown and the unknowable in requirements engineering education. In: IEEE Proceedings of the requirements engineering education and training (REET’08). pp 30–37Google Scholar
  29. 29.
    Martin JN (1996) Systems engineering guidebook: a process for developing systems and products, vol 10. CRC Press, Boca RatonGoogle Scholar
  30. 30.
    Young RR (2004) The requirements engineering handbook. Artech House, NorwoodGoogle Scholar
  31. 31.
    Ambrósio AM, Guimarães DC, Barreto JP (2007) Satellite simulator requirements specification based on standardized space services. In: Loureiro G et al (eds) Complex systems concurrent engineering. Springer, London, pp 175–183CrossRefGoogle Scholar
  32. 32.
    Glinz M (2007) On non-functional requirements. In: 15th IEEE international conference on the requirements engineering conference (RE’07), pp 21–26Google Scholar
  33. 33.
    Hause M, Thom F, Moore A (2005) Inside SysML. Comput Control Eng J 16(4):10–15CrossRefGoogle Scholar
  34. 34.
    Haneyah SWA, Schutten JMJ, Schuur PC, Zijm WHM (2013) Generic planning and control of automated material handling systems: practical requirements versus existing theory. Comput Ind 64(3):177–190CrossRefGoogle Scholar
  35. 35.
    Lim SL, Finkelstein A (2011) Anticipating change in requirements engineering. In: Relating software requirements and architectures. Springer, Heidelberg, pp 17–34Google Scholar
  36. 36.
    Team CP (2010) CMMI for Development (CMMI-DEV) vol 1. Technical report CMU/SEI-2006-TR-008Google Scholar
  37. 37.
    Ebert C (2008) Systematisches requirements engineering und management; Anforderungen ermitteln, spezifizieren, analysieren und verwalten. 2. Auflage. dpunkt Verlag, HeidelbergGoogle Scholar
  38. 38.
    Wynn MT, Ouyang C, ter Hofstede AH, Fidge CJ (2011) Data and process requirements for product recall coordination. Comput Ind 62(7):776–786CrossRefGoogle Scholar
  39. 39.
    Huang HZ, Li Y, Liu W, Liu Y, Wang Z (2011) Evaluation and decision of products conceptual design schemes based on customer requirements. J Mech Sci Technol 25(9):2413–2425CrossRefGoogle Scholar
  40. 40.
    Sommerville I (2011) Software engineering, 9th edn. Addison-Wesely, BostonGoogle Scholar
  41. 41.
    Van Lamsweerde A (2009) Requirements engineering: from system goals to UML models to software specificationsGoogle Scholar
  42. 42.
    Project Management Institute, Inc (2013) A guide to the project management body of knowledge (PMBOKSM Guide), 5th edn. PMI, Pennsylvania. ISBN 978-1935589-67-9Google Scholar
  43. 43.
    Carillo de Gea J, Nicolas J, Fernandez Aleman JL, Toval A, Ebert C, Vizcaino A (2011) Requirements engineering tools. IEEE Soft 28:86–91CrossRefGoogle Scholar
  44. 44.
    Massonet P, Van Lamsweerde A (1997) Analogical reuse of requirements frameworks. In: Proceedings of the 3rd IEEE International symposium on requirements engineering, pp 26–37Google Scholar
  45. 45.
    Ebert C, Jastram M (2012) ReqIF: aeamless requirements interchange format between business partners. IEEE Soft 29(5):82–87CrossRefGoogle Scholar
  46. 46.
    IBM (2014) Rational DOORS. Accessed 31 Mar 2014
  47. 47.
    IBM (2012) DXL reference manualGoogle Scholar
  48. 48.
    Gümmer R, Junk C, Rock G (2013) A variant management based methodology for the requirements-engineering process of mechanical parts. In: Stjepandić J, Rock G, Bil C (eds) Concurrent engineering approaches for sustainable product development in a multi-disciplinary environment. Proceedings of the 19th ISPE international conference on concurrent engineering. Springer, London, pp 109–120Google Scholar
  49. 49.
    Peruzzini M, Germani M (2013) Investigating the sustainability of product and product-service systems in the B2C industry. In: Meier H (ed) Product-service integration for sustainable solutions. Lecture notes in production engineering LNPE 6, Springer, Heidelberg, pp 421–434Google Scholar
  50. 50.
    Favi C, Peruzzini M, Germani M (2012) A lifecycle design approach to analyze the eco-sustainability of industrial products and product-service systems. In: DS70 Proceedings of the 12th international design conference DESIGN 2012, Cavtat, 21–24 May, pp 879–888Google Scholar
  51. 51.
    Peruzzini M, Germani M, Favi C (2012) Shift from PLM to SLM: a method to support business requirements elicitation for service innovation. In: Rivest L, Bouras A, Louhichi B (eds) Product lifecycle management. Towards knowledge-rich enterprises, IFIP Advances in information and communication technology 388 (AICT). Springer, New York, pp 111–123Google Scholar
  52. 52.
    Jarke M, Loucopoulos P, Lyytinen K, Mylopoulos J, Robinson W (2011) The brave new world of design requirements. Inf Syst 36(7):992–1008CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2015

Authors and Affiliations

  • Stefan Wiesner
    • 1
    Email author
  • Margherita Peruzzini
    • 2
    • 3
  • Jannicke Baalsrud Hauge
    • 1
  • Klaus-Dieter Thoben
    • 1
  1. 1.BIBA - Bremer Institut für Produktion und Logistik GmbH at the University of BremenBremenGermany
  2. 2.Indesit Company S.p.AFabriano ANItaly
  3. 3.Department of Industrial Engineering and Mathematical SciencesUniversità Politecnica delle MarcheAnconaItaly

Personalised recommendations