Using information retrieval to support software maintenance tasks

Poshyvanyk, Denys

doi:10.1109/icsm.2009.5306298

Cited by 13 publications

(10 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Reiss (2006) produced a tool called CLIME that allows one to define constraints and track the co-evolution of artifacts in order to enforce adherence. Savage et al (2010), Poshyvanyk (2008), andMcMillan et al (2009) has explored the use of IR techniques for software traceability in source code to other kinds of documents. Others within the RE community have leveraged natural language processing (NLP) techniques to produce UML models (Konrad and Cheng 2006).…”

Section: Traceability and Requirements Engineeringmentioning

confidence: 99%

“…Many techniques are used, ranging from LDA (Hindle et al 2011) to Latent Semantic Indexing (LSI) (Marcus et al 2004). Researchers such as Poshyvanyk (2008) and Marcus et al (2004) often focus on the document relationships rather than the topic words. In terms of topics and traceability, Baldi et al (2008) labelled topics and then tried to relate topics to aspects in software.…”

Section: Topics In Software Engineeringmentioning

confidence: 99%

See 1 more Smart Citation

Do topics make sense to managers and developers?

et al. 2014

View full text Add to dashboard Cite

Large organizations like Microsoft tend to rely on formal requirements documentation in order to specify and design the software products that they develop. These documents are meant to be tightly coupled with the actual implementation of the features they describe. In this paper we evaluate the value of high-level topic-based requirements traceability and issue report traceability in the version control system, using Latent Dirichlet Allocation (LDA). We evaluate LDA topics on practitioners and check if the topics and trends extracted match the perception that industrial Program Managers and Developers have about the effort put into addressing certain topics. We then replicate this study again on Open Source Developers using issue reports from issue trackers instead of requirements, confirming our previous industrial conclusions. We found that efforts extracted as commits from version control systems relevant to a topic often matched the perception of the managers and developers of what actually occurred at that time. Furthermore we found evidence that many of the identified topics made sense to practitioners and matched their perception of what occurred. But for some topics, we found that practitioners had difficulty interpreting and labelling them. In summary, we investigate the high-level traceability of requirements topics and issue/bug report topics to version control commits via topic analysis and validate with the actual stakeholders the relevance of these topics extracted from requirements and issues.

show abstract

Section: Traceability and Requirements Engineeringmentioning

confidence: 99%

Section: Topics In Software Engineeringmentioning

confidence: 99%

Do topics make sense to managers and developers?

et al. 2014

View full text Add to dashboard Cite

show abstract

“…Other researchers have investigated the use of traceability within specific contexts. For example, Von Knethen [89] and Conte de Leon [18] both described techniques for using trace links to support impact analysis, while Mäder et al [60] and Poshyvanyk et al [77] explored its use for supporting software maintenance and for bug fixing [60].…”

Section: Task-driven Traceabilitymentioning

confidence: 99%

Software traceability: trends and future directions

Cleland‐Huang

Gotel²,

Hayes

et al. 2014

Future of Software Engineering Proceedings

231

View full text Add to dashboard Cite

Software traceability is a sought-after, yet often elusive quality in software-intensive systems. Required in safety-critical systems by many certifying bodies, such as the USA Federal Aviation Authority, software traceability is an essential element of the software development process. In practice, traceability is often conducted in an ad-hoc, after-the-fact manner and, therefore, its benefits are not always fully realized. Over the past decade, researchers have focused on specific areas of the traceability problem, developing more sophisticated tooling, promoting strategic planning, applying information retrieval techniques capable of semi-automating the trace creation and maintenance process, developing new trace query languages and visualization techniques that use trace links, and applying traceability in specific domains such as Model Driven Development, product line systems, and agile project environments. In this paper, we build upon a prior body of work to highlight the state-of-the-art in software traceability, and to present compelling areas of research that need to be addressed.

show abstract

“…Nevertheless, it requires a lot of experience from the developer. If the technique failed, more advanced tools were required, especially when the system is large [2,4,6,7,21].…”

Section: A Previous Work On Feature Locationmentioning

confidence: 99%

Improving Feature Location by Enhancing Source Code with Stereotypes

Alhindawi

Dragan

Collard

et al. 2013

2013 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

Abstract-A novel approach to improve feature location by enhancing the corpus (i.e., source code) with static information is presented. An information retrieval method, namely Latent Semantic Indexing (LSI), is used for feature location. Adding stereotype information to each method/function enhances the corpus. Stereotypes are terms that describe the abstract role of a method, for example get, set, and predicate are well-known method stereotypes. Each method in the system is automatically stereotyped via a static-analysis approach. Experimental comparisons of using LSI for feature location with, and without, stereotype information are conducted on a set of open-source systems. The results show that the added information improves the recall and precision in the context of feature location. Moreover, the use of stereotype information decreases the total effort that a developer would need to expend to locate relevant methods of the feature.

show abstract

Using information retrieval to support software maintenance tasks

Abstract: Abstract

Cited by 13 publications

References 31 publications

Do topics make sense to managers and developers?

Do topics make sense to managers and developers?

Software traceability: trends and future directions

Improving Feature Location by Enhancing Source Code with Stereotypes

Contact Info

Product

Resources

About