Have you considered that the "Maintain employee" use
case is abstract?
If this is true then the Add, Delete, ... could either
be identified AS
1.) Use Case Realizations from the abstract use case.
OR
2.) Multiple activity diagrams attached directly to
the abstract use case.
Both seem to work well for business analysis however
the use of realizations provides a good path from
analysis to design.
--- Romuald Restout <[EMAIL PROTECTED]> wrote:
> Seems to me that in the "Maintain employee" use-case
> you cannot define a
> basic flow, but severals !
> So I would say : several use-cases !
>
> -----Original Message-----
> From: Ng, Pan Wei [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 30, 2000 10:00 AM
> To: Michael Hill; Ng, Pan Wei
> Cc: '[EMAIL PROTECTED] '
> Subject: RE: (ROSE) Use Cases and UC Diagram
>
>
>
> Of course the observable result is different! Your
> basic flow and alternate
> flow will give you different observable results!
> Should you split them into
> different use case? Definitely Not. The What are
> flows and what are use
> cases depends on the value it brings to the actor.
> The "complete sequences
> of events" that are "of value to the actor". Focus
> on the larger picture on
> what the actor wants.
>
> -----Original Message-----
> From: Michael Hill [mailto:[EMAIL PROTECTED]]
> Sent: 30 November 2000 20:45
> To: 'Ng, Pan Wei '; Michael Hill
> Cc: '[EMAIL PROTECTED] '
> Subject: RE: (ROSE) Use Cases and UC Diagram
>
>
> But the observable result would be different for
> "Update", "Add", etc. If
> the result is different, then you have broken the
> definition of a Use Case.
>
> -----Original Message-----
> From: Ng, Pan Wei
> To: Michael Hill
> Cc: [EMAIL PROTECTED]
> Sent: 11/30/00 6:46 AM
> Subject: RE: (ROSE) Use Cases and UC Diagram
>
> Hi,
>
> The definition of a use case is A SEQUENCE OF EVENTS
> PERFORMED BY THE
> SYSTEM
> THAT YIELDS AND OVSERVABLE RESULT WHICH IS OF VALUE
> TO THE ACTOR. Focus
> on
> the phrase "of value to the actor". Is adding
> records by itself of value
> to
> the actor? Think of a system in context. If it can
> only add records, but
> cannot browse, delete, edit. Is it of value to the
> actor. If it is, I
> agree
> with you. BUT IN MOST cases, what the actor wants is
> to be able to
> mantain
> records, Add, Delete, Update, Browse and Search, and
> use case like this
> in
> most cases are NOT BIG.
>
> Cheers
> --Pan-Wei Ng
> Rational Software (Singapore)
>
> -----Original Message-----
> From: Michael Hill [mailto:[EMAIL PROTECTED]]
> Sent: 30 November 2000 20:33
> To: 'Ng, Pan Wei '
> Subject: RE: (ROSE) Use Cases and UC Diagram
>
>
> I disagree with what was stated below, Update
> Records, etc. are not
> flows
> in the Use Case. Think about you alternalte flows
> or exceptional flows,
> it
> would cause the Use Case to be to big. Split them
> up in smaller Use
> Cases.
>
> -----Original Message-----
> From: Ng, Pan Wei
> To: CHIAM CHOON YEE, LSD; '[EMAIL PROTECTED] '
> Sent: 11/29/00 9:28 AM
> Subject: RE: (ROSE) Use Cases and UC Diagram
>
>
> 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]
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
************************************************************************
* 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
*
*************************************************************************
