I have never been too sure about these. They appear in many text books
on use cases but I would definitely concentrate on the use cases that
specify the essential functionality of the system before considering the
use cases related to security.
If you have security requirements on your system there may be a whole
group of use cases related to this. After all, the use cases related to
administering the security of the system will need to be defined too
(add user, remove user, modify user), and if you have this type of
logon/logoff session management then which actor is responsible for
adding and removing the various types of users to/from the system?
Look at the security requirements for the system to decide how
significant security is at this stage. As in the elevator example, in
some cases security is definitely not required, but in the ATM example,
validation of the user will be a significant requirement. No doubt there
are examples between these, and more extreme than the ATM.
So I guess I am just saying that ... it depends (on the requirements)!
Again, just an opinion, but it may help!
David Bainbridge
[EMAIL PROTECTED] wrote:
>
> 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
>
> "Styve, Arne" <[EMAIL PROTECTED]> on 07/02/2001 06:15:02 AM
>
> Please respond to "Styve, Arne" <[EMAIL PROTECTED]>
>
> To: Jie Zhao <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'"
> <[EMAIL PROTECTED]>
> cc: (bcc: Gary Hayes/Jeppesen/TMC)
>
> Subject: RE: (ROSE) Logon and Logout Use Case
>
> I think I would have operated on a slightly higher level when defining
> Use-Cases. I think I would have had a Use-Case called "User Access" or
> something similar, and then used an activity-diagram to describe the
> activities involved in conjunction to the user accessing the system, where
> two of the possible activities would be "User Logon" and "User Logout".
> Supplied with a couple of sequence diagrams showing the sequence of
> operations involved between the user and the system (as a black box), this
> Use-Case would be quite good.
>
> I have seen examples of this type of Use-Case, but I cannot remember exactly
> where, at the moment. Sorry.
>
> Hope this was of help :-)
>
> Regards
>
> Arne Styve
>
> > -----Original Message-----
> > From: Jie Zhao [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, July 02, 2001 11:09 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: (ROSE) Logon and Logout Use Case
> >
> >
> >
> > 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
> > *
> > **************************************************************
> > ***********
> >
> This email, its content and any attachments is PRIVATE AND CONFIDENTIAL to
> TANDBERG Television. If received in error please notify the sender and
> destroy the original message and attachments.
> ************************************************************************
> * 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
> *
> *************************************************************************
************************************************************************
* 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
*
*************************************************************************
