Redefining Software Quality
gojko.net
gojko.net
Personally I would reorder this with Useful at the bottom, then Functional, then Usable. It doesn't even need to work for you to ask people, "If you had a magic button that you could do this thing for you, would you want it?" Maybe this is edging towards "Product Quality" rather than "Software Quality", but I think the two are intertwined.
When pushed, we generally talk about quality products, usually high end cars like Porsche, Mercedes or Audi. We think of these as quality products because people are willing to pay large amounts for them. Their customers like the product enough to part with their hard earned cash.
However, If you agree with the agile manifesto, then "working software is the primary measure of progress", I think that gives the "zen-like sentence" you're talking about.
To help make it easier to understand, you can break down "working software" into two parts:
1. Objective, from a craftsmanship perspective, you can measure code coverage, performance and bugs.
2. Subjective, from a customer perspective, Does it meet their expectations? Is it useful, and secure? What are they comparing it to?
Hopefully you'll find this is easier to use than another pyramid.
Speaking of Zen, this is the core plot of Zen and the Art of Motorcycle Maintenance.
Someone hasn't read Zen and the Art of Motorcycle Maintenance
Just like "quality." I mean "Quality."