The SQUID approach to defining a quality model

  • Authors:

  • Barbara Kitchenham;Steve Linkman;Alberto Pasquini;Vincenzo Nanni

  • Affiliations:

  • Department of Computer Science, University of Keele Keele ST5 5BG UK;Department of Computer Science, University of Keele Keele ST5 5BG UK;-;-

  • Venue:
  • Software Quality Control
  • Year:
  • 1997

Quantified Score

Hi-index 0.00

Visualization

Abstract

This paper describes an attempt to use the approach developed by the SQUIDproject, which was part of the ESPRIT 3 programme, to define the software quality requirements of the Telescience project. The SQUID project developed its approach to quality modelling in parallel with ongoing feedback from testing that approach on the Telescience project, which was both large and software intensive.As part of this exercise we used the ISO software quality standard ISO 9126. It was an assessment of this and other existing quality models that caused us to re-assess what was meant by a quality model and led to a decomposition of existing ‘quality models‘ into a composite model reflecting the different aspects of the model and its mapping onto a specific project or product. We break existing quality models into components which reflect the structure and content of the model. This composite model must then be customized for an individual product/project, we call this customized model a ‘Product Quality Model‘.Application of this approach to the Telescience project identified a number of practical problems that the SQUID project needed to address. It also indicated a number of problems inherent in the current version of ISO 9126.