Automatic identification of class stereotypes

Dragan, Natalia; Collard, Michael L.; Maletic, Jonathan I.

doi:10.1109/icsm.2010.5609703

Cited by 46 publications

(51 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Stereotypes describe the abstract behavior and role of a method within a class. We felt that this was relevant information and our previous work investigating the automatic detection of stereotypes [14,20], bares evidence that they support program comprehension. Moreover, we found that distributions of method stereotypes can be used to derive class stereotypes.…”

Section: Introductionmentioning

confidence: 90%

Improving Feature Location by Enhancing Source Code with Stereotypes

Alhindawi

Dragan

Collard

et al. 2013

2013 IEEE International Conference on Software Maintenance

Self Cite

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

Section: Introductionmentioning

confidence: 90%

Improving Feature Location by Enhancing Source Code with Stereotypes

Alhindawi

Dragan

Collard

et al. 2013

2013 IEEE International Conference on Software Maintenance

Self Cite

View full text Add to dashboard Cite

show abstract

“…Dragan et al [7] presented an approach to automatically determine a class stereotype; this stereotype is based on the frequency and distribution of method stereotype in the class. They implemented a tool that automatically reverse engineers a class's stereotype and re-documents the class.…”

Section: Related Workmentioning

confidence: 99%

Summarizing Services of Java Packages

Hammad¹,

Abuljadayel²,

Khalaf³

2016

LNSE

View full text Add to dashboard Cite

Abstract-Program comprehension is essential for code maintenance and evolution activities. It saves time and efforts of developers who want to perform any code changes. It also minimizes the chances of introducing bugs. Textual summaries for source code provide great help to code understanding activities. This paper presents an approach to automatically generate textual summaries for services implemented in java packages. The summary is generated by analyzing the source code of methods defined the package. Each method represents a service provide by the package. Each service is summarized as a natural language textual description. The generated summary for a method mainly includes the used data and the names of invoked methods. Summaries of all methods defined in a package are refined and integrated to be reported as a comprehensive summary for the services provided by the package. The generated summaries are useful in different ways. They can be used by developers in their maintenance activities. They also can be useful for the documentation purposes. IndexTerms-Program comprehension, software maintenance, source code summarization.

show abstract

“…The process of commit categorization is influenced by our previous work on uncovering patterns of design from a single-version system at the different levels of abstraction: method [4], class [5], and system [8]. This foundation of identifying stereotypes at the method, class, and system level allowed us to hypothesize that those patterns of design, in the form of method stereotype distributions for a single-version system, also exist in multiple-version systems and could characterize design changes over the evolution history.…”

Section: Commit Categorizationmentioning

confidence: 99%

“…The commit signatures are fed into StereoCommit to assign types to a commit. The rules for identification of commit types are influenced by the rules on automatic identification of patterns of design at the class level for a single-version system [8].…”

Section: Commit Categorizationmentioning

confidence: 99%

Using stereotypes to help characterize commits

Dragan

Collard

Hammad

et al. 2011

2011 27th IEEE International Conference on Software Maintenance (ICSM)

Self Cite

View full text Add to dashboard Cite

Abstract-Individual commits to a version control system are automatically characterized based on the stereotypes of added and deleted methods. The stereotype of each method is automatically reverse engineered using a previously defined taxonomy.Method stereotypes reflect intrinsic atomic behavior of a method and its role in the class. The stereotypes of the added and deleted methods form a descriptor of the change embodied by a given commit. These descriptors are then used to categorize commits, into types, based on the impact of the changes to a class (or classes). The goal is to gain a better understanding of the design changes to a system over its history and provide a means for documenting the commit.

show abstract

Automatic identification of class stereotypes

Cited by 46 publications

References 18 publications

Improving Feature Location by Enhancing Source Code with Stereotypes

Improving Feature Location by Enhancing Source Code with Stereotypes

Summarizing Services of Java Packages

Using stereotypes to help characterize commits

Contact Info

Product

Resources

About