SpecGL Scope definition: Complete set of Use Cases?

Regarding the definition of Use Cases in SpecGL (guideline #1)
  - My AI to deal with the @@@ on the "system (specification)" text:

  Having re-read this final sentence I wonder what the purpose of it
is?
  It says that a complete set of use cases specifies all the possible
uses of the system (specification).

  I have a couple of thoughts about this:
  1. It states the obvious, but in reverse order i.e. it's telling us
  that if one describes all possible uses of the system/spec. then one
has a complete set of use cases.

  2. Can a spec author/WG be expected to anticipate and describe
     every possible use of a system/spec?
     This is surely an exhaustive task and outside of the author's
scope anyway. It reminds me of the issue of conformance statements in
which there is a danger of trying to ring-fence the uses of the
spec in advance rather than leaving it to the creativity of the
developers

  So my first recommendation at a way to clean up this sentence is to
delete it!

  -Andrew

Received on Saturday, 2 November 2002 09:36:38 UTC