Effective Implementation of Agile Practices - Object Oriented Metrics Tool to Improve Software Quality

Veerapaneni Esther Jyothi

doi:10.5121/ijsea.2012.3402

Abstract

Maintaining the quality of the software is the major challenge in the process of software development. Software inspections which use the methods like structured walkthroughs and formal code reviews involve careful examination of each and every aspect/stage of software developmen t. In Agile software development, refactoring helps to improve software quality . This refactoring is a technique to improve software internal structure without changing its behaviour.After much study regarding the ways to improve software quality, our research proposes an object oriented software metric tool called “MetricAnalyzer”. This tool is tested on different codebases and is proven to be much usefu l.

Highlights

Based on the developments in the business Software frequently undergoes changes
This research paper is organised into different phases systematically as follows: Section 2: Decide upon Metrics [IDENTIFYING PHASE] Section 3: Apply metrics on codebase [EVALUATION PHASE] Section 4: Result analysis [INTERPRETATION AND ADVISING PHASE] Section 5: Refactoring the codebase [APPLICATION PHASE]
The following are the code snippets for four metrics TNOA (Total Number of Attributes), WMPC (Weighted Methods per Class), MIT (Max Inheritance Tree), NOCP (Number of classes Per Package) written as a part of “MetricAnalyzer” tool development which are provided for examination

Summary

INTRODUCTION

Based on the developments in the business Software frequently undergoes changes. These changes in the software generally made under the demand of time and budget. To improve the quality of the software the design problems must be identified and eradicated otherwise they may cause the system to display low maintainability, low reuse, high complexity and flawed behaviour. We tried to detect the code smells [3] in the codebase of a java project by using our tool called “MetricAnalyzer” This tool examined the code and has come up with an advice to refactor in order code to improve the software quality. This research paper is organised into different phases systematically as follows: Section 2: Decide upon Metrics [IDENTIFYING PHASE] Section 3: Apply metrics on codebase [EVALUATION PHASE] Section 4: Result analysis [INTERPRETATION AND ADVISING PHASE] Section 5: Refactoring the codebase [APPLICATION PHASE]

IDENTIFYING PHASE

EVALUATION PHASE

INTERPRETATION AND ADVISING PHASE

APPLICATION PHASE

CONCLUSIONS