Applying Software Product Metrics in Software Maintenance

2003

2012

The software development process plays an important role in the field of Information & Telecommunicati on ( The project managers are emphasis to improve the quality of the software process. To provide the good quality product the developers are prominence on new improved approaches. Many researchers have proposed many approaches, but, the most promising ap proach is object orientation. With the development of the improved software also demand for the software measurement and also enhance the quality of services (QoS). Such metrics are needed or useful when the organization is adopting the new technology with the new programming standards. The purpose of this study is to have qualitative analysis by el evating design complexity of the software. In this paper, we investigate the problems in software development which includes understand-ability, maintainability, ability, security and encapsulation. The metrics an d the subset of metrics prevalent in practice. The anticipated outcomes ...

2010

Adequate metrics of object-oriented software enable to determine the complexity of a system, estimate the effort needed for testing and even locate some parts in the design that could be error prone or should be redesigned. The measurements and metrics are not widely used in the development of software. Contemporary systems are complex and adequate measuring tool is necessary in the design and evolution process. In this chapter we present how software metrics can be used in assessing software. Some software measuring tools (i.e. JMetrics, Essential metrics, Understand, X-Ray, Eclipse Metrics Plugin, Borland Together and Metrics) are briefly described. A critical comparison of these tools is also given. Next, a case study-an evaluation of three versions of a well known open source software-Junit is presented. To measure this application Metrics 1.3.6, an Eclipse plug-in, was used. The correlation of metrics values and real quality attributes of software is described. On the basis of metrics values some conclusions concerning the quality of the design of each version and some general trends in the evolution of JUnit project evolution are derived.

2012

Necessity for a Productive software has been culminating and Object-Oriented Design technique is providing solution to this as it is the most powerful mechanism for developing proficient software systems. It is helpful not only in declining the cost but also in the development of high quality software systems. Software developers require accurate metrics for developing efficient software system. Object-Oriented Metrics plays a significant role pertaining to this aspect because of their importance in the development of successful software applications. In this paper Assessment of the current state of the art in Metrics and Object-Oriented Software System Quality is done. Further it contains short descriptive taxonomy of the Object-Oriented Design and Metrics.

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.

2014

— Object oriented metrics have become more important in software engineering field. They are used to measure software quality and to estimate the cost, to enhance the reliability, maintainability and effort of software projects. Object oriented metrics evaluate the complexity of OO program. Object oriented concepts are dominating the software industry and engineers need proper measuring parameters in order to make software more efficient and reused. Object Oriented Design metrics is an essential part of software engineering. This paper collects many object oriented metrics proposed by various researchers and a final conclusion is to overcome the drawbacks of existing metrics and to deliver efficient metrics which is effectively used to measure the programs. Keywords-Software architecture; Coupling; cohesion; reusability; maintainability I.

International Journal of Computer Applications, 2011

Open source software systems are becoming more popular today, and are playing important roles in many scientific and business software applications. Many companies are investing in open source projects and lots of them are also using such software in their own work. But, because open source software is often developed with a different management style than the industrial ones, the quality and reliability of the code needs to be investigated. Hence, more projects need to be measured to obtain information about the characteristics and nature of the source code. In this paper we have evaluated the object-oriented metrics given by Chidamber and Kemerer, and few other static code metrics for two open source projects. We have carried out an empirical study and tried to find out the nature of relationship between these metrics and defects. In other words, it has been investigated whether these metrics are significantly associated with defects or not. For this we have extracted source code, defects processed it for metrics .Two open source java projects of emulators have been taken from source forge and used for this purpose.

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

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.

International Journal of Computer Applications, 2015

Object oriented metrics have become more important in software development environment. They are used to measure software quality and to estimate the cost, to enhance reliability, maintainability and effort of software projects. Object oriented metrics estimate the complexity of OO programs. This paper highlights all the object oriented metrics which are proposed in the last two decades such as CK metrics, Moose Metrics, QMOOD Metrics, GQM, MOOSE, LI Metrics, Chen Metrics, Lorenz Kidd Metrics, Reuse Metrics and EMOOSE. The need for such metrics is particularly acute when an organization is adopting a new technology for which established practices have yet to be improved. This research addresses these desires through the development and implementation of a suite of metrics for OO design. The equations and measurement calculation methods for all mentioned OO metrics are clearly defined. In this research paper a java program is taken as a model with OOP concepts such as inheritance, polymorphism, and abstraction. The above mentioned Object oriented metrics are applied on this java program and the results of each metrics are tabulated clearly. The objective of the research is to select the correct object oriented metrics for their models and application for software developers.

TJPRC, 2013

Software quality has been a major challenge in the software industry. Reliability is one of most important quality factors of any software and an important issue in the development of successful applications. Software reliability is affected by many factors during the life cycle of a software product. Software metrics provide a quantitative basis for planning and measuring software development process. By the introduction of object oriented technology and programming, software designers experience another paradigm shift in the field of software engineering. Available traditional software metrics are not sufficient for evaluating various software products. As a result, a set of new object oriented software metrics came into existence. In this work, we use CK metrics for measuring the reliability of software. A tool is designed and developed called „Java Class Analyzer‟ which extracts the values of the metric parameters from the source code. Based on the values of metric parameters extracted, some relationship is established between reliability and object oriented metrics. These results help the customer and producer to improve the software development process.

The Journal of Object Technology, 2006

The increasing importance of software measurement has led to development of new software measures. Many metrics have been proposed related to various constructs like class, coupling, cohesion, inheritance, information hiding and polymorphism. But there is a little understanding of the empirical hypotheses and application of many of these measures. It is often difficult to determine which metric is more useful in which area. As a consequence, it is very difficult for project managers and practitioners to select measures for object-oriented systems. In this paper we investigate 22 metrics proposed by various researchers. The metrics are first defined and then explained using practical applications. They are applied on standard projects on the basis of which descriptive statistics, principal component analysis and correlation analysis is presented. Finally, a review of the empirical study concerning chosen metrics and subset of these measures that provide sufficient information is given and metrics providing overlapping information are excluded from the set.

Software Process: Improvement and Practice, 2009

The importance of software measurement is increasing, leading to the development of new measurement techniques. Many metrics have been proposed related to the various objectoriented (OO) constructs like class, coupling, cohesion, inheritance, information hiding and polymorphism. The purpose of this article is to explore relationships between the existing design metrics and probability of fault detection in classes. The study described here is a replication of an analogous study conducted by Briand et al. The aim is to provide empirical evidence to draw the strong conclusions across studies. We used the data collected from Java applications for constructing a prediction model. Results of this study show that many metrics capture the same dimensions in the metric set, hence are based on comparable ideas and provides redundant information. It is shown that by using a subset of metrics prediction models can be built to identify faulty classes. The model predicts faulty classes with more than 90% accuracy. The predicted model shows that import coupling and size metrics are strongly related to fault proneness, confirming the results from previous studies. However, there are also differences reported in this study with respect to previous studies such as inheritance metric which counts methods inherited in a class is also included in the predicted model.

ArXiv, 2019

Software metrics offer a quantitative basis for predicting the software development process. In this way, software quality can be improved very easily. Software quality should be achieved to satisfy the customer with decreasing the software cost and improve there liability of the software product. In this research, we have discussed how the software metrics affect the quality of the software and which stages of its development software metrics have applied. We discussed the different software metrics and how these metrics have an impact on software quality and reliability. These techniques have been used for improving the quality of software and increase the revenue.