An Empirical Validation of Object-Oriented Design Metrics for Fault Prediction

Object-oriented design has become a dominant method in software industry and many design metrics of object-oriented programs have been proposed for quality prediction, but there is no well-accepted statement on how significant those metrics are. In this study, empirical analysis is carried out to validate object-oriented design metrics for defects estimation. Approach: The Chidamber and Kemerer metrics suite is adopted to estimate the number of defects in the programs, which are extracted from a public NASA data set. The techniques involved are statistical analysis and neuro-fuzzy approach. Results: The results indicate that SLOC, WMC, CBO and RFC are reliable metrics for defect estimation. Overall, SLOC imposes most significant impact on the number of defects. Conclusions/Recommendations: The design metrics are closely related to the number of defects in OO classes, but we can not jump to a conclusion by using one analysis technique. We recommend using neuro-fuzzy approach together with statistical techniques to reveal the relationship between metrics and dependent variables, and the correlations among those metrics also have to be considered

Software quality attribute measurement and analysis based on class diagram metrics

Software quality measurement lies at the heart of the quality engineering process. Quality measurement for object-oriented artifacts has become the key for ensuring high quality software. Both researchers and practitioners are interested in measuring software product quality for improvement. It has recently become more important to consider the quality of products at the early phases, especially at the design level to ensure that the coding and testing would be conducted more quickly and accurately. The research work on measuring quality at the design level progressed in a number of steps. The first step was to discover the correct set of metrics to measure design elements at the design level. Chidamber and Kemerer (C&K) formulated the first suite of OO metrics. Other researchers extended on this suite and provided additional metrics. The next step was to collect these metrics by using software tools. A number of tools were developed to measure the different suites of metrics; some represent their measurements in the form of ordinary numbers, others represent them in 3D visual form. In recent years, researchers developed software quality models which went a bit further by computing quality attributes from collected design metrics. In this research we extended on the software quality modelers’ work by adding a quality attribute prioritization scheme and a design metric analysis layer. Our work is all focused on the class diagram, the most fundamental constituent in any object oriented design. Using earlier researchers’ work, we extract a class diagram’s metrics and compute its quality attributes. We then analyze the results and inform the user. We present our figures and observations in the form of an analysis report. Our target user could be a project manager or a software quality engineer or a developer who needs to improve the class diagram’s quality. We closely examine the design metrics that affect quality attributes. We pinpoint the weaknesses in the class diagram, based on these metrics, inform the user about the problems that emerged from these classes, and advice him/her as to how he/she can go about improving the overall design quality. We consider the six basic quality attributes: “Reusability”, “Functionality”, “Understandability”, “Flexibility”, “Extendibility”, and “Effectiveness” of the whole class diagram. We allow the user to set priorities on these quality attributes in a sequential manner based on his/her requirements. Using a geometric series, we calculate a weighted average value for the arranged list of quality attributes. This weighted average value indicates the overall quality of the product, the class diagram. Our experimental work gave us much insight into the meanings and dependencies between design metrics and quality attributes. This helped us refine our analysis technique and give more concrete observations to the user

Analisis Metriks Berorientasi Objek terhadap aplikasi yang mengimplementasikan framework zend

