trace link
Recently Published Documents


TOTAL DOCUMENTS

13
(FIVE YEARS 8)

H-INDEX

2
(FIVE YEARS 0)

Author(s):  
Alberto Rodriguez ◽  
Jane Cleland-Huang ◽  
Falessi Davide
Keyword(s):  

2021 ◽  
Author(s):  
Alberto D. Rodriguez ◽  
Jane Cleland-Huang ◽  
Davide Falessi
Keyword(s):  

2021 ◽  
pp. 101-116
Author(s):  
Jan Keim ◽  
Sophie Schulz ◽  
Dominik Fuchß ◽  
Claudius Kocher ◽  
Janek Speit ◽  
...  

Author(s):  
Bangchao Wang ◽  
Rong Peng ◽  
Zhuo Wang ◽  
Xiaomin Wang ◽  
Yuanbang Li

Trace links between requirements and software artifacts provide available traceability information and in-depth insights for different stakeholders. Unfortunately, establishing requirements trace links is a tedious, labor-intensive and fallible task. To alleviate this problem, Information Retrieval (IR) methods, such as Vector Space Model (VSM), Latent Semantic Indexing (LSI), and their variants, have been widely used to establish trace links automatically. But with the widespread use of agile development methodology, artifacts that can be used to generate automatic tracing links are getting shorter and shorter, which decreases the effects of traditional IR-based trace link generation methods. In this paper, Biterm Topic Model–Genetic Algorithm (BTM–GA), which is effective in managing short-text artifacts and configuring initial parameters, is introduced. A hybrid method VSM[Formula: see text]BTM–GA is proposed to generate requirements trace links. Empirical experiments conducted on five real and frequently-used datasets indicate that (1) the hybrid method VSM+BTM[Formula: see text]GA outperforms the others, and its results can achieve the “Good” level, where recall and precision are no less than 70% and 30%, respectively; (2) the performance of the hybrid method is stable and (3) BTM–GA can provide a number of “hard-to-find” trace links that complement the candidate trace links of VSM.


Author(s):  
Iresha Rubasinghe ◽  
Dulani Meedeniya ◽  
Indika Perera

Software development in DevOps practice is a widely used approach to cope with the demand for frequent artefact changes. These changes require a well-defined method to manage artefact consistency to ease the continuous integration process. This chapter proposes a traceability management approach for the artefact types in the main phases of the software process including requirements, design, source code, testing, and configuration. This chapter addresses traceability management, including trace link creation, change detection, impact analysis, change propagation, validation, and visualisation. This chapter presents a tool named SAT-Analyser that is applicable for any software development method and designed for continuous integration, multi-user collaboration, and DevOps tool stack compatibility. The SAT-Analyser is assessed using case studies and shown an impact analysis accuracy of 0.93 of F-measure. Further, the feedback by DevOps practitioners has shown the suitability and innovativeness of the proposed approach.


Author(s):  
Salome Maro ◽  
Emil Sundklev ◽  
Carl-Oscar Persson ◽  
Grischa Liebel ◽  
Jan-Philipp Steghöfer

Sign in / Sign up

Export Citation Format

Share Document