Empirical Analysis of Metrics Using UML Class Diagram

Quality assessment of software is big issue for software development team The reason is variations of designed software in size and methodology. A huge number of metrics has designed to assess quality of software up to a level. In this paper we are discussing Object oriented metrics used to assess quality of software at design level as well as at code level. Although correct assessment of software quality is not possible but using Object oriented metrics quality can be assessed up to limit. The main focus of research is to assess software quality at design level because design level quality assessment effects coding, testing, maintaining phase of software development life cycle. First, for evaluating metrics of design level UML diagram is used as an input. A Java Parser is designed for parsing the XML code of UML diagram .Second, Quality of same software projects also assessed at code level using same formula as at the design level. At code level Eclipse with Metrics 1.3.6 is used for assessing quality. We observed that software quality at code level moves around CC (Cyclometer Complexity), LCOM (Lack Cohesion of Methods) and LOCM (Lines of Code of method).And we find out that for increasing quality of software, CC and LCOM and LOCM are low. For decreasing quality CC, LCOM and LOCL are high.

Abstract - Measurement of the maintainability and its factors is a typical task in finding the software quality on development phase of the system. Maintainability factors are understandability, modifiability, and analyzability…etc. The factors Understandability and Modifiability are the two important attributes of the system maintainability. So, metric selections for the both factors give the good results in system of maintainability rather than the existed models. In the existing metrics obtained for Understandability and Modifiability factors based on only generalization (inheritance) of the structural properties of the system design. In this paper we proposed SatyaPrasad-Kumar (SK) metrics for those two factors with help of more structural properties of the system. Our proposed metrics were validated against the Weyker’s properties also and got the results in good manner. When compare our proposed metrics are better than the other well-known OO (Object-Oriented) design metrics in getting the Weyker’s properties validation. Keywords – Understandability; Modifiability; Structural metrics; System Maintainability,; Weyker’s properties; SK metrics; OO design; International Journal of Computer Science and Information Security (IJCSIS), Vol. 13, No. 10, October 2015 https://sites.google.com/site/ijcsis/ ISSN 1947-5500

2001

The quality of class diagrams is critical because it has a great influence on the quality of the object oriented information system (OOIS) which are finally delivered. This fact motivated us to define a set of measures for evaluating the structural complexity (an internal quality attribute) of class diagrams made using the Unified Modeling Language (UML), which nowadays is the standard language for object oriented modelling. These measures could be used to predict class diagram external quality characteristics, such as maintainability, early in the OOIS life-cycle. In order to corroborate the practical utility of those metrics, we have put them under empirical validation by means of a controlled experiment. The description of each of the steps carried out to perform the experiment and the construction of the prediction model for class diagram maintainability are the main goals of this paper.

Journal of Information Engineering and Applications, 2019

Time, effort and money required in maintaining software has always been considered greater than its development time. Also, its ambiguity in forecast at early stage of software development makes the process more complicated. The early estimation of maintainability will significantly help software designers to adjust the software product, if there is any fault, in early stages of designing. By doing this; time, effort and money required in maintaining software will be lessened. Although Object Oriented Software Development (OOSD) approach is equipped for enhancing software maintainability, a method for finding out if the required level of maintenance is being achieved amid the development process is required. This can be accomplished through measurement. This paper outlines the need and importance of maintainability at design phase and develops a Metrics-Based Maintainability Estimation Framework for Object-Oriented software(MEFOOS) that estimates the maintainability of object oriented software components in regard of their Understandability, Modifiability and Portability-which are the sub-attributes of maintainability.

Software quality is an integral aspect of development scheme that determines the degree to which the software in use will meet the expectations of the customer. Maintainability has obtained its significance as an attribute of software quality. However in spite of the importance, there are no definite criteria to measure it. Hence great research interest is required for developing and applying sophisticated techniques to estimate software maintenance effort. As the object-oriented systems use a large number of small methods, a unique maintenance problem is associated with it. The relationship between OO metrics and software maintenance effort is complex and non linear. This paper surveys the different studies regarding software maintainability on object-oriented paradigm which provide further assistance in succeeding researches.

