>Roi,
>
>But here you've got to be carefull. Often users themselves don't know excactly what they want. The may say something like: "I need a button which pops up a form and shows me the more recent ordered articles of this client." Then you've got a choice: Don't ask anymore and start implementing this new feature, or ask: Why do you need this ?? The client may answer: "I want to check if the client has ordered this article before". Then you'd probaly add extra information on the form that displays the last date the client ordered that article (Or you could ask again: why do you want to know this ?, etc..).

Oh, I agree. You need to ask the user's why they want the things they ask for. You need to know what a feature's purpose is to implement it properly.

>
>This example shows that application development often is more an art than just a few rules.

Definately.