Hi Everyone,
I know this question came on the forum many times,
still it troubles me to decide Login and Logout either
as independent use cases or just pre and post conditions
of other usecases which actually carry out the functionality
of the system or solve the purpose of the User.
In one of the earlier questions I knew Login was taken as
a use case and then was considered as Pre-condition of
other use cases. But I am not able to get convenienced
that "Login" can be a usecase itself , since it indepenently
does not return some thing useful to the Actor. The actor
is going to access the required useful information only
after Login.
For example I have a usecase "View race Information"
which is initiated by the actor known as "Member" .
To view this information the the member must have already
logged in. But I don't want to make Login as a separate use case,
because it does not return any thing to the actor as such.
Now the problem is if Login is not a use case then what it is?
Where I can have it? If I can have it as a pre-condition then
I am worried where the flow of events which take place during
Login can be accomodated.
Any suggestion most welcome.
Thanks
Maheswari
************************************************************************
* 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
*
*************************************************************************
