I think that you should use the extend properties of use case. I mean,
considerar a use case "Enter", there you validate all general things that a
user must full to enter at the parking. Then consider (using extend) the
diferents way that user migth allow it's entrance, throguh a "credit card,
ticket,.." finally you'll get something like
<----extends----- validat credit-card
enter <----extends------ validate ticket
<----extends------ others forms to enter.
hope it likes!!!
----- Original Message -----
From: "Michael Hill" <[EMAIL PROTECTED]>
To: "Yves Gagnon" <[EMAIL PROTECTED]>; "Rose Forum"
<[EMAIL PROTECTED]>
Sent: Thursday, March 29, 2001 9:31 AM
Subject: RE: (ROSE) Use Case versus generic system
> First of all, define all your actors to your system (Client,
> Administrator, Arming Loop, etc.).
>
> Then define all the responsibilities for each actor, those
> responsiblities are your Use Cases.
>
> * Enter Parking with Credit Card (Client Actor)
> * Enter Parking with Ticket (Client Actor)
> * Configures System for One Barrier (Administrator Actor)
> * Configures System for Two Barriers (Administrator Actor)
> * Recognizes Car Passage through the Barrier (Arming Loop)
> * etc.
>
> Now you have your system boundries defined. Then finish each Use Case
> with the details (Description, Pre & Post Conditions, Flows, Special
> Requirements).
>
> What I gave above is an example, I don't know much about the system
> being written but I think this might give you a good start.
>
> -----Original Message-----
> From: Yves Gagnon
> Sent: Thu 3/29/2001 8:47 AM
> To: Rose Forum
> Cc:
> Subject: (ROSE) Use Case versus generic system
>
>
>
>
> Hi all,
>
> We start a system for the parking area. The purpose of it his to
> manage the
> entry/exit of the client. The system could be connect to an
> barrier, an
> arming loop (a device that capture the passage of the car), en
> entry device
> (that have button for the ticket, credit card reader etc). My
> question is
> about the approach to define a use case like 'Client enter in
> the parking'
> for a system that could have different configuration. We want to
> let our
> customer be able to configure the entry like they want. That
> means they
> could decide to include a credit card reader or not, to have two
> barrier or
> one etc. I ask myself what approach to take to define my use
> case ? What
> could be me primary scenario ? Even with a configuration, the
> client that
> enter in the parking could take many path, like to use the
> credit card
> reader instead of the button to take a ticket.
>
> An help will be very appreciate
>
> Thank you
>
> Yves Gagnon
> [EMAIL PROTECTED]
>
>
>
> ************************************************************************
> * 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
*
*************************************************************************
