Object oriented software metrics kidd

Abstract - Cited by 79 26 self - Add to MetaCart Reverse engineering software systems has become a major concern in software industry because of their sheer size and complexity. In this article we present the concept of a polymetric view, a lightweight software visualization technique enriched with software metrics information.

Polymetric views help to understand the structure and detect problems of a software system in the initial phases of a reverse engineering process. We discuss the benefits and limits of several predefined polymetric views we have implemented in our tool CodeCrawler. Moreover, based on clusters of different polymetric views we have developed a methodology which supports and guides a software engineer in the first phases of a reverse engineering of a large software system.

We have refined this methodology by repeatedly applying it on industrial systems, and illustrate it by applying a selection of polymetric views to a case study. Citation Context The reengineering and reverse engineering of software systems is gaining importance in software industry, because the accelerated turnover in software companies creates legacy systems in a shorter period of time.

Especially understanding classes is a key activity in object-oriented programming, sinc Abstract - Cited by 62 20 self - Add to MetaCart The reengineering and reverse engineering of software systems is gaining importance in software industry, because the accelerated turnover in software companies creates legacy systems in a shorter period of time.

Especially understanding classes is a key activity in object-oriented programming, since classes represent the primary abstractions from which applications are built. The main problem of this task is to quickly grasp the purpose of a class and its inner structure. To help the reverse engineers in their first contact with a foreign system, we propose a categorization of classes based on the visualization of their internal structure.

The contributions of this paper are a novel categorization of classes and a visualization of the classes which we call the class blueprint. We have validated the categorization on several case studies, two of which we present here. As systems evolve and their structure decays, maintainers need accurate and automatic identification of the design problems.

Current approaches for automatic detection of design problems are not accurate enough because they analyze only a single version of a system and consequently they miss essenti Abstract - Cited by 43 9 self - Add to MetaCart As systems evolve and their structure decays, maintainers need accurate and automatic identification of the design problems.

Current approaches for automatic detection of design problems are not accurate enough because they analyze only a single version of a system and consequently they miss essential information as design problems appear and evolve over time. Our approach is to use the historical information of the suspected flawed structure to increase the accuracy of the automatic problem detection. Our means is to define measurements which summarize how persistent the problem was and how much maintenance effort was spent on the suspected structure.

We apply our approach on a large scale case study and show how it improves the accuracy of the detection of God Classes and Data Classes, and additionally how it adds valuable semantical information about the evolution of flawed design structures. Shimba, a prototype reverse engineering environment, has been built to support the understanding of Java software. Shimba uses Rigi and SCED to analyze, visualize, and explore the static and dynamic aspects, respectively, of the subject system.

The static software artifacts and their dependencies ar Abstract - Cited by 27 1 self - Add to MetaCart Shimba, a prototype reverse engineering environment, has been built to support the understanding of Java software. The static software artifacts and their dependencies are extracted from Java byte code and viewed as directed graphs using the Rigi reverse engineering environment.

The static dependency graphs of a subject system can be annotated with attributes, such as software quality measures, and then be analyzed and visualized using scripts through the end-user programmable interface. Shimba has recently been extended with the Chidamber and Kemerer suite of object-oriented metrics.

The metrics measure properties of the classes, the inheritance hierarchy, and the interaction among classes of a subject system. Since Shimba is primarily intended for the analysis and exploration of Java software, the metrics have been tailored to measure properties of softwa This paper describes techniques for analyzing large UML models. The first part of the paper describes heuristics and processes for creating semantically correct UML analysis and design models.

The second part of the paper briefly describes the internal DesignAdvisor research tool that was used to an The second part of the paper briefly describes the internal DesignAdvisor research tool that was used to analyze Siemens models. The results are presented and some interesting conclusions are drawn. This paper proposes some new software metrics that can be applied to UML modelling elements like classes and messages. We're sorry! We don't recognize your username or password.

Please try again. The work is protected by local and international copyright laws and is provided solely for the use of instructors in teaching their courses and assessing student learning. You have successfully signed out and will be required to sign back in should you need to download more resources. Out of print.

Object-Oriented Software Metrics. If You're an Educator Additional order info. Overview Features Contents Order Overview.

Description For programmers interested in object-oriented technology. Table of Contents I. Project Metrics.