Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: David Lamb Newsgroups: comp.lang.java.programmer Subject: Re: Who gets interviewed to produce use cases? Date: Wed, 08 Aug 2012 09:47:54 -0400 Organization: A noiseless patient Spider Lines: 18 Message-ID: References: <023d634e-8bea-421f-a598-0bb668d44d38@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 8 Aug 2012 13:47:57 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="c397b0271b118225329a50c7668d0388"; logging-data="2221"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Co4IPLV8rMhi0G3kFEcJo" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: Cancel-Lock: sha1:zg577k9Y0hzeizxm9SqbIzV1DIs= Xref: csiph.com comp.lang.java.programmer:17351 On 07/08/2012 5:23 PM, Gene Wirchenko wrote: > And it could just be that the customer really does not know what > he wants. You can try describing it, but too often, he nods and then > complains later that it was not what he expected. Or the old "That's > just what I said, but it's not what I want!" I understand that. I was under the impression that "user centred design" involved a collection of practices meant to improve communication between customers and developers, of which UML use cases were one example. In fact I recently read parts of the 3 UML books I have on hand (reference, user's guide, and Unified Process) and found a statement to the effect that use cases in particular were designed to improve communications. But, as I said in answer to Lew upthread, I should have made clearer that use cases were just one example of the kind of user-centred requirements elicitation mechanisms I had in mind.