As a user, you get two things of value from login/logout behavior.
1) You get access.
2) You get security.
Making up one use case called something like "Control User Access" would
be a good idea.
The case for the use case is pretty good when you are using the builtin
login from the operating system, and even better when you are developing
all or part of it as part of your project. If it is part of the
development, the scope of Control User Access increases significantly,
because maintainance of the security system will require more behavior,
and probably, an additional actor.
This all looks pretty strong to me.
-Eric
Jie Zhao wrote:
>
> Hi,
>
> Should "Logon" and "Logout" be use cases? It seems all systems have these
> two special use cases.
>
> Jie
************************************************************************
* 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
*
*************************************************************************
