The interesting thing about this model is that it's ubiquitous: there's nothing inherently software-centric about the model, though it was written with software in mind. In fact, it's a pretty good checklist for anyone (and everyone) interested in delivering good quality to their beneficiaries.
Have a look:
Functionality - A set of attributes that bear on the existence of a set of functions and their specified properties. The functions are those that satisfy stated or implied needs.
Reliability - A set of attributes that bear on the capability of software to maintain its level of performance under stated conditions for a stated period of time.
- Suitability
- Accuracy
- Interoperability
- Security
- Functionality Compliance
Usability - A set of attributes that bear on the effort needed for use, and on the individual assessment of such use, by a stated or implied set of users.
- Maturity
- Fault Tolerance
- Recoverability
- Reliability Compliance
Efficiency - A set of attributes that bear on the relationship between the level of performance of the software and the amount of resources used, under stated conditions.
- Understandability
- Learnability
- Operability
- Attractiveness
- Usability Compliance
Maintainability - A set of attributes that bear on the effort needed to make specified modifications.
- Time Behaviour
- Resource Utilisation
- Efficiency Compliance
Portability - A set of attributes that bear on the ability of software to be transferred from one environment to another.
- Analyzability
- Changeability
- Stability
- Testability
- Maintainability Compliance
- Adaptability
- Installability
- Co-Existence
- Replaceability
- Portability Compliance
