Automatic Documentation of [Mined] Feature Implementations from Source Code Elements and Use-Case Diagrams with the REVPLINE Approach

Al-Msie’deen, Ra’Fat; Huchard, Marianne; Seriai, Abdelhak-Djamel; Urtado, Christelle; Vauttier, Sylvain

doi:10.1142/s0218194014400142

Cited by 15 publications

(18 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…All participants were felt that the extracted map was very important as the changes between the two versions were very precise. Juana's approach has been evaluated by three metrics: precision, recall, and F-Measure [19]. All metrics have values between 0 and 1.…”

Section: Argoumlmentioning

confidence: 99%

See 1 more Smart Citation

Software Evolution Understanding: Automatic Extraction of Software Identifiers Map for Object-Oriented Software Systems

Al-Msie’deen¹,

Blasi

2021

JCOMSS

View full text Add to dashboard Cite

Software companies usually develop a set of product variants within the same family that share certain functions and differ in others. Variations across software variants occur to meet different customer requirements. Thus, software product variants evolve over time to cope with new requirements. A software engineer who deals with this family may find it difficult to understand the evolution scenarios that have taken place over time. In addition, software identifier names are important resources to understand the evolution scenarios in this family. This paper introduces an automatic approach called Juana’s approach to detect the evolution scenario across two product variants at source code level and identifies the common and unique software identifier names across software variants source code. Juana’s approach refers to common and unique identifier names as a software identifiers map and compute it by comparing software variants to each other. Juana considers all software identifier names such as package, class, attribute and method. The novelty of this approach is that it exploits common and unique identifier names across the source code of software variants, to understand the evolution scenarios across software family in an efﬁcient way. For validity, Juana was applied on ArgoUML and Mobile Media software variants. The results of this evaluation validate the relevance and the performance of the approach as all evolution scenarios were correctly detected via software identifiers map.

show abstract

Section: Argoumlmentioning

confidence: 99%

“…Fig.6. The packages map for ArgoUML software variants Juana's approach has been evaluated by three metrics: precision, recall, and F-Measure[19]. All metrics have values between 0 and 1.…”

mentioning

confidence: 99%

Software Evolution Understanding: Automatic Extraction of Software Identifiers Map for Object-Oriented Software Systems

Al-Msie’deen¹,

Blasi

2021

JCOMSS

View full text Add to dashboard Cite

show abstract

“…In contrast, manually written summaries were more precise and short. For future work, Suncode plans to split the names of software identifiers (e.g., package, class, attribute and method) into words by using the camel-case splitting algorithm (Al-Msie'deen et al, 2014a). It also plans to use the class and method comments in the summarization process.…”

Section: Suncode Summarymentioning

confidence: 99%

Supporting software documentation with source code summarization

Al-Msie’deen

Blasi²

2019

Int. j. adv. appl. sci.

View full text Add to dashboard Cite

Source code summarization is a process of generating summaries that describe software code, the majority of source code summarization usually generated manually, where the summaries are written by software developers. Recently, new automated approaches are becoming more useful. These approaches have been found to be effective in some cases. The main weaknesses of these approaches are that they never exploit code dependencies and summarize either the software classes or methods but not both. This paper proposes a source code summarization approach (Suncode) that produces a short description for each class and method in the software system. To validate the approach, it has been applied to several case studies. Moreover, the generated summaries are compared to summaries that written by human experts and to summaries that written by a state-of-theart solution. Results of this paper found that Suncode summaries provide better information about code dependencies comparing with other studies. In addition, Suncode summaries can improve and support the current software documentation. The results found that manually written summaries were more precise and short as well.

show abstract

“…For the second question, we check the component services to evaluate the identified dependencies. The authors of this paper are familiar with the case studies since they studied it in many previous research projects, such as Eyal Salman et al 2015and Al-Msie'deen et al (2014) .…”

Section: Threats To Internal Validitymentioning

confidence: 99%

Recovering software product line architecture of a family of object-oriented product variants

Shatnawi

Seriai

Sahraoui

2017

Journal of Systems and Software

View full text Add to dashboard Cite

International audienceSoftware Product Line Engineering (SPLE) aims at applying a pre-planned systematic reuse of large-grained software artifacts to increase the software productivity and reduce the development cost. The idea of SPLE is to analyze the business domain of a family of products to identify the common and the variable parts between the products. However, it is common for companies to develop, in an ad-hoc manner (e.g. clone and own), a set of products that share common services and differ in terms of others. Thus, many contributions are proposed to re-engineer existing product variants to a software product line. Nevertheless, these contributions are mostly focused on managing the variability at the requirement level. Few contributions address the variability at the architectural level despite its major importance. Starting from this observation, we propose an approach to reverse engineer the architecture of a set of product variants. Our goal is to identify variability and dependencies among architectural-element variants. Our work relies on formal concept analysis to analyze the variability. To validate the proposed approach, we experimented on two families of open-source product variants; Mobile Media and Health Watcher. %The results show that our approach is able to identify the architectural variability and the dependencies

show abstract

Automatic Documentation of [Mined] Feature Implementations from Source Code Elements and Use-Case Diagrams with the REVPLINE Approach

Cited by 15 publications

References 25 publications

Software Evolution Understanding: Automatic Extraction of Software Identifiers Map for Object-Oriented Software Systems

Software Evolution Understanding: Automatic Extraction of Software Identifiers Map for Object-Oriented Software Systems

Supporting software documentation with source code summarization

Recovering software product line architecture of a family of object-oriented product variants

Contact Info

Product

Resources

About