Requirements and the way they are dealt with are decisive to the success of a project. This statement is never really questioned in modern software engineering circles. Why is it, then, that a systematic requirements engineering (RE) system is so rarely established? Where do the problems lie when it comes to implementing such a system?
This paper outlines the challenges and how these may be met using the example of the automotive industry.
Click on the file attachment below to read this paper.
About the Author
Michael Gerdom studied computer science at the University of Erlangen-Nuremberg. He has gained several years' practical experience from customer projects in the area of implementing object-oriented technologies and UML in embedded systems environments. He is responsible at method park Software AG for heading the area of Training & Consulting. His current main areas of work as a consultant lie in system and software architecture, as well as in requirements engineering. He is a founding member of the iSQI German Software Architecture Board.
Dr. Uwe Rastofer studied computer science and gained his Ph.D. in it at the University of Erlangen-Nuremberg. He has gained several years' experience as a consultant, trainer, developer and project manager in the area of distributed and embedded systems. His main areas of work at method park are in consulting and training within the fields of requirements engineering, system and software architecture, UML and object-oriented software technologies.
