AHierarchicalModelforOODesignQualityAssessment

AHierarchicalModelforOODesignQualityAssessment - 4 IEEE...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
A Hierarchical Model for Object-Oriented Design Quality Assessment Jagdish Bansiya, Member , IEEE , and Carl G. Davis, Fellow , IEEE Abstract ÐThis paper describes an improved hierarchical model for the assessment of high-level design quality attributes in object- oriented designs. In this model, structural and behavioral design properties of classes, objects, and their relationships are evaluated using a suite of object-oriented design metrics. This model relates design properties such as encapsulation, modularity, coupling, and cohesion to high-level quality attributes such as reusability, flexibility, and complexity using empirical and anecdotal information. The relationship, or links, from design properties to quality attributes are weighted in accordance with their influence and importance. The model is validated by using empirical and expert opinion to compare with the model results on several large commercial object-oriented systems. A key attribute of the model is that it can be easily modified to include different relationships and weights, thus providing a practical quality assessment tool adaptable to a variety of demands. Index Terms ÐQuality model, quality attributes, design metrics, product metrics, object-oriented metrics. æ 1I NTRODUCTION T HE demand for quality software continues to intensify due to our society's increasing dependence on software and the often devastating effect that a software error can have in terms of life, financial loss, or time delays. Today's software systems must ensure consistent and error free operation every time they are used. This demand for increased software quality has resulted in quality being more of a differentiator between products than it ever has been before. In a marketplace of highly competitive products, the importance of delivering quality is no longer an advantage but a necessary factor for companies to be successful. While there is uniform agreement that we need quality software, the question of how, when, and where you measure and assure quality are far from settled issues. The switch to the object-oriented paradigm has changed the elements that we use to assess software quality. Traditional software product metrics that evaluate product characteristics such as size, complexity, performance, and quality must be changed to rely on some fundamentally different notions such as encapsulation, inheritance, and polymorphism which are inherent in object-orientation. This has led to the definition of many new metrics [8], [15], [20] to measure the products of the object-oriented approach. However, the new object-oriented metrics are varied in what they measure, how they are used in measuring, and when they are applicable. Many of the newer metrics have only been validated with small, and sometimes nonrealistic data sets and, therefore, the practical applicability and effectiveness of the metrics on large complex projects such as those encountered in an industrial environment is not known. Finally, if the goal is assessing the external quality
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 09/06/2009 for the course CIS 12414 taught by Professor Deloach,scotta during the Spring '09 term at Kansas State University.

Page1 / 14

AHierarchicalModelforOODesignQualityAssessment - 4 IEEE...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online