Software Product Quality Models, Developments, Trends, and Evaluation

Abstract

Software product quality models have evolved in their abilities to capture and describe the abstract notion of software quality since the 1970s. Many models constructed deal with a specific part of software quality only which makes them ineligible to assess the quality of software products as a whole. Former publications failed to thoroughly examine and list all the available models which attempt to describe each known property of software product quality. This paper discovers such complete software product quality models published since 2000; moreover, it endeavours to measure the relevance of each model quantitatively by introducing indicators with regard to the scientific and industrial community. The identified 23 software product quality model classes differ significantly in terms of publication intensity, publication range, quality score average, relevance score and the 12-month average of the Google Relative Search Index. The results offer a foundation for selecting the appropriate software product quality model for use or for extension if newly identified quality properties need to be connected to a general context. Furthermore, the experiences accumulated on the field of software product quality modelling motivated researchers to successfully transfer the concepts to other areas where abstract entities need to be compared or assessed including the quality of higher educational teaching and business processes, which is also briefly highlighted in the paper.

Quality evaluation models or frameworks for open source software: A systematic literature review

“…As shown in Table 4, 58% of the QEMoF proposed in the literature are of general purpose, which is recommended for measuring general OSS quality. These are more comprehensive as they define quality properties to cover all aspects of OSS quality 33 and have a wider application domain. The remaining 42% of the QEMoF proposed are of specific purpose, which only deals with a specific part of OSS quality and has a particular domain of application such as issue tracking system and web application.…”

A Survey on Blockchain Acquainted Software Requirements Engineering: Model, Opportunities, Challenges, and Future Directions

“…The blueprint is also known as a software requirement specification (SRS) which contains the final set of requirements for the system under development. The SRS consists of two essential requirement categories namely functional and non-functional [22]. Functional requirements are based on features while non-functional requirements are based on outside scope.…”

Quality Properties of Execution Tracing, an Empirical Study

“…Quality assessment examines to which extent concrete quality requirements are satisfied. This activity is performed along defined variables, i.e., quality properties, in all the identified quality models in [36]. Moreover, variables are necessary to define to be able to capture a manageable part of quality.…”

“…Galli et al analysed all the software product quality models defined and published in the past 20 years; moreover, the investigation was extended to the application of such models including their tailoring [36]. The partial software product quality models were ruled out from the analysis, as these models give up the aim to define quality properties to cover the whole set of software product quality.…”

“…On the other hand, quality models, which aim to consider each aspect of software product quality are designated in the present paper as complete software product quality models even if completeness means an elusive target in a precise sense. The models identified in this manner were classified and assigned to software product quality model families to indicate whether a new software product quality model was born or merely enhancements of a previous model were published [36]. If the model published built on previous models but introduced new concepts, then it was regarded as a new software product quality model.…”