People probably have a lot of different answers here, like good...: scalability, speed, usability, stability, consistency, completeness, absence of bugs, accessibility, documentation, code-quality and so on.

There are a lot of philosophies on development of software. Like the UNIX-philosophy. Often vague and not easy to understand.

I am looking for statements such as the one cited below.

Which you can ask about the software when it's in the design-stage, is ready to be coded, and has been coded and is ready for launch.

The software I am talking about, is of course the software made for the end-user.

Ken Rockwell wrote: "I expect that it will let me get more accomplished in less time." (Here one could ask "will this let me get more accomplished in less time?")