Information Flow Between Requirement Artifacts. Results of an Empirical Study

  • Stefan Winkler
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4542)


Requirements engineering is still an area of software engineering in which theory and practice greatly differ. This work presents the results of an empirical study of artifacts created and used in the requirements engineering process. We discover that meeting notes and lists of requirements are most commonly used, that they usually play the role of information sources, and that specification documents are information sinks. Furthermore we show that most projects create several different artifacts. Finally we find out that despite the quality risks, inconsistencies between artifacts are often accepted.


empirical study requirements engineering requirements traceability requirements documentation requirements artifacts 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Sommerville, I., Sawyer, P.: Requirements Engineering – a good practice guide. John Wiley & Sons Ltd, New York (1997)MATHGoogle Scholar
  2. 2.
    Sommerville, I., Ransom, J.: An Empirical Study of Industrial Requirements Engineering Process Assessment and Improvement. ACM Transactions on Software Engineering and Methodology 14(1), 85–117 (2005)CrossRefGoogle Scholar
  3. 3.
    IEEE: Guide to Software Requirements Specification, ANSI/IEEE Std 830-1984 (1984)Google Scholar
  4. 4.
    Cleland-Huang, J., Chang, C.K., Christensen, M.: Event-based traceability for managing evolutionary change. IEEE Transactions on Software Engineering 29(9), 796–810 (2003)CrossRefGoogle Scholar
  5. 5.
    Gorschek, T., Svahnberg, M.: Requirements Experience in Practice: Studies of Six Companies. In: Engineering and Managing Software Requirements, pp. 405–426. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  6. 6.
    Paech, B., Koenig, T., Borner, L., Aurum, A.: An Analysis of Empirical Requirements Engineering Survey Data. In: Engineering and Managing Software Requirements, pp. 427–452. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  7. 7.
    Gotel, O.C.Z., Finkelstein, A.C.W.: An analysis of the requirements traceability problem. In: Proceedings of the First International Conference on Requirements Engineering, pp. 94–101 (1994)Google Scholar
  8. 8.
    Ramesh, B., Jarke, M.: Towards reference models for requirements traceability. IEEE Transactions on Software Engineering 27(1), 58–93 (2001)CrossRefGoogle Scholar
  9. 9.
    Forward, A., Lethbridge, T.C.: The Relevance of Software Documentation, Tools and Technologies: a Survey. In: DocEng ’02: Proceedings of the 2002 ACM symposium on Document engineering, pp. 26–33. ACM Press, New York (2002)CrossRefGoogle Scholar
  10. 10.
    Lethbridge, T.C., Singer, J., Forward, A.: How Software Engineers Use Documentation: The State of the Practice. IEEE Software 20(6), 35–39 (2003)CrossRefGoogle Scholar
  11. 11.
    Nikula, U., Sajaniemi, J., Kälviäinen, H.: A State-of-the-Practice Survey on Requirements Engineering in Small-and Medium-Sized Enterprises. Technical report, Telecom Business Research Center Lappeenranta (2000),
  12. 12.
    Neill, C.J., Laplante, P.A.: Requirements Engineering: the State of the Practice. IEEE Software 20(6), 40–45 (2003)CrossRefGoogle Scholar
  13. 13.
    Juristo, N., Moreno, A., Silva, A.: Is the European Industry Moving Toward Solving Requirements Engineering Problems? IEEE Software 19(6), 70–77 (2002)CrossRefGoogle Scholar
  14. 14.
    Boehm, B.: Software Engineering Economics. Prentice-Hall, Englewood Cliffs (1981)MATHGoogle Scholar

Copyright information

© Springer Berlin Heidelberg 2007

Authors and Affiliations

  • Stefan Winkler
    • 1
  1. 1.FernUniversität in Hagen, 58084 HagenGermany

Personalised recommendations