TY - JOUR
T1 - Recovering traceability links between requirements and source code using the configuration management log
AU - Tsuchiya, Ryosuke
AU - Washizaki, Hironori
AU - Fukazawa, Yoshiaki
AU - Kato, Tadahisa
AU - Kawakami, Masumi
AU - Yoshimura, Kentaro
N1 - Publisher Copyright:
Copyright © 2015 The Institute of Electronics, Information and Communication Engineers.
Copyright:
Copyright 2017 Elsevier B.V., All rights reserved.
PY - 2015/4/1
Y1 - 2015/4/1
N2 - Traceability links between requirements and source code are helpful in software reuse and maintenance tasks. However, manually recovering links in a large group of products requires significant costs and some links may be overlooked. Here, we propose a semi-automatic method to recover traceability links between requirements and source code in the same series of large software products. In order to support differences in representation between requirements and source code, we recover links by using the configuration management log as an intermediary. We refine the links by classifying requirements and code elements in terms of whether they are common to multiple products or specific to one. As a result of applying our method to real products that have 60KLOC, we have recovered valid traceability links within a reasonable amount of time. Automatic parts have taken 13 minutes 36 seconds, and non-automatic parts have taken about 3 hours, with a recall of 76.2% and a precision of 94.1%. Moreover, we recovered some links that were unknown to engineers. By recovering traceability links, software reusability and maintainability will be improved.
AB - Traceability links between requirements and source code are helpful in software reuse and maintenance tasks. However, manually recovering links in a large group of products requires significant costs and some links may be overlooked. Here, we propose a semi-automatic method to recover traceability links between requirements and source code in the same series of large software products. In order to support differences in representation between requirements and source code, we recover links by using the configuration management log as an intermediary. We refine the links by classifying requirements and code elements in terms of whether they are common to multiple products or specific to one. As a result of applying our method to real products that have 60KLOC, we have recovered valid traceability links within a reasonable amount of time. Automatic parts have taken 13 minutes 36 seconds, and non-automatic parts have taken about 3 hours, with a recall of 76.2% and a precision of 94.1%. Moreover, we recovered some links that were unknown to engineers. By recovering traceability links, software reusability and maintainability will be improved.
KW - Commonality and variability analysis
KW - Configuration management log
KW - Software product line
KW - Traceability recovery
UR - http://www.scopus.com/inward/record.url?scp=84926483664&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84926483664&partnerID=8YFLogxK
U2 - 10.1587/transinf.2014EDP7199
DO - 10.1587/transinf.2014EDP7199
M3 - Article
AN - SCOPUS:84926483664
VL - E98D
SP - 852
EP - 862
JO - IEICE Transactions on Information and Systems
JF - IEICE Transactions on Information and Systems
SN - 0916-8532
IS - 4
ER -