Recovering traceability links between requirements and source code in the same series of software products

Ryosuke Tsuchiya, Tadahisa Kato, Hironori Washizaki, Masumi Kawakami, Yoshiaki Fukazawa, Kentaro Yoshimura

    研究成果: Conference contribution

    13 引用 (Scopus)

    抄録

    If traceability links between requirements and source code are not clarified when conducting maintenance and enhancements for the same series of software products, engineers cannot immediately find the correction location in the source code for requirement changes. 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 or specific to the products. 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 will be improved, and software product line introduction will be facilitated.

    元の言語English
    ホスト出版物のタイトルACM International Conference Proceeding Series
    ページ121-130
    ページ数10
    DOI
    出版物ステータスPublished - 2013
    イベント17th International Software Product Line Conference, SPLC 2013 - Tokyo
    継続期間: 2013 8 262013 8 30

    Other

    Other17th International Software Product Line Conference, SPLC 2013
    Tokyo
    期間13/8/2613/8/30

    Fingerprint

    Computer software reusability
    Engineers
    Costs

    ASJC Scopus subject areas

    • Human-Computer Interaction
    • Computer Networks and Communications
    • Computer Vision and Pattern Recognition
    • Software

    これを引用

    Tsuchiya, R., Kato, T., Washizaki, H., Kawakami, M., Fukazawa, Y., & Yoshimura, K. (2013). Recovering traceability links between requirements and source code in the same series of software products. : ACM International Conference Proceeding Series (pp. 121-130) https://doi.org/10.1145/2491627.2491633

    Recovering traceability links between requirements and source code in the same series of software products. / Tsuchiya, Ryosuke; Kato, Tadahisa; Washizaki, Hironori; Kawakami, Masumi; Fukazawa, Yoshiaki; Yoshimura, Kentaro.

    ACM International Conference Proceeding Series. 2013. p. 121-130.

    研究成果: Conference contribution

    Tsuchiya, R, Kato, T, Washizaki, H, Kawakami, M, Fukazawa, Y & Yoshimura, K 2013, Recovering traceability links between requirements and source code in the same series of software products. : ACM International Conference Proceeding Series. pp. 121-130, 17th International Software Product Line Conference, SPLC 2013, Tokyo, 13/8/26. https://doi.org/10.1145/2491627.2491633
    Tsuchiya R, Kato T, Washizaki H, Kawakami M, Fukazawa Y, Yoshimura K. Recovering traceability links between requirements and source code in the same series of software products. : ACM International Conference Proceeding Series. 2013. p. 121-130 https://doi.org/10.1145/2491627.2491633
    Tsuchiya, Ryosuke ; Kato, Tadahisa ; Washizaki, Hironori ; Kawakami, Masumi ; Fukazawa, Yoshiaki ; Yoshimura, Kentaro. / Recovering traceability links between requirements and source code in the same series of software products. ACM International Conference Proceeding Series. 2013. pp. 121-130
    @inproceedings{eee5fa8c8a6540afb9989d99fe106d49,
    title = "Recovering traceability links between requirements and source code in the same series of software products",
    abstract = "If traceability links between requirements and source code are not clarified when conducting maintenance and enhancements for the same series of software products, engineers cannot immediately find the correction location in the source code for requirement changes. 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 or specific to the products. 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 will be improved, and software product line introduction will be facilitated.",
    keywords = "commonality and variability analysis, configuration management log, traceability recovery",
    author = "Ryosuke Tsuchiya and Tadahisa Kato and Hironori Washizaki and Masumi Kawakami and Yoshiaki Fukazawa and Kentaro Yoshimura",
    year = "2013",
    doi = "10.1145/2491627.2491633",
    language = "English",
    isbn = "9781450319683",
    pages = "121--130",
    booktitle = "ACM International Conference Proceeding Series",

    }

    TY - GEN

    T1 - Recovering traceability links between requirements and source code in the same series of software products

    AU - Tsuchiya, Ryosuke

    AU - Kato, Tadahisa

    AU - Washizaki, Hironori

    AU - Kawakami, Masumi

    AU - Fukazawa, Yoshiaki

    AU - Yoshimura, Kentaro

    PY - 2013

    Y1 - 2013

    N2 - If traceability links between requirements and source code are not clarified when conducting maintenance and enhancements for the same series of software products, engineers cannot immediately find the correction location in the source code for requirement changes. 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 or specific to the products. 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 will be improved, and software product line introduction will be facilitated.

    AB - If traceability links between requirements and source code are not clarified when conducting maintenance and enhancements for the same series of software products, engineers cannot immediately find the correction location in the source code for requirement changes. 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 or specific to the products. 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 will be improved, and software product line introduction will be facilitated.

    KW - commonality and variability analysis

    KW - configuration management log

    KW - traceability recovery

    UR - http://www.scopus.com/inward/record.url?scp=84883898323&partnerID=8YFLogxK

    UR - http://www.scopus.com/inward/citedby.url?scp=84883898323&partnerID=8YFLogxK

    U2 - 10.1145/2491627.2491633

    DO - 10.1145/2491627.2491633

    M3 - Conference contribution

    AN - SCOPUS:84883898323

    SN - 9781450319683

    SP - 121

    EP - 130

    BT - ACM International Conference Proceeding Series

    ER -