Requirements Are Not the Same as Expectations

For many years , computing people have searched for techniques and tools to assist in the analysis and modeling of requirements. Techniques such as use case, data flow diagrams, data models, and even ( shock ! horror !) flow charts are useful in de termining the system functionality, data, and events, but they offer little assistance in modeling the "softer" requirements that are a key part of the business client's expectations.

"What are your requirements?" is the wrong question. The right question is, "What is your world?" Once we have begun to understand our client's organizational culture, their pressures, their concerns, and their way of working, we can begin to get a clearer idea of them and then it becomes much easier to understand their requirements.

To understand their systems, we need to understand their organizational culture, their dreams, and their expectations.