Thus successful design must understand not what users (say they) want,
    but much more fundamentally, why they want, i.e.,

• What are their underlying basic values?

Analysts also cannot know what users need:

• Computer-based systems are in larger distributed socio-technical systems,
• which no one fully understands;
• also time-to-market pressure.

Refine understanding of values, users, requirements, specs, code,
    by use in context, on real cases.

So called waterfall process is a disaster:
    therefore agile programming, extreme programming, etc.
But still have errors, anxiety, failures, and hope & fear cycles.