Information Flow Between Requirement Artifacts. Results of an Empirical Study
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.
Keywordsempirical study requirements engineering requirements traceability requirements documentation requirements artifacts
Unable to display preview. Download preview PDF.
- 3.IEEE: Guide to Software Requirements Specification, ANSI/IEEE Std 830-1984 (1984)Google Scholar
- 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
- 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), http://www.cs.ucl.ac.uk/research/renoir/TBRC_RR01.pdf