Re: use case definition -- follow-up

I have a problem with the plain, ordinary meaning of "case" in
contrast to "use case" being defined as:
...captures all the different ways a specification would be used...

I think we want to encourage publication of a set of use cases that
is sufficient to justify the existence of a new standard and all the
work that goes into creating its specification. If there are more use
cases beyond the published ones, that's fine, but I don't think that
the QA or W3C needs are served by suggesting that *all* uses need to
be enumerated.

I prefer:
a specification mechanism or technique that conveys the range of
different ways a specification would be used...

Notice that my preferred verbiage grants some value to the attempt to
convey "all the ways" but allows the sufficiency standard to prevail.
.................David Marston

Received on Friday, 16 August 2002 01:10:44 UTC