Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #17889

Re: Who gets interviewed to produce use cases?

Show all headers | View raw

On Tue, 14 Aug 2012 15:35:51 -0500, Leif Roar Moldskred
<leifm@dimnakorr.com> wrote:

>Leif Roar Moldskred <leifm@dimnakorr.com> wrote:
>> 
>> Another problem -- or perhaps rather a restating of the first problem
>> you mentioned -- is that even users with a very good _implicit_
>> knowledge of their work process often have a poor _explicit_
>> understanding of it. Often, a lot of important business requirements
>> are overlooked because the users either plain doesn't realise that
>> they're there, or because they take them as implicitly understood.
>> 
>> For the same reason, users are often terrible at prioritising between
>> features and choosing between different solutions. Often, the highest
>> priority goes to whichever feature the user thought of most recently.

>Commenting to my own post here, but I really should add that the above
>isn't to mean that the software developers know best and should
>overrule the customer on requirements and priorities. Far from
>it. (Well, _sometimes_ we should do that for _technical_ requirements,
>but only sometimes.) It's still the users that actually _knows_ the
>requirements, but sometimes they don't know what they know.

     It is some of this, some of that.  I have worked with one cient
for nearly 25 years.  I know some of his requirements to the point
where I need not discuss them with him.  Some are his to the point
where I do not know in detail why he wants it.  In the middle are the
ones we discuss.  We respect each other and come up with a plan.

>Gathering requirements thus often turn into an explanatory dig into
>the user's work process and business, and you often end up with not
>only having the users teach the software developers about the buisness
>domain but also with the software developers having to teach the users
>about requirement gathering.

     Again, quite.

Sincerely,

Gene Wirchenko

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Who gets interviewed to produce use cases? David Lamb <dalamb@cs.queensu.ca> - 2012-08-07 14:26 -0400
  Re: Who gets interviewed to produce use cases? Robert Klemme <shortcutter@googlemail.com> - 2012-08-07 22:13 +0200
  Re: Who gets interviewed to produce use cases? Lew <lewbloch@gmail.com> - 2012-08-07 13:47 -0700
    Re: Who gets interviewed to produce use cases? Gene Wirchenko <genew@ocis.net> - 2012-08-07 14:23 -0700
      Re: Who gets interviewed to produce use cases? Lew <lewbloch@gmail.com> - 2012-08-07 14:54 -0700
      Re: Who gets interviewed to produce use cases? David Lamb <dalamb@cs.queensu.ca> - 2012-08-08 09:47 -0400
        Re: Who gets interviewed to produce use cases? Gene Wirchenko <genew@ocis.net> - 2012-08-08 09:48 -0700
        Re: Who gets interviewed to produce use cases? Arne Vajhøj <arne@vajhoej.dk> - 2012-08-12 22:57 -0400
    Re: Who gets interviewed to produce use cases? David Lamb <dalamb@cs.queensu.ca> - 2012-08-08 09:44 -0400
    Re: Who gets interviewed to produce use cases? Arne Vajhøj <arne@vajhoej.dk> - 2012-08-12 22:53 -0400
  Re: Who gets interviewed to produce use cases? Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2012-08-08 11:41 +0300
  Re: Who gets interviewed to produce use cases? Arne Vajhøj <arne@vajhoej.dk> - 2012-08-12 22:48 -0400
    Re: Who gets interviewed to produce use cases? Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-08-13 05:32 -0500
      Re: Who gets interviewed to produce use cases? Gene Wirchenko <genew@ocis.net> - 2012-08-14 12:35 -0700
      Re: Who gets interviewed to produce use cases? Leif Roar Moldskred <leifm@dimnakorr.com> - 2012-08-14 15:35 -0500
        Re: Who gets interviewed to produce use cases? Gene Wirchenko <genew@ocis.net> - 2012-08-15 09:32 -0700

csiph-web