Hi, all RUP is a use case driven process, a use case describes the step-by-step communication between the user and the system, therefore no doubt the user interface design solution will be derived mainly from the flow of events of the use case specification (IMHO) . Should this relationship/traceability between use cases and user interfaces affect the decision making regarding whether login/logout should be independent use cases? For example, if login/logout are separate use cases the system has to provide UI to allow the actors to initiate the use cases, otherwise if they are included use cases that are used by other more obvious use cases the system will not probably have UI for login/logout. In other words if the customer requires to have login user interface to allow users to login first, then perform other tasks, should login be a separate use case? 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 * *************************************************************************
