Page 36 - Demo

PROFIT
and hope the system performs the way they explained it to the analyst in the first place.
The analyst has done the best job he knows how to map the documentation and specifications to fit the user's needs. But the only point when the user will know how close he has come is when the system is complete. Only then will he have a good idea of what he is getting. Until then, he must just assume that it will be what he needs.
When we are building an office building, the construction follows a very structured predefined process. But when we are creating business software, a structured process like this just drives out all opportunities for creative thinking.
The Power of Narrative
The kind of documentation we really need is of an entirely different form. Rather than system documentation, we just need a written description of what this solution would be like. It should read more like a story than a system manual.
36