I agree with Jeff. Use cases should be organized hierarchically. Just
because we use a hierarchical approach to organize them does not imply that
we are doing functional decomposition. In Rose, you can use the note as
link to another diagram approach to relate the hierarchy.
J.D. Baker
BAE SYSTEMS, Methods and Tools
My ideas, my words - they can not be attributed to or
held against any organization that I might work for.
-----Original Message-----
From: Jeff James [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 12:24 PM
To: Ng, Pan Wei
Cc: CHIAM CHOON YEE, LSD; '[EMAIL PROTECTED] '
Subject: Re: (ROSE) Use Cases and UC Diagram
We use Shlaer Mellor OOA to break down a complex system into domains
(subject matters).
Each of these subject matters is analysed as a system in its own
right....each with their
own set of use cases. The application level use cases would be huge and
useless and
unmanageable without breaking the system down into lower level use cases.
And even within
these domains, if the system is compex enough or if the use cases have
similar functionality
that can be broken into lower level use cases then do it (I'm not talking
about breaking it
down anywhere near function level though). It makes the development easier.
Call it
"functional decomposition" if you want ....... what's wrong with it? If you
look at Alistair
Cockburn' s use case papers he certainly describes various levels of use
cases (summary,
user goals and tasks). If it helps to solve a complex problem then use it.
Cheers,
Jeff
"Ng, Pan Wei" wrote:
> Hi,
>
> Your suggested approach is what we call "functional decomposition". This
is
> actually one of the pitfalls of mis-applying use cases. Your update
records,
> delete records, add records and view records are flows of events within
the
> Maintain Employee Records use case. Each of them is documented as an
> interaction diagram, not a use case.
>
> What you can do is as follows: Right Click use case. Select New-->Create
> Sequence Diagram, and rename them as update records, delete records, add
> records and view records respectively.
>
> Cheers
> --Pan-Wei Ng
> Rational Software (Singapore)
>
> -----Original Message-----
> From: CHIAM CHOON YEE, LSD [mailto:[EMAIL PROTECTED]]
> Sent: 29 November 2000 21:59
> To: '[EMAIL PROTECTED] '
> Subject: (ROSE) Use Cases and UC Diagram
>
> From what I understand, Use Case Diagram captures all the use cases which
> describes the functionalities of the system in relation to the system.
> Usually, I would want to keep the main use case diagram uncluttered,
simple
> and neat. However, when I do that, I lose the details.
> As an example, I use "Maintain employee records" as a use case. In this
use
> case, I actually have
> * update records
> * delete records
> * add records
> * view records
>
> Is there any good way to layer the use cases conveniently? That is, I
click
> into one particular use case, if there is a layer of use case diagram
below
> it, the diagram will be blown up?
>
> Thanks.
>
> This communication contains confidential or privileged information. If you
> are not the intended recipient, please notify us IMMEDIATELY that you have
> received it and destroy it. We are not liable for any unauthorised
sending
> of or interference with this communication.
>
> ************************************************************************
> * 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
> *
> *************************************************************************
--
<X><<>><X><<>><X><<>><X><<>><X><<>><X>
Jeffrey James, Sr Design Engineer
Tait Electronics Ltd.
Christchurch, New Zealand
<X><<>><X><<>><X><<>><X><<>><X><<>><X>
************************************************************************
* 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
*
*************************************************************************
