Reconstructing requirements coverage views from design and test using traceability recovery via LSI

Lormans, M.; Deursen, Arie van

doi:10.1145/1107656.1107665

Cited by 33 publications

(26 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One of them is coverage analysis: determining the extent to which requirements are covered by other (downstream) work products. Tools for doing this automatically are being developed, e.g., [16]. By connecting such tools, a DSE support system could help to provide up-to-date status views of the requirements coverage of a software system under development.…”

Section: Discussionmentioning

confidence: 99%

Tool Support for Distributed Software Engineering

Spanjers

Huurne

Bendas

et al. 2006

2006 IEEE International Conference on Global Software Engineering (ICGSE'06)

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 99%

Tool Support for Distributed Software Engineering

Spanjers

Huurne

Bendas

et al. 2006

2006 IEEE International Conference on Global Software Engineering (ICGSE'06)

Self Cite

View full text Add to dashboard Cite

show abstract

“…Lucia et al [15] present an approach and a tool to automatically uncover trace links between a wider range of artifacts, among them use cases. Lormans [16] uses trace link recovery to identify requirements that have not been implemented. Compared to these works, which often use text mining techniques [17], we share the underlying techniques such as LSI, but establish relations between use cases and source code with the goal to find unexecuted features.…”

Section: Related Workmentioning

confidence: 99%

Which Features Do My Users (Not) Use?

Eder

Femmer

Hauptmann

et al. 2014

2014 IEEE International Conference on Software Maintenance and Evolution

View full text Add to dashboard Cite

Abstract-Maintenance of unused features leads to unnecessary costs. Therefore, identifying unused features can help product owners to prioritize maintenance efforts. We present a tool that employs dynamic analyses and text mining techniques to identify use case documents describing unused features to approximate unnecessary features. We report on a preliminary study of an industrial business information system over the course of one year quantifying unused features and measuring the performance of the approach. It indicates the relevance of the problem and the capability of the presented approach to detect unused features.

show abstract

“…In our earlier work, we have proposed an approach for reconstructing requirements views (Lormans and van Deursen 2005) and experimented with the reconstruction of traceability links in several case studies van Deursen 2006, 2009). The method is called Marev: Methodology for Automating Requirements Evolution using Views.…”

Section: Marev and Reqanalystmentioning

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%

“…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%

See 1 more Smart Citation

An industrial case study in reconstructing requirements views

2008

Self Cite

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

Reconstructing requirements coverage views from design and test using traceability recovery via LSI

Cited by 33 publications

References 16 publications

Tool Support for Distributed Software Engineering

Tool Support for Distributed Software Engineering

Which Features Do My Users (Not) Use?

An industrial case study in reconstructing requirements views

Contact Info

Product

Resources

About