Contents
Should log in be a use case?
At the requirement eliciting, logging in is not a use case, but at the system design level it might appear as a use case . If security is a concern, it must appear and be treated as a special use case.
When should use cases be used?
Use cases add value because they help explain how the system should behave and in the process, they also help brainstorm what could go wrong. They provide a list of goals and this list can be used to establish the cost and complexity of the system.
What is an Actor in a use case?
An actor in use case modeling specifies a role played by a user or any other system that interacts with the subject. An Actor models a type of role played by an entity that interacts with the subject (e.g., by exchanging signals and data), but which is external to the subject.
When to use login as a use case?
Mostly not. In the rare case you are performing the use case analysis of some authentication or user management software, such as an SSO solution, in which the business value for the user is really to get logged into some protected systems, login is a use case.
When to use use case notation for login?
If the login is part of the system you are creating it should be a use case in itself that is listed as a prerequisite for other use cases. if you are using an outside system (i.e. Windows authentication) you could simply list that the user has authenticated through windows authentication or whatever system you plan to use.
What are the use case requirements of UML?
According to UML, every use case must yield an observable result that is of value for actors or other stakeholders. A use case like “Log in” does not satisfy this requirement, in my view.
Which is the best definition of a use case?
Use cases describe the pattern of how an actor interacts with a software to complete some goals.