Do developers benefit from requirements traceability when evolving and maintaining a software system?
- 22 June 2014
- journal article
- Published by Springer Nature in Empirical Software Engineering
- Vol. 20 (2) , 413-441
Abstract
No abstract availableKeywords
This publication has 28 references indexed in Scilit:
- Mind the gap: assessing the conformance of software traceability to relevant guidelines2014
- Traceability and SysML design slices to support safety inspectionsACM Transactions on Software Engineering and Methodology, 2014
- Towards automated traceability maintenanceJournal of Systems and Software, 2012
- A visual language for modeling and executing traceability queriesSoftware and Systems Modeling, 2012
- Traceability Fundamentals2011
- Exploring a Bayesian and linear approach to requirements traceabilityInformation and Software Technology, 2011
- A Visual Traceability Modeling Language2010
- Toward reference models for requirements traceabilityIEEE Transactions on Software Engineering, 2001
- Building knowledge through families of experimentsIEEE Transactions on Software Engineering, 1999
- Adapting traceability environments to project-specific needsCommunications of the ACM, 1998