Software Developments Magic Triangle
spf13.com
spf13.com
"Quality" isn't something you can define readily. http://en.wikipedia.org/wiki/Software_quality lists 20 things, some mutually contradictory, that often are considered aspects of "quality" software.
I've become cynical about it. I know what I mean: software that never crashes, and runs rapidly. I don't know that managers, directors, senior directors, vice presidents, etc of development mean. I believe that vendors use the word 'quality" a lot when trying to get senior directors and VPs to buy into "enterprise software", like SharePoint or "Smart Filter" browser nannies, or any proprietary version control system that imposes a "lifecycle" on development. The vendors use "quality" because they know "quality" means a bunch of different things, and that Senior Directors and VPs never realize that "strict compliance with PCI" might not be the same "quality" that the developers think of, and it certainly isn't what the users think of.
stability and efficiency shouldn't be the only factors you focus on. An empty loop is pretty fast and stable, but wouldn't solve most of the problems you're expected to solve. It sounds like you're just taking all the other factors for granted, where in reality they're as hard or harder to get right as stability and efficiency.