From: Andrew Gabb (agabb@tpgi.com.au)
Date: Tue Aug 26 2003 - 10:04:28 EST
Philippe THUILLIER wrote:
> Depending on the system considered, i sometimes use a "misuse case" approach
> to elicite and describe non-functional requirements. This approach (based on
> negative "What-if" scenarios) was first proposed by Ian Alexander (see related
> papers on http://www.scenarioplus.org.uk/) to support security requirements
> analysis and can be generalized to others non-functional aspects.
A caution here. Having used scenarios to address military security and safety requirements, such 'misuse cases' are significantly different in their representation and usefulness from genuine use cases. I'm talking mainly of user use cases here (eg pre-design).
Real use cases can quite effectively express the use of a system, often comprehensively (but rarely exhaustively).
Misuse cases are *examples* of some things that might happen. As such, they are usually far from comprehensive, and need much more supporting and coordinating text to express the overall concerns (needs). Used as a basis for design, they will usually be inadequate.
I'm not saying don't use them, just realise that you're only getting part of the story.
Andrew
-- Andrew Gabb email: agabb@tpgi.com.au Adelaide, South Australia phone: +61 8 8342-1021, fax: +61 8 8269-3280 ----- ------------------------------------------------------------------------------- To send a message to this mailing list send it to re-online@it.uts.edu.au. To unsubscribe from this mailing list, email majordomo@it.uts.edu.au with the message `unsubscribe re-online' in the BODY of the mail.
This archive was generated by hypermail 2.1.6 : Mon Sep 01 2003 - 09:00:12 EST