Answers are grounded in this paper and cite their sources.
Concrete and useful suggestions about what constitutes quality software have always been elusive. I suggest a framework for the construction and use of practical, testable quality models for requirements, design and implementation. Such information may be used directly to build, compare, and assess better quality software products.
No takes yet. Share an insight, caveat, or question.
R. Geoff Dromey (1996) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: