Dan Rawsthorne wrote:
> So, a use case can just be a name that acts as the organizing idea for a
> bunch of stories. I use the use case as the "bottom" of a function WBS that
> organizes work so that management can understand it (see
> http://www.netobjectives.com/resources/downloads/ManagingTheWork.pdf for a
> discussion of this concept.
>
> Now, the artifact we call a use case is a different thing. It has many
> forms, some of them more useful for deriving stories than others. The kind
Either I'm missing something crucial, or there's a fundamental inconsistency in
your use of terminology. Did you really mean to write two paragraphs that be
summarized as:
A use case can be this ...
A use case is different from what the previous paragraph says.
Which is it? A use case can't be different from a use case.
I have a similar difficulty with the paper cited above. The definition and
examples of stories don't seem consistent with each other, and aren't at all
consistent with the way I usually see user story defined elsewhere.
Gary
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
