I think it depends on the system, and if a use case "Login" is essential,
you should design it.
However, for all those who on principle say no to the need for use cases
"Login" or "Logout", it's interesting that Rational teaches the use of a
"Login" use case in their training courses material (the "Course
Registration System")...
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 02, 2001 4:10 PM
> To: Styve, Arne
> Cc: Jie Zhao; '[EMAIL PROTECTED]'
> Subject: RE: (ROSE) Logon and Logout Use Case
>
>
>
>
>
> There is a school of thought that says these two items
> should NOT be use cases.
>
> Use cases should make a case for using the system. I
> typically don't use a
> system to login or logout, I want to get something of value
> from the system.
> Many times, login is shown as a precondition to the other
> use-cases. Granted,
> you'll need to acknowledge these in some way, but I don't
> know if you would want
> to have them as their own use-cases.
>
> Just my two cents worth, but I know there are a lot of
> disagreements over this
> issue.
>
> -GLH
************************************************************************
* 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
*
*************************************************************************
