Why and How of Requirements Tracing
IEEE Software
Adapting traceability environments to project-specific needs
Communications of the ACM
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Implementing requirements traceability: a case study
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
PRO-ART: Enabling Requirements Pre-Traceability
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
A domain-specific architectural foundation for engineering of numerical software systems
WSEAS TRANSACTIONS on SYSTEMS
A formal scheme for systematic translation of software requirements to source code
ACC'11/MMACTEE'11 Proceedings of the 13th IASME/WSEAS international conference on Mathematical Methods and Computational Techniques in Electrical Engineering conference on Applied Computing
| Hi-index | 0.02 |
Requirements traceability, regardless of the process used to produce a software system, is an important quality attribute for the resulting software product. However, existing approaches to achieving requirements traceability have been specifically designed for traditional software development with formal requirements processes. With the wide industry adoption of agile development methodologies, where requirements are captured and communicated through informal channels, the applicability of existing traceability approaches to agile software projects has been restricted. In this paper, we introduce traceability patterns as a solution to requirement-component tractability in agile software development. In our approach, we achieve traceability through source code, which is the main development artifact in agile methodologies.