Preventing Defects: The Impact of Requirements Traceability Completeness on Software Quality
Authors:
- 27 October 2016
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 43 (8) , 777-797
Abstract
Requirements traceability has long been recognized as an important quality of a well-engineered system. Among stakeholders, traceability is often unpopular due to the unclear benefits. In fact, little evidence exists regarding the expected traceability benefits. There is a need for empirical work that studies the effect of traceability. In this paper, we focus on the four main requirements implementation supporting activities that utilize traceability. For each activity, we propose generalized traceability completeness measures. In a defined process, we selected 24 medium to large-scale open-source projects. For each software project, we quantified the degree to which a studied development activity was enabled by existing traceability with the proposed measures. We analyzed that data in a multi-level Poisson regression analysis. We found that the degree of traceability completeness for three of the studied activities significantly affects software quality, which we quantified as defect rate. Our results provide for the first time empirical evidence that more complete traceability decreases the expected defect rate in the developed software. The strong impact of traceability completeness on the defect rate suggests that traceability is of great practical value for any kind of software development project, even if traceability is not mandated by a standard or regulation.Keywords
Funding Information
- German Ministry of Education and Research (BMBF) (01IS14026A, 01IS16003B)
- Thüringer Aufbaubank (TAB) (2015FE9033)
This publication has 76 references indexed in Scilit:
- A SysML-based approach to traceability management and design slicing in support of safety certification: Framework, tool support, and case studiesInformation and Software Technology, 2012
- Design evolution metrics for defect prediction in object oriented systemsEmpirical Software Engineering, 2010
- Five Misunderstandings About Case-Study ResearchQualitative Inquiry, 2006
- Event-based traceability for managing evolutionary changeIEEE Transactions on Software Engineering, 2003
- The software maintenance project effort estimation model based on function pointsJournal of Software Maintenance and Evolution: Research and Practice, 2003
- A staged model for the software life cycleComputer, 2000
- Factors influencing requirements traceability practiceCommunications of the ACM, 1998
- Adapting traceability environments to project-specific needsCommunications of the ACM, 1998
- Software quality: the elusive target [special issues section]IEEE Software, 1996
- Metrics for requirements engineeringJournal of Systems and Software, 1995