To explain it a bit further, Explaining 'How' the customer will insert the
card is a 'How' "external" to the system.So it is not a problem.
If you had explained a 'How" internal to the system for example how the card
reader works then it is wrong

Hope this helps
Prabhu
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, December 22, 2000 2:07 AM
> To:   [EMAIL PROTECTED]
> Subject:      (ROSE) ATM Use Case Model
> 
> 
> I have been giving a two hour presentation to introduce RUP to our project
> teams. The presentation contains the ATM use-case model that is used in
> most of the Rational training. I have been stressing that use cases
> describe "what" and not "how". At the last presentation, a lively
> discussion about having the bank customer insert his/her ATM card
> constituted "how" and not "what". Has anyone encountered this situation
> and
> what was the consensus?
> 
> ************************************************************************
> * 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
*
*************************************************************************

Reply via email to