Reputation: 23
For instance, in a use case specification, one of the preconditions is that the user is logged in but in the main flow it also states that the user logs in.
Upvotes: 2
Views: 3058
Reputation: 1789
to complete, in the specification Message does not have pre-condition. But as @Salman explain, you can model a login sequence and use it as an interactionUse.
Here are some schemas: a class diagram to define a LoginManager, a diagram sequence with two gates which defines how credentials are checked, a diagram which uses the previous one. Diagrams done with EA.
Upvotes: 0
Reputation: 11649
All diagrams can show different levels of abstraction. If you want to focus on more important business stuff, then you have to be more abstract, and forget about trivial stuff such as log in. You can draw a very detailed sequence diagram, or an abstract sequence which explain 5 or 6 actions.It would be up to you, and your goal.
But, if the authentication is an important part of sequence, it is better to keep it. For instance, let's say, you want to draw the sequence diagram for money withdraw, then having the authentication is an important part of the whole process, unless you want to focus on other aspects.
Upvotes: 2