[eluser]Jondolar[/eluser]
I'm reading a book called Object Oriented Analysis and Design which discusses the responsibility of a programmer/designer when working with clients. It talks about how to gather requirements by using use cases. The interesting tone of the book is that if you don't deliver what your customer wants "even if they don't tell you what they want the first time" it is really your fault/issue. The goal of the book is to get you to find out what your clients "really" want and to build them an application that will actually work for them.