ABSTRAKSI: Framework muncul karena adanya kebutuhan akan dukungan berbagai macam library dan sebuah aturan yang seragam dalam pembangunan sistem informasi yang besar dan akan terus berkembang sejalan dengan teknologi rekayasa perangkat lunak. Salah satu framework yang muncul untuk mendukung teknologi berorientasi objek pada PHP adalah framework zend. Pada manualnya dijelaskan bahwa framework zend diimplementasikan menggunakan 100 % kode berorientasi objek. Struktur komponen dari framework zend dibuat unik, tiap komponen di desain dengan dependencies yang kecil dengan komponen lainnya yang sering disebut dengan istilah arsitektur loosely coupled Tugas akhir ini bermaksud untuk menganalisis penerapan teknik berorientasi objek pada website yang mengimplementasikan framework zend, bagaimana sebenarnya kualitas penggunaan pendekatan berorientasi objek pada aplikasi web yang mengimplementasikan framework zend. Analisis dilakukan dengan Object Oriented Metrics, yang sering disebut dengan suite metrik CK dan paling banyak direferensi karena terbukti mewakili prinsip-prinsip berorientasi objek sehingga hasilnya jelas menggambarkan kualitas perangkat lunak. Metrik-metrik tersebut antara lain : WMC ( Weight Method Class) , DIT (Depth of Inheritance Tree) , NOC (Number of Children), CBO ( Coupling Between Objek), RFC (Response for a Class), dan LCOM (Lack of Cohesion in Methods). Tugas akhir ini dibangun menggunakan menggunakan analisis dan desain berorientasi objek, dan arsitekturnya menyesuaikan dengan arsitektur framework zend yaitu MVC (Model View Controller). Dari implementasi serta hasil analisa pengukuran dengan OO metrics didapatkan kesimpulan tentang kualitas dukungan object oriented pada framework zend. Ternyata nilai-nilai yang dihasilkan menunjukkan framework zend tidak 100% mengadaptasi object oriented dimana dalam beberapa parameter perhitungan menunjukkan nilai kualitas object oriented yang tidak baik.Kata Kunci : OOP, Framework Zend, OO metrics.ABSTRACT: The emergence of a framework as the needs of the library and a rule in the development of a uniform information system in line with the growing technology of software engineering. One of the framework that appears to support the object-oriented technology is zend framework in PHP. In tutorial of Zend Framework, explained that on the Zend framework is implemented using 100% object-oriented code. Structure components of the Zend Framework created a unique, in the design of each component with a small dependencies with other components is often referred to by the term loosely coupled architecture. This final project means to analyze OOP support on the website that the Zend Framework implemented, how the actual quality of the use of object-oriented approach in implementing a web application Zend Framework. Analysis conducted with OO-Metrics, often called the CK Metrics Suite and most references because evidently represents the principles of object-oriented so that the results clearly illustrate the quality of the software. Metrics-metrics are: WMC (Method Weight Class), DIT (Depth of Inheritance Tree), NOC (Number of Children), CBO (coupling Between Objects), RFC (Response for a Class), and LCOM (Lack of Cohesion in Methods) This final project was built using the analysis and design using object-oriented, architecture and adjust with the Zend Framework architecture MVC (Model View Controller). This can be concluded that the values indicate that the Zend Framework is not 100% object oriented adapt the parameters in the calculation of the value of quality shows that are not object oriented eitherKeyword: OOP, Framework Zend, Oometrics

Estimation of Defect proneness Using Design complexity Measurements in Object- Oriented Software

Software engineering is continuously facing the challenges of growing complexity of software packages and increased level of data on defects and drawbacks from software production process. This makes a clarion call for inventions and methods which can enable a more reusable, reliable, easily maintainable and high quality software systems with deeper control on software generation process. Quality and productivity are indeed the two most important parameters for controlling any industrial process. Implementation of a successful control system requires some means of measurement. Software metrics play an important role in the management aspects of the software development process such as better planning, assessment of improvements, resource allocation and reduction of unpredictability. The process involving early detection of potential problems, productivity evaluation and evaluating external quality factors such as reusability, maintainability, defect proneness and complexity are of utmost importance. Here we discuss the application of CK metrics and estimation model to predict the external quality parameters for optimizing the design process and production process for desired levels of quality. Estimation of defect-proneness in object-oriented system at design level is developed using a novel methodology where models of relationship between CK metrics and defect-proneness index is achieved. A multifunctional estimation approach captures the correlation between CK metrics and defect proneness level of software modules.Comment: 5 pages, 1 figur

An Approach for the Empirical Validation of Software Complexity Measures

Software metrics are widely accepted tools to control and assure software quality. A large number of software metrics with a variety of content can be found in the literature; however most of them are not adopted in industry as they are seen as irrelevant to needs, as they are unsupported, and the major reason behind this is due to improper empirical validation. This paper tries to identify possible root causes for the improper empirical validation of the software metrics. A practical model for the empirical validation of software metrics is proposed along with root causes. The model is validated by applying it to recently proposed and well known metrics

An empirical investigation of an object-oriented software system

This is the post print version of the article. The official published version can be obtained from the link below.This paper describes an empirical investigation into an industrial object-oriented (OO) system comprised of 133,000 lines of C++. The system was a subsystem of a telecommunications product and was developed using the Shlaer-Mellor method. From this study, we found that there was little use of OO constructs such as inheritance and, therefore, polymorphism. It was also found that there was a significant difference in the defect densities between those classes that participated in inheritance structures and those that did not, with the former being approximately three times more defect-prone. We were able to construct useful prediction systems for size and number of defects based upon simple counts such as the number of states and events per class. Although these prediction systems are only likely to have local significance, there is a more general principle that software developers can consider building their own local prediction systems. Moreover, we believe this is possible, even in the absence of the suites of metrics that have been advocated by researchers into OO technology. As a consequence, measurement technology may be accessible to a wider group of potential users