Estimation of Defect Proneness Using Design Complexity Measurements in Object-Oriented Software

Selvarani, R.; Nair, T. R. Gopalakrishnan; Prasad, V. Kamakshi

doi:10.1109/icsps.2009.163

Cited by 14 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Indeed, Chidamber and his colleagues stated that DIT is a measure of how many ancestral classes can potentially affect this class, which exactly describes the dependencies of a child class to its ancestors. For this reason, it was reported that higher DIT is associated with higher levels of defect proneness for classes . Many research studies used DIT as a measure of dependency (e.g., ).…”

Section: Methodsmentioning

confidence: 99%

Testing the theory of relative dependency from an evolutionary perspective: higher dependencies concentration in smaller modules over the lifetime of software products

Bian

Parande

Koru³

et al. 2016

J Software Evolu Process

View full text Add to dashboard Cite

Recent studies conducted on the single releases of multiple software products showed that dependencies concentrate on smaller modules, that is, smaller modules have more dependencies per source line of code. This phenomenon, called the Theory of Relative Dependency, explains why some earlier studies reported that smaller modules were proportionally more defect prone. It is important to test the Theory of Relative Dependency from multiple perspectives so that it can be used as an explanatory argument when garnering organizational support to give a higher quality assurance (QA) priority to smaller modules. In this study, we test the validity of this theory from an evolutionary perspective by examining the consecutive releases of a number of software products. Dependencies do concentrate over smaller modules regardless of the product age. Furthermore, continuous refactoring efforts are associated with increasing concentration of dependencies on smaller modules over product lifetime. Based on the consistent results, software managers and developers should consider giving a higher QA priority to smaller modules over the lifetime of a software product. In the projects where refactoring is adopted continuously, the QA priority on smaller modules should be further increased as the software product ages.

show abstract

Section: Methodsmentioning

confidence: 99%

Testing the theory of relative dependency from an evolutionary perspective: higher dependencies concentration in smaller modules over the lifetime of software products

Bian

Parande

Koru³

et al. 2016

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…The desire for programming measurements permits the examiners, fashioners, coders, analyzers and the supervisors imagine the product improvement forms and survey the framework [13]. In the item situated environment, one of the significant viewpoints having a solid impact on the nature of coming about programming framework is the configuration many-sided quality [14].…”

Section: Previous Workmentioning

confidence: 99%

Evaluate The Software Through Object Oriented Paradigms

Mateen¹,

Nazir²

2016

IJCA

View full text Add to dashboard Cite

Programming assumes an essential part in today's electronic world. The developer utilizes diverse dialects to build up the product. Keeping in mind the end goal to create programming, it needs a few stages, for example, Analysis, Design, Implementation, Testing and Maintenance. Of these few stages, the investigation and outline get to be fundamental, since these are the most crucial component in the advancement of the product. Presently a-days, a large portion of the product is article stated, in light of the fact that the item arranged dialects give a simple approach to create and keep up the system. This item situated project is comprised of a few divisions based upon the reason. Every division performs some capacities subordinate upon the code. Every one of these divisions are then incorporated to give the single system. In the event that any blunder happened in any part of the project implies, it is important to change the influenced part of a system to expel the mistake. To keep away from this sort of pointless change with the long time term, the engineer must diagram and tests the underlying stage, for example, investigate and configuration. These sorts of tests on examination and outline for an article arranged project did by an innovation called the OOP (Object Oriented Paradigms). In this paper, an approach proposed for examination, the configuration to be completed in the improvement of the system, before begin to execute. These measurements developed by taking or gathering substantial volume of information keeping in mind the end goal to give the measurements reasonable to a wide range of Object-Oriented dialects, for example, Python, Ruby, .Net and R software for big data analysis. The proposed work gives the summing up procedure which termed as GenM (Generalized Measurement) strategy on the item situated programming. This is finished by executing the arrangement record for recognizing the mistake rate. Along these lines, this paper gives proficient systems to OOP.

show abstract

“…The data gathered over a longer project duration may reveal different patterns as a decreasing number of components are left unchanged. [2] Many other methods are described to identify and visualize class interactions that are the most change-prone. That method was object-oriented software developed using design patterns [3].…”

Section: Related Workmentioning

confidence: 99%