Can LSI help reconstructing requirements traceability in design and test?

Lormans, M.; Deursen, Arie van

doi:10.1109/csmr.2006.13

Cited by 93 publications

(71 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The benefits of these strategies are that they guarantee certain level of quality by using the constant threshold, and, yet, they take only the best k% of the links for a certain work product. Both strategies are described in detail in (Lormans and van Deursen 2009), and they have shown improved results in terms of recall and precision. As with all information retrieval techniques, it is not guaranteed that all correct links are indeed found: both, false negatives, and false positives may arise.…”

Section: Marev: a Methodology For Automating Requirements Evolution Umentioning

confidence: 99%

“…In our previous work, we proposed two link selection strategies, a one and a two dimensional vector filter strategy on the similarity matrix (Lormans and van Deursen 2009). These link selection strategies combine the already known strategies constant threshold (represented by the symbol c in this paper) and variable threshold (represented by a percentage q) discussed by De Lucia et al (2004).…”

Section: Marev: a Methodology For Automating Requirements Evolution Umentioning

confidence: 99%

“…In order to support the Marev approach, we developed the ReqAnalyst 1 (Lormans and van Deursen 2009) tool. This tool can reconstruct traceability information and generate requirements views using that reconstructed traceability information.…”

Section: The Reqanalyst Tool Suitementioning

confidence: 99%

“…The primary question addressed through this exploratory case study was how and to which extent requirements views can be reverse-engineered from existing work products. An important question hereby is whether the approach we proposed (Lormans and van Deursen 2005, 2009) may be used to reconstruct these views. To answer this question, it is described how our own prototype tool (ReqAnalyst) has been extended to support these views, offering project stakeholders means to inspect the system and development progress in terms of these views.…”

Section: Introductionmentioning

confidence: 99%

“…Our own line of research has focused on the use of information retrieval techniques, in particular latent semantic indexing (LSI) (Deerwester et al 1990), for this purpose, and on the application of the reconstructed matrices for view reconstruction, specifically. We incorporated our ideas in a method, called Marev, and implemented the method in a tool, called ReqAnalyst (Lormans and van Deursen 2005, 2009.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

An industrial case study in reconstructing requirements views

2008

View full text Add to dashboard Cite

Requirements views, such as coverage and status views, are an important asset for monitoring and managing software development projects. We have developed a method that automates the process of reconstructing these views, and we have built a tool, ReqAnalyst, that supports this method. This paper presents an investigation as to which extent requirements views can be automatically generated in order to monitor requirements in industrial practice. The paper focuses on monitoring the requirements in test categories and test cases. In order to retrieve the necessary data, an information retrieval technique, called Latent Semantic Indexing, was used. The method was applied in an industrial study. A number of requirements views were defined and experiments were carried out with different reconstruction settings for generating these views. Finally, we explored how these views can help the developers during the software development process.

show abstract

Section: Marev: a Methodology For Automating Requirements Evolution Umentioning

confidence: 99%

Section: Marev: a Methodology For Automating Requirements Evolution Umentioning

confidence: 99%

Section: The Reqanalyst Tool Suitementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

An industrial case study in reconstructing requirements views

2008

View full text Add to dashboard Cite

show abstract

Assigning change requests to software developers

Kagdi

Gethers

Poshyvanyk

et al. 2011

J Software Evolu Process

View full text Add to dashboard Cite

SUMMARYThe paper presents an approach to recommend a ranked list of expert developers to assist in the implementation of software change requests (e.g., bug reports and feature requests). An Information Retrieval (IR)-based concept location technique is first used to locate source code entities, e.g., files and classes, relevant to a given textual description of a change request. The previous commits from version control repositories of these entities are then mined for expert developers. The role of the IR method in selectively reducing the mining space is different from previous approaches that textually index past change requests and/or commits. The approach is evaluated on change requests from three open-source systems: ArgoUML, Eclipse, and KOffice, across a range of accuracy criteria. The results show that the overall accuracies of the correctly recommended developers are between 47 and 96% for bug reports, and between 43 and 60% for feature requests. Moreover, comparison results with two other recommendation alternatives show that the presented approach outperforms them with a substantial margin. Project leads or developers can use this approach in maintenance tasks immediately after the receipt of a change request in a free-form text.

show abstract