Abstract
In this paper, I discuss what I believe is the grand challenge facing the software quality research community: the ability to accurately determine, in the very earliest stages of development, the techniques that will be needed to achieve desired levels of non-functional attributes such as: reliability, availability, fault tolerance, testability, maintainability, performance, software safety, and software security. I will further consider the associated technical and economic tradeoffs that must be made in order to: (1) achieve these desired qualities, and (2) to certify that these qualities will be exhibited when the software is deployed. And I will also take into account the fact that satisfying a particular level of each attribute requires specific expenditures, some of these attributes conflict with each other, and when the environment or usage profile of the software is modified, all guarantees or claims of quality should be viewed suspiciously until additional evidence is provided.
Similar content being viewed by others
References
Morell, L. and Voas, J. 1993. A framework for defining semantic metrics, J. of Systems and Software 20: 245–251.
Viega, J. and McGraw, G. 2001. Building Secure Software, Addison-Wesley, Reading, MA.
Voas, J. 1997. Can clean pipes produce dirty water?, IEEE Software 14(4): 93–95.
Voas, J. 1998. Certifying off-the-shelf software components, IEEE Computer 31(6): 53–59. (Translated into Japanese and reprinted in Nikkei Computer magazine.)
Voas, J. 1998. Maintaining component-based systems, IEEE Software 15(4): 22–27. (Reprinted in the Moscow Open Systems Journal, Volume 6, 1998.)
Voas, J. 2000. Can chaotic methods improve software quality predictions?, Quality Time Column, IEEE Software 17(5): 20–22.
Voas, J. 2000. Toward a usage-based software certification process, IEEE Computer 33(8): 32–37.
Voas, J. 2001. Faster, better, and cheaper, Quality Time Column, IEEE Software 18(3): 96–97.
Voas, J. and Miller, K. 1995. Software testability: the new verification, IEEE Software 12(3): 17–28.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Voas, J. Trusted Software's Holy Grail. Software Quality Journal 11, 9–17 (2003). https://doi.org/10.1023/A:1023679926998
Issue Date:
DOI: https://doi.org/10.1023/A:1023679926998