Abstract
Due to required efforts and the challenges involved in understanding the quantification of software quality, researchers have chosen varying quality attributes to describe the quantification of software quality. The degree of software quality is achieved from the standards and quality attributes at each development process: the adherence of software engineering principles towards realizing a product of good quality. In agile environment, the software engineering process ensures that qualities of interest are built-in and to produce software product with an acceptable level of quality. Thus, this study is aimed at quantifying six related software quality attributes. The specific objectives include identifying the software quality attributes, the design of the algorithm for measurement metrics, and to perform relational analytics of each attribute with respect to the software quality. The methodology followed an exploratory evaluation of measurement and metrics and their role in quantifying software quality in agile development environment. The study adopted existing metrics to quantify software quality attributes. Twelve opensource software projects were tested for 6 specific quality attributes and each result is quantified and presented. Results show that software number 2 (SW2) has a maintainability value of 6 minutes, 50% availability, and 0.62 reliability values. It implies that a high value of maintainability does not translate to high reliability. These values establish the relationship between attributes and enhances developers and users’ understanding of the software quality and its attributes.
Highlights
The agile framework emphasised on continuous delivery of quality applications through object-oriented modelling and universal modelling language but silent on the process of quantifying the quality of the ensuing software
The rest of the study is structured as follows: section 2 presents the correlation between measurement and metrics; section 3 presents the related works to this study; section 4 is the methodology; and section 5 presents the results of the study and the conclusion drawn from them
It is observed that through quantification, software quality when broken down to varying quality attributes indicate the lack of software product with 100% quality
Summary
The agile framework emphasised on continuous delivery of quality applications through object-oriented modelling and universal modelling language but silent on the process of quantifying the quality of the ensuing software. Over the years, commonly suggest that, to build-in acceptable level of quality in software, each development process must adhere to its standards and quality attributes [2, 3]. This implies that established software quality control inputs should be performed in the engineering process to ensure that the final software product has an acceptable level of quality. In practice, quantification of software quality has fallen short of detailed explanation especially in organisations where it has not been a norm from the inception [5] To reduce this ambiguity and improve on the quality, [5] is of the view that stakeholders should clearly define system requirements and present understandable attributes. The rest of the study is structured as follows: section 2 presents the correlation between measurement and metrics; section 3 presents the related works to this study; section 4 is the methodology; and section 5 presents the results of the study and the conclusion drawn from them
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
