Article Preview
Top1. Introduction
Object Oriented design (OO) quality is a topic of great interest for the scientific research and the development of software system. In the maintenance phase of software life cycle, many studies were achieved on OO design quality assurance (Bansiya and Davis, 2002; Chauhan et al., 2014; Srinivasan and Devi, 2014c).
Software quality requires the compliance of software product for defined functions and specified quality level (Card and Agresti, 1987). The guarantee of quality level for a software project requires the quality attributes and appropriate metrics (Arvanitou et al., 2017). On the other hand, The software validity is depending on some quality factors at a certain acceptable level (Blundell et al., 1997).
Metrics can be used to measure the quality of software. Software metrics can be divided into two categories: Product metrics and process metrics (Wand and Weber, 1995):
- •
Product Metrics: They are generally used to evaluate the attributes of the software. Product metrics, also known as quality metrics are composed of different metrics and properties including complexity, size, style, usability, functionality, performance and non-reliability.
- •
Process Metrics: They are effective to measure the attributes of the software process during the development of software product. Process metrics, also known as management metrics are composed of different metrics and properties including cost, advancement, effort and reusability.
A software quality attribute is calculated or evaluated by a set of metrics (Arvanitou et al., 2017). The authors (Kochar et al., 2017) defined the impact of design metrics on different types of software quality attributes. In this paper, we exploit the relationship between products metrics and quality attributes to propose a new approach for studying the software quality. This approach consists in formal intended modeling for the evaluation of finite state automaton. We give in section 2 the problematic description. Our proposal approach is discussed in section 3. Section 4 is reserved for experimentation. In section 5, we discuss the obtained results. Finally, section 6 closes this paper with a general conclusion and some perspectives.
TopMany studies were performed in the context of software design quality. The authors (Rawat et al., 2012) investigated the impact of software metrics on software quality and reliability. Dagpinar and Jahnke presented an empirical study for the maintainability prediction owing to Object-Oriented design metrics (OO) (Dagpinar and Jahnke, 2003). The authors (Abdi et al., 2009; Dahane et al., 2019; Srinivasan and Devi, 2014b) verified the suitability of certain OO design metrics about maintainability.
Subramanyam and Krishnan used CK (Chidamber and Kemerer) metrics to confirm that the metrics play an important role in design aspects (Subramanyam and Krishnan, 2003). The authors (Chauhan et al., 2014) used OO design metrics MOOD (Metrics for OO Design) and CK Metrics to estimate the quality of software product implemented according to the object-oriented paradigm.
The authors (Bansiya and Davis, 2002) proposed a hierarchical model based on OO design metrics and quality attributes for the study and evaluation of OO design quality named QMOOD (Quality Metrics for OO Design). This model is used to generate a quality index for an input software system.