|
|
 |
| |
|
|
|
Correspondence of OOP Refactoring Techniques in PL\SQL Environment: A Case Study of Agile Project Code |
|
|
|
PP: 993-1002 |
|
|
|
doi:10.18576/amis/170605
|
|
|
|
Author(s) |
|
|
|
Khitam Mashaqbeh,
Issam Jebreen,
Ahmad Nabot,
Ahmad Al-Qerem,
Amer Abu Salem,
|
|
|
|
Abstract |
|
|
| scrum is one of the most popular agile approaches for developing software, which has code quality challenges that affect software functionality, maintainability, reliability, usability, efficiency, and portability. However, many techniques are applied to enhance code quality by analyzing and reviewing the code using code conventions, standards, and refactoring. In the Scrum development framework, handling code quality issues requires focusing on the practices that cause such issues (i.e., short testing volume). Therefore, this study aims to investigate how refactoring affects scrum source code quality and code maintainability. This study followed an experimental approach, including a case study for a large and complex Oracle PL/SQL software program through its development phase. The source code of the chosen sprint is analyzed to evaluate its quality and identify the probability of code smell existence. Nine refactoring techniques are applied to the collected data to identify code smells for the chosen PL/SQL software. The study findings show that choosing a suitable refactoring technique positively affects the maintainability of sprint code.
|
|
|
|
|
|
|
|
