IEICE TRANSACTIONS on Information
Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log
Summary :
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.
- Publication
- IEICE TRANSACTIONS on Information Vol.E98-D No.4 pp.852-862
- Publication Date
- 2015/04/01
- Publicized
- 2015/01/06
- Online ISSN
- 1745-1361
- DOI
- 10.1587/transinf.2014EDP7199
- Type of Manuscript
- PAPER
- Category
- Software Engineering
Authors
Ryosuke TSUCHIYA
Waseda University
Hironori WASHIZAKI
Waseda University
Yoshiaki FUKAZAWA
Waseda University
Tadahisa KATO
Hitachi, Ltd.
Masumi KAWAKAMI
Hitachi, Ltd.
Kentaro YOSHIMURA
Hitachi, Ltd.
Keyword
Latest Issue
Copyrights notice of machine-translated contents
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Cite this
Copy
Ryosuke TSUCHIYA, Hironori WASHIZAKI, Yoshiaki FUKAZAWA, Tadahisa KATO, Masumi KAWAKAMI, Kentaro YOSHIMURA, "Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log" in IEICE TRANSACTIONS on Information,
vol. E98-D, no. 4, pp. 852-862, April 2015, doi: 10.1587/transinf.2014EDP7199.
Abstract: 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.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.2014EDP7199/_p
Copy
@ARTICLE{e98-d_4_852,
author={Ryosuke TSUCHIYA, Hironori WASHIZAKI, Yoshiaki FUKAZAWA, Tadahisa KATO, Masumi KAWAKAMI, Kentaro YOSHIMURA, },
journal={IEICE TRANSACTIONS on Information},
title={Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log},
year={2015},
volume={E98-D},
number={4},
pages={852-862},
abstract={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.},
keywords={},
doi={10.1587/transinf.2014EDP7199},
ISSN={1745-1361},
month={April},}
Copy
TY - JOUR
TI - Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log
T2 - IEICE TRANSACTIONS on Information
SP - 852
EP - 862
AU - Ryosuke TSUCHIYA
AU - Hironori WASHIZAKI
AU - Yoshiaki FUKAZAWA
AU - Tadahisa KATO
AU - Masumi KAWAKAMI
AU - Kentaro YOSHIMURA
PY - 2015
DO - 10.1587/transinf.2014EDP7199
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E98-D
IS - 4
JA - IEICE TRANSACTIONS on Information
Y1 - April 2015
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.
ER -
English
