Hi,
I am also reading and enjoying Alistair Cockburn (pronounced Coburn)
unpretentious book on use cases. He mentions that the typical ways use cases
are packaged include by Primary Actor, by Summary Use Case, by Development
Team and Release or by Subject Area. There is no best approach - it depends
on your circumstances.
For those who haven't read the book here's a nutshell summary. He uses
simple icons to classify the system scope and goal level for *every* use
case. For scope, the system under discussion may be the organization (shown
as a house), a software system (shown as a cube) or a component (shown as a
screw). Organizational use cases provide context for system use cases.
System use cases provide context for component use cases.
The goal level of the use case may be a very high summary (shown as a
cloud), summary level (a kite), user goal level (waves - the most important
level when designing the system), subfunction level (a fish) and "too low"
(a clam - no use case should be that far removed from a user goal). He also
distinguishes between black box and white box use cases. He gives an example
of how white box use cases can effectively communicate complex design
decisions.
Apart from these icons, the book does not spend much time discussing the
visual modeling aspects of use cases. In fact, I now find discussions about
includes, extends and generalization to be somehow missing the point. What
the point? Use cases are hyperlinked prose. If a use case is associated with
another you simply click on its name and there you go for further detail.
This is because the names of use cases are goals, and goals may naturally
contain subgoals.
Cheers,
-Richard
----- Original Message -----
From: "Yves Stalgies" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, January 03, 2001 1:01 AM
Subject: Re: (ROSE) is there any rule when seperating use cases in different
packages
>
> Hi daniel,
>
> i separate my use cases arcording to the new book from Alistair Cockburn
(awl). He structure the use cases in packages in dependency of the context
(or scope): enterprise, system, component use cases. Have a look into this I
book - it contains many useful hints how to structure use cases.
>
> regards
>
> yves
>
> >>> "daniel wang" <[EMAIL PROTECTED]> 01/03/01 06:32PM >>>
> hi:
> i have many use cases and of course i don't want all of them in
> the same use case diagram . so i should seperate them in different
> packages.How to define package , i mean, is there any rule when seperating
> use cases in different packages.
>
> thanks in advance
> best regards
>
> daniel
>
>
!
> !
> !
> !
>
> ************************************************************************
> * Rose Forum is a public venue for ideas and discussions.
> * For technical support, visit http://www.rational.com/support
> *
> * Admin.Subscription Requests: [EMAIL PROTECTED]
> * Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
> * Other Requests: [EMAIL PROTECTED]
> *
> * To unsubscribe from the list, please send email
> *
> * To: [EMAIL PROTECTED]
> * Subject:<BLANK>
> * Body: unsubscribe rose_forum
> *
> *************************************************************************
>
>
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
