More archetypal usage scenarios for software search engines

Janjic, Werner; Hummel, Oliver; Atkinson, Colin

doi:10.1145/1809175.1809181

Cited by 12 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A variety of approaches deal with reuse tasks by starting from test cases. The developer specifies test cases that would satisfy his goals; these drive an automated search for reusable code that (mostly) satisfies the tests . All such approaches to‐date have been rather limited: they are essentially able to suggest only methods or snippets of code for reuse, not complex features, and they demand rather exacting input from the developer in specifying the required test cases.…”

Section: Related Workmentioning

confidence: 99%

Validating pragmatic reuse tasks by leveraging existing test suites

Makady

Walker

2012

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARYTraditional industrial practice often involves the ad hoc reuse of source code that was not designed for that reuse. Such pragmatic reuse tasks play an important role in disciplined software development. Pragmatic reuse has been seen as problematic due to a lack of systematic support, and an inability to validate that the reused code continues to operate correctly within the target system. Although recent work has successfully systematized support for pragmatic reuse tasks, the issue of validation remains unaddressed. In this paper, we present a novel approach and tool to semi‐automatically reuse and transform relevant portions of the test suite associated with pragmatically reused code, as a means to validate that the relevant constraints from the originating system continue to hold, while minimizing the burden on the developer. We conduct a formal experiment with experienced developers, to compare the application of our approach versus the use of a standard IDE (the ‘manual approach’). We find that, relative to the manual approach, our approach: reduces task completion time; improves instruction coverage by the reused test cases; and improves the correctness of the reused test cases. Copyright © 2012 John Wiley & Sons, Ltd.

show abstract

Section: Related Workmentioning

confidence: 99%

Validating pragmatic reuse tasks by leveraging existing test suites

Makady

Walker

2012

Softw Pract Exp

View full text Add to dashboard Cite

show abstract

“…Even though a significant amount of literature exists aiming to understand software developers' information behaviour, in the domain of Psychology of Software Development (Sim et al 1998;LaToza et al 2006;Umarji et al 2008;Janjic et al 2010;) and Human Information Behaviour research ( Ellis & Haugan, 1997;Freund et al 2005;Buckley et al 2006 ), it does not provide a consistent description of software developers' task distribution and does not address the variations of factors laid out in the Cognitive Approach Theory.…”

Section: % 66% Very Wide Literature Review Specific To Information mentioning

confidence: 99%

“…The experiment was carried out on a group of 69 professional software developers and based on the results and the proposed classification, 9 archetypes of behavior were identified spanning across most of the code development related IR cases. The above archetypal classification was then further extended to support the variation of developers' behavior across different stages of the project (Janjic et. 2010).…”

Section: Software Developers' Task Distributionmentioning

confidence: 99%

Software Developers’ Information Needs: Towards the Development of Intelligent Recommender Systems

Grzywaczewski

James

Halloran

2011

Electronic Workshops in Computing

View full text Add to dashboard Cite

Software development is a process which is significantly reliable on information and in the context of the Internet on Information Retrieval (IR) tools. Approximately 20%-30% of work time of software developers is spent on information retrieval and this proportion would be significantly higher if it were not for time constraints and pressure to deliver code. Even though a number of IR solutions exist, 86% of work-related search sessions start with a general purpose search engine. Therefore there exists a significant potential for research and development of ubiquitous, domain specific tools to support the IR process. This paper discusses how the knowledge of work tasks and information needs of software developers can be used to deliver ubiquitous, highly contextsensitive search and intelligent recommendation tools. We present a detailed review of software developers' work related tasks and habits. We also discuss factors that can be used as implicit feedback indicators for further collaborative filtering.

show abstract

“…For instance, it seems reasonable to use such a system in order to search for missing libraries or to find the source code of a specific open source file more quickly than by browsing the web and checking it out from its version control system. However, to our knowledge there is currently no comprehensive compilation of possible usage modes for software retrieval systems beyond the preliminary overview given by Janjic et al [17] and consequently it is hard to tell which of them should be supported in a reference collection.…”

Section: Open Challengesmentioning

confidence: 99%

Facilitating the comparison of software retrieval systems through a reference reuse collection

Hummel

2010

Proceedings of 2010 ICSE Workshop on Search-Driven Development: Users, Infrastructure, Tools and Evaluation

Self Cite

View full text Add to dashboard Cite

Although the idea of component-based software reuse has been around for more than four decades the technology for retrieving reusable software artefacts has grown out of its infancy only recently. After about 30 years of basic research in which scientists struggled to get their hands on meaningful numbers of reusable artifacts to evaluate their prototypes, the "open source revolution" has made software reuse a serious practical possibility. Millions of reusable files have become freely available and more sophisticated retrieval tools have emerged providing better ways of searching among them. However, while the development of such systems has made considerable progress, their evaluation is still largely driven by proprietary approaches which are all too often neither comprehensive nor comparable to one another. Hence, in this position paper, we propose the compilation of a reference collection of reusable artifacts in order to facilitate the future evaluation and comparison of software retrieval tools.

show abstract

More archetypal usage scenarios for software search engines

Cited by 12 publications

References 9 publications

Validating pragmatic reuse tasks by leveraging existing test suites

Validating pragmatic reuse tasks by leveraging existing test suites

Software Developers’ Information Needs: Towards the Development of Intelligent Recommender Systems

Facilitating the comparison of software retrieval systems through a reference reuse collection

Contact Info

Product

Resources

About