Mining subclassing directives to improve framework reuse

Bruch, Marcel; Mezini, Mira; Monperrus, Martin

doi:10.1109/msr.2010.5463347

Cited by 20 publications

(11 citation statements)

References 17 publications

(32 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A "Subclassing" directive states a requirement that has to be satisfied when subclassing a library class; such directives are, e.g., related to how and when to extend a library class, implementing a library interface, overriding a library method, implementing an abstract library method (or a method from a library interface). This section deepens the empirical findings of our previous work [10], which introduced the concept of "subclassing directives".…”

Section: Subclassing Directivesupporting

confidence: 52%

“…In other terms, pieces of an API's documentation that describe how to correctly and optimally use a library are API directives. This definition encompasses Dekel's [14] and Bruch's [10] definition of API directive, but is a bit broader to provide enough leeway to accommodate natural language subtleties. Next, we present three different directives from three different software packages to sketch the scope of API directives.…”

Section: Edition)]mentioning

confidence: 99%

“…This enables us to find API directives related to subclassing. This list is based upon our work on subclassing directives [10] and encompasses: "extend*", "overrid*", "overload*", "overwrit*", "reimplement*", "subclass*", "inherit*", and "super*".…”

Section: Determining An Api Corpusmentioning

confidence: 99%

See 2 more Smart Citations

What should developers be aware of? An empirical study on the directives of API documentation

Monperrus¹,

Eichberg²,

Tekes³

et al. 2011

Empir Software Eng

Self Cite

View full text Add to dashboard Cite

Application Programming Interfaces (API) are exposed to developers in order to reuse software libraries. API directives are natural-language statements in API documentation that make developers aware of constraints and guidelines related to the usage of an API. This paper presents the design and the results of an empirical study on the directives of API documentation of object-oriented libraries. Its main contribution is to propose and extensively discuss a taxonomy of 23 kinds of API directives.

show abstract

Section: Subclassing Directivesupporting

confidence: 52%

Section: Edition)]mentioning

confidence: 99%

See 1 more Smart Citation

What should developers be aware of? An empirical study on the directives of API documentation

Monperrus¹,

Eichberg²,

Tekes³

et al. 2011

Empir Software Eng

Self Cite

View full text Add to dashboard Cite

show abstract

“…The best way of manual verification is performing it by the actual user (e.g., developers), who are expert in the field [24], [40]. If this is not possible, then at least somebody outside the research group should perform the manual verification [14]. It is also suggested that rigorous inspection and testing is applied to the source code and scripts that implement the analysis approach since wrong output might not necessarily be due to poor heuristics, but simply due to defective implementations [44].…”

Section: Comments From 5 Papers]mentioning

confidence: 99%

The MSR Cookbook: Mining a decade of research

Hemmati

Nadi

Baysal

et al. 2013

2013 10th Working Conference on Mining Software Repositories (MSR)

View full text Add to dashboard Cite

Abstract-The Mining Software Repositories (MSR) research community has grown significantly since the first MSR workshop was held in 2004. As the community continues to broaden its scope and deepens its expertise, it is worthwhile to reflect on the best practices that our community has developed over the past decade of research. We identify these best practices by surveying past MSR conferences and workshops. To that end, we review all 117 full papers published in the MSR proceedings between 2004 and 2012. We extract 268 comments from these papers, and categorize them using a grounded theory methodology. From this evaluation, four high-level themes were identified: data acquisition and preparation, synthesis, analysis, and sharing/replication. Within each theme we identify several common recommendations, and also examine how these recommendations have evolved over the past decade. In an effort to make this survey a living artifact, we also provide a public forum that contains the extracted recommendations in the hopes that the MSR community can engage in a continuing discussion on our evolving best practices.

show abstract

“…Schäfer et al [36] exploit framework usage data to cluster elements of an API into building blocks that are typically used together. Finally, Bruch et al [37] present an automated framework documentation approach that mines sample applications for subclassing directives, short descriptions of how to subclass a framework class or override its methods.…”

Section: Supporting Framework Usagementioning

confidence: 99%

Two Studies of Framework-Usage Templates Extracted from Dynamic Traces

Heydarnoori

Czarnecki

Binder

et al. 2012

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Abstract-Object-oriented frameworks are widely used to develop new applications. They provide reusable concepts that are instantiated in application code through potentially complex implementation steps such as subclassing, implementing interfaces, and calling framework operations. Unfortunately, many modern frameworks are difficult to use because of their large and complex APIs and frequently incomplete user documentation. To cope with these problems, developers often use existing framework applications as a guide. However, locating concept implementations in those sample applications is typically challenging due to code tangling and scattering. To address this challenge, we introduce the notion of concept-implementation templates, which summarize the necessary concept-implementation steps and identify them in the sample application code, and a technique, named FUDA, to automatically extract such templates from dynamic traces of sample applications. This paper further presents the results of two experiments conducted to evaluate the quality and usefulness of FUDA templates. The experimental evaluation of FUDA with 14 concepts in five widely used frameworks suggests that the technique is effective in producing templates with relatively few false positives and false negatives for realistic concepts by using two sample applications. Moreover, we observed in a user study with 28 programmers that the use of templates reduced the concept-implementation time compared to when documentation was used.

show abstract

Mining subclassing directives to improve framework reuse

Cited by 20 publications

References 17 publications

What should developers be aware of? An empirical study on the directives of API documentation

What should developers be aware of? An empirical study on the directives of API documentation

The MSR Cookbook: Mining a decade of research

Two Studies of Framework-Usage Templates Extracted from Dynamic Traces

Contact Info

Product

Resources

About