Abstract
[Context and motivation] This paper reports the results and lessons learned of a requirements engineering improvement project conducted in a Siemens business unit. [Question/problem] In particular, the project addressed the following major problems: (i) communication gap between marketing and development, resulting in misbalance between technology-driven and market-driven requirements; (ii) limited value of monolithic requirements specifications, resulting in inconsistencies across product versions; (iii) requirements overloading, resulting in cumbersome and time consuming descoping; (iv) insufficient traceability, resulting in poor or missing impact analysis, regression testing and other traceability errors; (v) intransparent mapping between a non-hierarchical topology of problem space artifacts to hierarchically structured solution space artifacts; (vi) missing support for platform variant management and reuse, resulting in long release cycles; (vii) waterfall process, resulting in inability to effectively handle change in requirements or design. [Principal ideas/results] The paper describes the situation at the business unit before the process improvement project, gives a short overview on how the project was implemented and the techniques applied to solve the various problems the organization was facing. The paper wraps up with a comparison between the initial and the final state of the requirements engineering process in the organization and finally, a lessons learned section discusses some of the highlights and pitfalls encountered during the project. [Contribution] The paper can be used as an initial point of reference to other practitioners and organizations facing similar problems and/or involved in similar improvement projects.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Boehm, B.W.: Software Engineering Economics. Prentice-Hall PTR, Englewood Cliffs (1981)
Rainer, S., Hall, A., Beecham, T.: Requirements problems in twelve software companies: an empirical analysis. IEEE Proceedings Software 149 (2002)
Software process improvement on the right road with espiti - the espiti european survey results (1996)
Gorschek, T., Wohlin, C.: Requirements abstraction model. Requirements Engineering Journal 11, 79–101 (2006)
Robertson, J., Robertson, S.: Requirements-Led Project Management. Addison-Wesley, Reading (2005)
Kroll, P., Kruchten, P.: The Rational Unified Process made easy: A practitioner’s guide to the RUP. Addison-Wesley Professional, Boston (2003)
Geisberger, E., Broy, M., Berenbach, B., Kazmeier, J., Paulish, D., Rudorfer, A.: Requirements Engineering Reference Model (REM). Technical report, Technischer Bericht, Technische Universitart Muenchen (2006)
Eriksson, M., Brstler, J., Borg, K.: Software product line modeling made practical. Communications of the ACM 49, 49–54 (2006)
Berenbach, B., Paulish, D.J., Kazmeier, J., Rudorfer, A.: Software & Systems Requirements Engineering: In Practice. The McGraw-Hill Companies, New York (2009)
van Lamsweerde, A.: Goal-oriented requirements engineering: a guided tour. In: Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, pp. 249–262 (2001)
Jarke, M., Pohl, K.: Vision-Driven Requirements Engineering. In: Proc. IFIP WG8. 1 Working Conference on Information System Development Process, pp. 3–22
Dardenne, A., Fickas, S., van Lamsweerde, A.: Goal-directed concept acquisition in requirements elicitation. In: IWSSD 1991: Proceedings of the 6th International Workshop on Software Specification and Design, pp. 14–21. IEEE Computer Society Press, Los Alamitos (1991)
Lapouchnian, A.: Goal-oriented requirements engineering: An overview of the current research. Technical report, University of Toronto (2005)
Hoffmann, A.: Requirements Pyramid. In: EuroPLop 2010, Irsee, Germany, July 7 (2010) (accepted)
Vici, A.D., Argentieri, N., Mansour, A., d’ Alessandro, M., Favaro, J.: Fodacom: An experience with domain analysis in the italian telecom industry. In: Proceedings of the Fifth International Conference on Software Reuse 1998, pp. 166–175 (2004)
Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall PTR, Englewood Cliffs (2001)
Kang, K.C., Kim, S., Lee, J., Kim, K., Shin, E., Huh, M.: Form: A feature-;oriented reuse method with domain-specific reference architectures. Annals of Software Engineering 5, 143–168 (1998)
Griss, M.L., Favaro, J., d’ Alessandro, M.: Integrating feature modeling with the rseb. In: ICSR 1998: Proceedings of the 5th International Conference on Software Reuse, p. 76. IEEE Computer Society, Washington, DC, USA (1998)
Krzysztof, C., Eisenecker, U.: Generative Programming: Methods, Tools, and Applications (2000)
Kang, P., Jaejoon, K.C., Donohoe, L.: Feature-oriented product line engineering. IEEE Software 19, 58–65 (2002)
Streitferdt, D.: Family-oriented requirements engineering. PhD thesis, Technical University Ilmenau (2004)
Beuche, D.: Composition and Construction of Embedded Software Families. PhD thesis, University of Magdeburg (2003)
Nuseibeh, B.: Weaving together requirements and architectures. IEEE Xplore 34, 115–119 (2001)
Broy, M., Slotosch, O.: From requirements to validated embedded systems. In: Henzinger, T.A., Kirsch, C.M. (eds.) EMSOFT 2001. LNCS, vol. 2211, pp. 51–65. Springer, Heidelberg (2001)
Brinkkemper, S., van de Weerd, I., Saeki, M., Versendaal, J.: Process improvement in requirements management: A method engineering approach. In: Rolland, C. (ed.) REFSQ 2008. LNCS, vol. 5025, pp. 6–22. Springer, Heidelberg (2008)
Damian, D., Zowghi, D., Vaidyanathasamy, L., Pal, Y.: An industrial study of immediate benefits of requirements engineering process improvement at the australian center for unisys software. Empirical Software Engineering 9, 45–75 (2004)
Palyagar, B.: A framework for validating process improvement in requirements engineering. In: First International Workshop on Requirements Engineering Visualization, REV 2006 (2006)
Hemmer, S.: Identifikation von Schwächen im Requirements-Engineering-Prozess anhand eines Bewertungsmodels (unpublished master’s thesis). Fakultaet Elektrotechnik/Informatik, Hochschule Coburg (available through the faculty archive) (2010)
Loy, P.H.: A comparison of object-oriented and structured development methods. ACM SIGSOFT Software Engineering Notes 15, 44–48 (1990)
Pettersson, F., Ivarsson, M., Gorschek, T., Ohman, P.: A practitioner’s guide to light weight software process assessment and improvement planning. Journal of Systems and Software 81(6), 972–995 (2008)
Savolainen, J., Vehkomaki, T., Mannion, M.: An Integrated Model for Requirements Structuring and Architecture Design. In: Proceedings of the Seventh Australian Workshop on Requirements Engineering, Melbourne. Citeseer (2002)
Bodker, S.: Creating conditions for participation: Conflicts and resources in systems development. Human-Computer Interaction 11, 215–236 (1996)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Markov, G.A., Hoffmann, A., Creighton, O. (2011). Requirements Engineering Process Improvement: An Industrial Case Study. In: Berry, D., Franch, X. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2011. Lecture Notes in Computer Science, vol 6606. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19858-8_4
Download citation
DOI: https://doi.org/10.1007/978-3-642-19858-8_4
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-19857-1
Online ISBN: 978-3-642-19858-8
eBook Packages: Computer ScienceComputer Science (R0)