Journal of King Saud University - Computer and Information Sciences, 2007

This paper describes an integrated single class based metric called Weighted Class Complexity (WCC) for object oriented design. The metric is discussed from measurement theory viewpoint, taking into account the recognized object oriented features which the metrics was intended to measure encapsulation, inheritance, coupling and polymorphism, and the quality factors efficiency, complexity, understandability, reusability and maintainability/testability. Empirical data, collected from eight different application domains, is then analyzed using WCC metric to support this theoretical validation. The result shows that the proposed metric could be used to provide an overall quality assessment of object oriented software system in early stage of development life cycle, which may be helpful to the developer to fix problems, remove irregularities and non-conformance to standards and eliminate unwanted complexities in the early development cycle. Early use of this metric may help to ensure that the analysis and design have favorable internal properties that will lead to the development of quality end product. WCC may significantly help in reducing rework during and after implementation to design effective test plans. However, further studies are needed before these results can be generalized.

International Journal of Intelligent Systems and Applications, 2016

Software maintenance is one of the main quality characteristics of the software product. The maintainability of a system is a measure of the ability of the system to undergo maintenance or to return to normal operation after a failure. In this paper, a new model to improve the maintainability of object-oriented software has been proposed. The proposed model is based on newer versions of software quality standard and it is according to the measurement of several new metric. This model has been evaluated on famous PHP framework and the results showed that the proposed model is effective compared with the previous models.

IJCSNS, 2011

Software metrics are required to measure quality in terms of software performance and reliability related characteristics like dependencies, coupling and cohesion etc. It provides a way to measure the progress of code during development and having direct relationship with cost and time incurred in the software design and development at their later stages. These major issues must be checked and informed early in the development stage, so that reliability of any software product could be ensured for any large and complex software project. Object oriented software metrics directly focuses on the issues like complexity, reliability and robustness of the software developed using object oriented design methodologies. It reflects the time, cost and effort that would be incurred in development at later stage. While the software in its development stage, it is desirable that the complexity levels at every stage should be minimized to make the end product more reliable and manageable. Object oriented metrics provides all parameters through which one can estimate the complexities and quality related issues of any software at their early stages of development. In this paper, authors have studied three object oriented metrics namely MOOD Metrics, CK Metrics, and QMOOD Metrics and given a case study to show, how these metrics are useful in determining the quality of any software designed by using object oriented paradigm.

ISRN Software Engineering, 2013

Software developers require information to understand the characteristics of systems, such as complexity and maintainability. In order to further understand and determine characteristics of object-oriented (OO) systems, this paper describes research that identifies attributes that are valuable in determining the difficulty in implementing changes during maintenance, as well as the possible effects that such changes may produce. A set of metrics are proposed to quantify and measure these attributes. The proposed complexity metrics are used to determine the difficulty in implementing changes through the measurement of method complexity, method diversity, and complexity density. The paper establishes impact metrics to determine the potential effects of making changes to a class and dependence metrics that are used to measure the potential effects on a given class resulting from changes in other classes. The case study shows that the proposed metrics provide additional information not sufficiently provided by the related existing OO metrics. The metrics are also found to be useful in the investigation of large systems, correlating with project outcomes.

Lecture Notes on Software Engineering, 2015

Software measurement tools have been used to support quality assurance through the development cycle with an increasing popularity recently. However, understanding the results of these tools still is a big problem. They generally present polymetric views which are too complex and hard to comment on. In this study, a software tool was developed to present metrics in UML class diagrams. Colors of traffic lights are used to colorize the status of units in classes. Status is determined by techniques called limit and point approaches. Tool includes common structured and class based complexity metrics and only parses C# grammar presently. Finally a survey is applied to computer engineering students taken software engineering course. The obtained feedback is affirmative and useful for further steps.