The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
Practical implications of traceability
Software—Practice & Experience
Communications of the ACM
Factors influencing requirements traceability practice
Communications of the ACM
Mastering the requirements process
Mastering the requirements process
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Software Requirements: Styles and Techniques
Software Requirements: Styles and Techniques
Early Experience with Requirements Traceability in an Industrial Environment
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Requirements Engineering
Overcoming the Traceability Benefit Problem
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
| Hi-index | 0.01 |
The use of requirements traceability for information systems development (ISD) projects is not very common in practice despite its often mentioned advantages in the literature. We conducted a case study in a large IT company to identify the factors that are relevant for the decision whether or not to adopt traceability in an ISD project. Five dominant factors emerged: development organization awareness, customer awareness, return on investment, stakeholder preferences, and process flow. It turned out that the majority of the software development project leaders we interviewed were not aware of the concept of traceability - with the obvious result that using traceability in software project is not even considered. This fact has possibly been underestimated in the present literature of requirements engineering.