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.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
ISO 9126 Information technology - Software product evaluation - Quality characteristics and guidelines for their use, International Organisation for Standardization, Geneva, 1992.
T. Gilb, Principles of Software Engineering Management. Addison-Wesley, 1987
B.W. Boehm, J.R. Brown, H. Kaspar, M. Lipow, G.J. Macleod, and M.J. Merrit, Characteristics of Software Quality.North-Holland, 1978.
T.P. Bowen, G.B. Wigle, and J. Tsai. Specification of software quality attributes. Volumes 1, 2 and 3. D182-11678-1/2/3, Prepared by Boeing for RADC, 1984.
J.A. McCall, P.K. Richards, and G.F. Walters, Factors in Software Quality (3 volumes), RADC reports, 1978.
B.A. Kitchenham. Software quality assurance. Microprocessors and Microsystems, 13(6), (1989), 373-381.
B.A. Kitchenham, and S.L. Pfleeger, Software quality - the elusive goal. IEEE Software, 13(1), (1996), 12-21.
G. Frewin, P. Hamer, B. Kitchenham, N. Ross, and L. Wood. Quality measurement and modelling - state of the art report. REQUEST Report to the CEC ESPRIT programme, R1.1.1, 1984.
P.G. Petersen, and B.A. Kitchenham. The development of a software quality model. Proceedings of 1st European Conference on Software Quality, Brussels, 1988.
B.A. Kitchenham, and J.G. Walker. A quantitive approach to monitoring software development. Software Engineering Journal, 4(1), (1989), 2-13.
W.W. Agresti, and W.M. Evanco, Projecting software defects from analyzing Ada designs. IEEE Transactions on Software Engineering, 18(11), (1992), 988-997.
L.C. Briand, V.R. Basili and W.M. Thomas. A pattern recognition approach for software engineering data analysis. IEEE Transactions on Software Engineering, 18(11), (1992), 931-942.
B.A. Kitchenham, S.G. Linkman, J. Boegh and A. Pasquini. Report RD 3.7/1 SQUID Conceptual Handbook, 1996, A publicly available deliverable which may be obtained by contacting the Project Coordinators CAP-VOLMAC Daltonlan, Utrecht, Holland.
R.G. Dromey. A model for software product quality. IEEE Transactions on Software Engineering, 21(2), (1995) 146-162.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Kitchenham, B., Linkman, S., Pasquini, A. et al. The SQUID approach to defining a quality model. Software Quality Journal 6, 211–233 (1997). https://doi.org/10.1023/A:1018516103435
Issue Date:
DOI: https://doi.org/10.1023/A:1018516103435