Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Software Engineering Economics
Software Engineering Economics
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
The relevance of software documentation, tools and technologies: a survey
Proceedings of the 2002 ACM symposium on Document engineering
Event-Based Traceability for Managing Evolutionary Change
IEEE Transactions on Software Engineering
Requirements Engineering: The State of the Practice
IEEE Software
An empirical study of industrial requirements engineering process assessment and improvement
ACM Transactions on Software Engineering and Methodology (TOSEM)
Beyond Documents: Visualizing Informal Communication
REV '08 Proceedings of the 2008 Requirements Engineering Visualization
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
| Hi-index | 0.00 |
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.