On the Use of Quality Models to Address Distinct Quality Views

Different software product quality models interpret different amounts of information, i.e., they can capture and address different manifestations of software quality. This characteristic can cause misleading statements and misunderstandings while explaining or comparing the results of software produ...

Full description

Bibliographic Details
Main Authors: Tamas Galli, Francisco Chiclana, Francois Siewe
Format: Article
Language:English
Published: MDPI AG 2021-07-01
Series:Applied System Innovation
Subjects:
Online Access:https://www.mdpi.com/2571-5577/4/3/41
_version_ 1797520286068768768
author Tamas Galli
Francisco Chiclana
Francois Siewe
author_facet Tamas Galli
Francisco Chiclana
Francois Siewe
author_sort Tamas Galli
collection DOAJ
description Different software product quality models interpret different amounts of information, i.e., they can capture and address different manifestations of software quality. This characteristic can cause misleading statements and misunderstandings while explaining or comparing the results of software product quality assessments. A total of 23 previously identified distinct software product quality models are analysed on how they handle the abstract notion of quality, and a taxonomy on the quality manifestations that the individual software product quality models are able to capture is established. Quality models that are able to solely describe the quality manifestation of the source code are attractive due to their full automation potential through static code analysers, but their assessment results ignore a huge part of software product quality, which is the one that most impresses the end user. The manifestations of software product quality that address the behaviour of the software while it operates, or the perception of the end user with regard to the software in use, require human involvement in the quality assessment. The taxonomy contributes to interpreting the quality assessment results of different quality models by showing the possible quality manifestations that can be captured by the identified models; moreover, the taxonomy also provides assistance while selecting a quality model for a given project. The quality manifestations used for the quality measurement always need to be presented, otherwise the quality assessment results cannot be interpreted in an appropriate manner.
first_indexed 2024-03-10T07:54:37Z
format Article
id doaj.art-dc1095bb14334e77b37e9fcfab887c14
institution Directory Open Access Journal
issn 2571-5577
language English
last_indexed 2024-03-10T07:54:37Z
publishDate 2021-07-01
publisher MDPI AG
record_format Article
series Applied System Innovation
spelling doaj.art-dc1095bb14334e77b37e9fcfab887c142023-11-22T11:58:36ZengMDPI AGApplied System Innovation2571-55772021-07-01434110.3390/asi4030041On the Use of Quality Models to Address Distinct Quality ViewsTamas Galli0Francisco Chiclana1Francois Siewe2Institute of Artificial Intelligence (IAI), Faculty of Computing, Engineering and Media, De Montfort University, Leicester LE1 9BH, UKInstitute of Artificial Intelligence (IAI), Faculty of Computing, Engineering and Media, De Montfort University, Leicester LE1 9BH, UKSoftware Technology Research Laboratory (STRL), Faculty of Computing, Engineering and Media, De Montfort University, Leicester LE1 9BH, UKDifferent software product quality models interpret different amounts of information, i.e., they can capture and address different manifestations of software quality. This characteristic can cause misleading statements and misunderstandings while explaining or comparing the results of software product quality assessments. A total of 23 previously identified distinct software product quality models are analysed on how they handle the abstract notion of quality, and a taxonomy on the quality manifestations that the individual software product quality models are able to capture is established. Quality models that are able to solely describe the quality manifestation of the source code are attractive due to their full automation potential through static code analysers, but their assessment results ignore a huge part of software product quality, which is the one that most impresses the end user. The manifestations of software product quality that address the behaviour of the software while it operates, or the perception of the end user with regard to the software in use, require human involvement in the quality assessment. The taxonomy contributes to interpreting the quality assessment results of different quality models by showing the possible quality manifestations that can be captured by the identified models; moreover, the taxonomy also provides assistance while selecting a quality model for a given project. The quality manifestations used for the quality measurement always need to be presented, otherwise the quality assessment results cannot be interpreted in an appropriate manner.https://www.mdpi.com/2571-5577/4/3/41software engineeringsoftware product quality modelquality assessmentquality viewSQALEISO25010
spellingShingle Tamas Galli
Francisco Chiclana
Francois Siewe
On the Use of Quality Models to Address Distinct Quality Views
Applied System Innovation
software engineering
software product quality model
quality assessment
quality view
SQALE
ISO25010
title On the Use of Quality Models to Address Distinct Quality Views
title_full On the Use of Quality Models to Address Distinct Quality Views
title_fullStr On the Use of Quality Models to Address Distinct Quality Views
title_full_unstemmed On the Use of Quality Models to Address Distinct Quality Views
title_short On the Use of Quality Models to Address Distinct Quality Views
title_sort on the use of quality models to address distinct quality views
topic software engineering
software product quality model
quality assessment
quality view
SQALE
ISO25010
url https://www.mdpi.com/2571-5577/4/3/41
work_keys_str_mv AT tamasgalli ontheuseofqualitymodelstoaddressdistinctqualityviews
AT franciscochiclana ontheuseofqualitymodelstoaddressdistinctqualityviews
AT francoissiewe ontheuseofqualitymodelstoaddressdistinctqualityviews