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

Tsuchiya, Ryosuke; Kato, Toshikazu; Washizaki, Hironori; Kawakami, Masumi; Fukazawa, Yoshiaki; Yoshimura, Kazuyoshi

doi:10.1145/2491627.2491633

Cited by 20 publications

(14 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…* This paper is an extended version of a paper presented at the 17th International Software Product Line Conference [1]. We have added some descriptions that explain how our framework supports software reuse and maintenance in the Sects.…”

Section: Introductionmentioning

confidence: 99%

Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log

Tsuchiya

Washizaki

Fukazawa

et al. 2015

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

SUMMARYTraceability 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. key words: traceability recovery, configuration management log, commonality and variability analysis, software product line

show abstract

Section: Introductionmentioning

confidence: 99%

Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log

Tsuchiya

Washizaki

Fukazawa

et al. 2015

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

show abstract

“… Articles that focus on traceability modeling [30], [48]- [53] traceability tools [27], [54]- [59], or trace links [28], [48], [60]- [78].…”

Section: Refining the Search Articlementioning

confidence: 99%

“…Regarding Question 2 and Question 3, the review findings show that the most common traceability models are domain specific [60], [65]- [72], [76]- [78], [81]- [83]. For instance, Aversano and colleagues [78] presented a domain specific model for capturing traceability links between a business process model which comprises a set of enterprise activities and software components that control the business process model.…”

Section: Modeling Traceabilitymentioning

confidence: 99%

“…For instance, Aversano and colleagues [78] presented a domain specific model for capturing traceability links between a business process model which comprises a set of enterprise activities and software components that control the business process model. Tsuchiya and colleagues [60] proposed a traceability method to recover traceability links between requirements and the source code that represents these requirements in a software product. Antoniol and colleagues [84] proposed a recovery method for trace links between documentation and source code using an information retrieval model.…”

Section: Modeling Traceabilitymentioning

confidence: 99%

“…Regarding the articles that discussed domain specific traceability such as [60], [65]- [72], [74], [76]- [78], [81]- [83], they are only concerned with certain types of trace links that link the artifacts under study. For instance, Sardinha and colleagues [76] discussed identifying trace links between code aspect and early aspect.…”

Section: Modeling Traceabilitymentioning

confidence: 99%

See 2 more Smart Citations

Traceability Modeling for the Engineering of Heterogeneous Systems

Nasser¹

View full text Add to dashboard Cite

Capturing traceability information among artifacts helps ensure product quality and assists tracking functional and non-functional requirements, and performing system validation and impact analysis. Although literature provides many techniques for modeling traceability, existing solutions are either tailored to specific domains or not complete enough (e.g., lack support to specify traceability link semantics). This research examines the current traceability solutions and identifies the drawbacks that hinder capturing some traceability information of heterogeneous artifacts. In this context, heterogeneous artifacts refer to artifacts that come from widely different modeling notations (e.g., UML, Simulink, natural language text, source code).In this thesis, our contribution comprises a traceability framework that can accommodate the traceability of system engineering artifacts which come from different domains of expertise.The framework includes the followings: First, a set of requirements for a traceability model that are necessary to build a generic traceability model. Second, a generic traceability model that is not domain specific and which, therefore, provides a solution for modeling traceability links among heterogeneous models, that is, models for which traceability links need to be established between artifacts in widely different modeling languages (e.g., UML, block diagrams, informal documents). We argue that the proposed requirements are sufficient to build a traceability model oblivious of the heterogeneity of the models whose artifacts need to be traced. We also argue that our traceability model is extensible in the sense that it can adapt to new modeling languages, new ways of characterizing traceability information for instance, without requiring changes to the model itself; Third, a trace links taxonomy that encompasses semantically well-defined trace links that can be utilized along with the traceability model. The design of our framework is validated through a set of validation methods. Also, it is supported by our findings from a survey and a systematic literature review. ii Acknowledgement I would like to thank my supervisor Dr. Yvan Labiche the head of the he Software Quality Engineering Laboratory (SQUALL) at Carleton University for his unlimited support and advice during my PhD study. Also, I would like to extend my thanks to Dr. Daniel Amyot from the University of Ottawa for his valuable comments and the revision of my thesis. I would like to thank NSERC, CRIAQ, CAE, CMC Electronics, and Mannarino Systems & Software for their financial support. Last but not least, many thanks for my lovely family; my wife Hanan, my daughter Nathalie, and my son Mohammed for their support and encouragement.iii DedicationTo the souls of my father and mother who gave me their courage and support.between things written in RDF, OWL must be used to specify these relationships. Therefore, the owl tags in lines 10 and 14 imply a relationship exists between the dependency trace link and the other trace links, i.e., p...

show abstract

Semantic History Slicing

Rubin

Chećhik

2022

Handbook of Re-Engineering Software Intensive Systems Into Software Product Lines

View full text Add to dashboard Cite

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

Cited by 20 publications

References 11 publications

Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log

Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log

Traceability Modeling for the Engineering of Heterogeneous Systems

Semantic History Slicing

Contact Info

Product

Resources

About