[155] in magellan
Use Cases
daemon@ATHENA.MIT.EDU (Tim McGovern)
Thu Apr 29 12:09:23 1999
Message-Id: <v03130306b34e34119ada@[18.152.1.21]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 29 Apr 1999 12:13:43 -0400
To: magellan@MIT.EDU
From: Tim McGovern <tjm@MIT.EDU>
Fellow Discovery Leaders:
A few weeks ago during our fortnightly magellan meeting, I mentioned a
course that I took on Use Case Analysis. Because this technique is not
widely used at MIT, I inappropriately suggested that Discovery leaders
might consider using this technique if they're involved in a project that
will produce a "system" of one form or another. I promised to summarize
the technique and post to the group, so that my suggestion could be
considered, debated and dealt with.
Better than any summary I could have written, I have found a terrific web
page that describes when/where/how you might consider using Use Cases:
http://www.zoo.co.uk/~z0001039/PracGuides/pg_use_cases.htm
You don't need to read the whole page (it is on the long side) if you don't
want to dig into all of the examples, etc. But I do want to mention one
point that the author makes:
Remember: Use Cases are about capturing HIGH-LEVEL, USER-CENTRIC
requirements for the purpose of scoping the project. Use Case
modelling should, must, be a short stage in the project's life cycle.
Forgetting this is the surest way to disastrous Use Case models.
I look forward to your thoughts on this topic...
Thanks,
Tim
