Normalizing source code vocabulary to support program comprehension and software quality

2013 ◽  
Author(s):  
Latifa Guerrouj
Keyword(s):  
Software Quality ◽  
Source Code ◽  
Program Comprehension ◽  
Support Program

Impact of Clone Refactoring on External Quality Attributes of Open Source Softwares

2018 ◽  
pp. 86-94
Author(s):  
Himanshi Vashisht ◽  
Sanjay Bharadwaj ◽  
Sushma Sharma
Keyword(s):  
Open Source ◽  
Internal Structure ◽  
Software Quality ◽  
Source Code ◽  
Quality Attributes ◽  
Software Component ◽  
External Quality ◽  
Code Refactoring ◽  
Observable Behaviour

Code refactoring is a “Process of restructuring an existing source code.”. It also helps in improving the internal structure of the code without really affecting its external behaviour”. It changes a source code in such a way that it does not alter the external behaviour yet still it improves its internal structure. It is a way to clean up code that minimizes the chances of introducing bugs. Refactoring is a change made to the internal structure of a software component to make it easier to understand and cheaper to modify, without changing the observable behaviour of that software component. Bad smells indicate that there is something wrong in the code that have to refactor. There are different tools that are available to identify and emove these bad smells. A software has two types of quality attributes- Internal and external. In this paper we will study the effect of clone refactoring on software quality attributes.

scholarly journals What do class comments tell us? An investigation of comment evolution and practices in Pharo Smalltalk

2021 ◽  
Vol 26 (6) ◽  
Author(s):  
Pooja Rani ◽  
Sebastiano Panichella ◽  
Manuel Leuenberger ◽  
Mohammad Ghafari ◽  
Oscar Nierstrasz
Keyword(s):  
Empirical Study ◽  
Programming Languages ◽  
Program Comprehension ◽  
Assessment Tools ◽  
Support Program ◽  
Writing Style ◽  
High Quality ◽  
Types Of Information ◽  
Similar Code

Abstract Context Previous studies have characterized code comments in various programming languages, showing how high quality of code comments is crucial to support program comprehension activities, and to improve the effectiveness of maintenance tasks. However, very few studies have focused on understanding developer practices to write comments. None of them has compared such developer practices to the standard comment guidelines to study the extent to which developers follow the guidelines. Objective Therefore, our goal is to investigate developer commenting practices and compare them to the comment guidelines. Method This paper reports the first empirical study investigating commenting practices in Pharo Smalltalk. First, we analyze class comment evolution over seven Pharo versions. Then, we quantitatively and qualitatively investigate the information types embedded in class comments. Finally, we study the adherence of developer commenting practices to the official class comment template over Pharo versions. Results Our results show that there is a rapid increase in class comments in the initial three Pharo versions, while in subsequent versions developers added comments to both new and old classes, thus maintaining a similar code to comment ratio. We furthermore found three times as many information types in class comments as those suggested by the template. However, the information types suggested by the template tend to be present more often than other types of information. Additionally, we find that a substantial proportion of comments follow the writing style of the template in writing these information types, but they are written and formatted in a non-uniform way. Conclusion The results suggest the need to standardize the commenting guidelines for formatting the text, and to provide headers for the different information types to ensure a consistent style and to identify the information easily. Given the importance of high-quality code comments, we draw numerous implications for developers and researchers to improve the support for comment quality assessment tools.

Why Do Developers Reject Refactorings in Open-Source Projects?

2022 ◽  
Vol 31 (2) ◽  
pp. 1-23
Author(s):  
Jevgenija Pantiuchina ◽  
Bin Lin ◽  
Fiorella Zampetti ◽  
Massimiliano Di Penta ◽  
Michele Lanza ◽  
...  
Keyword(s):  
Open Source ◽  
Software Quality ◽  
Good Practice ◽  
Source Code ◽  
Code Review ◽  
Code Quality ◽  
Shed Light

Refactoring operations are behavior-preserving changes aimed at improving source code quality. While refactoring is largely considered a good practice, refactoring proposals in pull requests are often rejected after the code review. Understanding the reasons behind the rejection of refactoring contributions can shed light on how such contributions can be improved, essentially benefiting software quality. This article reports a study in which we manually coded rejection reasons inferred from 330 refactoring-related pull requests from 207 open-source Java projects. We surveyed 267 developers to assess their perceived prevalence of these identified rejection reasons, further complementing the reasons. Our study resulted in a comprehensive taxonomy consisting of 26 refactoring-related rejection reasons and 21 process-related rejection reasons. The taxonomy, accompanied with representative examples and highlighted implications, provides developers with valuable insights on how to ponder and polish their refactoring contributions, and indicates a number of directions researchers can pursue toward better refactoring recommenders.

scholarly journals Same but Different: Consistently Developing and Evolving Software Architecture Models and Their Implementation

2020 ◽  
pp. 87-112
Author(s):  
Marco Konersmann ◽  
Michael Goedicke
Keyword(s):  
Performance Evaluation ◽  
Software Architecture ◽  
Software Quality ◽  
Source Code ◽  
Use Case ◽  
Program Code ◽  
Separate Representation ◽  
Main Driver ◽  
Integrated Architecture ◽  
Architecture Specification

AbstractAs software architecture is a main driver for the software quality, source code is often accompanied by software architecture specifications. When the implementation is changed, the architecture specification is often not updated along with the code, which introduces inconsistencies between these artifacts. Such inconsistencies imply a risk of misunderstandings and errors during the development, maintenance, and evolution, causing serious degradation over the lifetime of the system. In this chapter we present the Explicitly Integrated Architecture approach and its tool Codeling, which remove the necessity for a separate representation of software architecture by integrating software architecture information with the program code. By using our approach, the specification can be extracted from the source code and changes in the specification can be propagated to the code. The integration of architecture information with the code leaves no room for inconsistencies between the artifacts and creates links between artifacts. We evaluate the approach and tool in a use case with real software in development and with a benchmark software, accompanied by a performance evaluation.

A Novel Integrated Framework to Increase Software Quality by Mining Source Code

2013 ◽  
Vol 7 (3) ◽  
pp. 86-105
Author(s):  
Shaheen Khatoon ◽  
Azhar Mahmood ◽  
Guohui Li ◽  
Jianfeng Xu
Keyword(s):  
Software Quality ◽  
Source Code ◽  
Integrated Framework
Sign in / Sign up

Export Citation Format

Share Document