I think that pre-conditions and post-conditions are significant events that must occur before and after a use case instance. Since every actor with the exception of the time actor must log in to do anything of importance with the system, stating that the actor must be logged in is the same as saying that the system must be plugged in. Repeating the condition that the actor must be logged in wastes trees and toner and adds little to the documentation of the system. Logging in is a pre-condition that every novice use case specifier lists because it is obvious. Gary Hockman >>> "Logan Wilkins" <[EMAIL PROTECTED]> 03/13/01 02:39PM >>> Maheswari: My $.02 are that Login is a valid precondition. I use all sorts of preconditions to get to the stage of the system where I want to begin my use case. For example: Preconditions: - User has logged in - User has clicked on Main Order Form - User has entered at least one valid hardware part number Why not use them? They are unambiguous (or should be) and make it very easy to get to the action that I want to describe. I advise against making writing use cases harder than it needs to be. Keep it simple. Also, IMHO Login is a valid use case. The value it provides is that the user gains access to a restricted system. Logan Wilkins Ciso Systems > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Maheswari Subburaman > Sent: Tuesday, March 13, 2001 2:10 PM > To: [EMAIL PROTECTED] > Subject: (ROSE) Whether Login and Logout are usecase or pre-condition > and post-condition? > > > > 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 * ************************************************************************* ************************************************************************ * 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 * *************************************************************************
