When to Omit Interactions from Sequence Diagrams

Explanation

Unless you are using sequence diagrams for code generation or detailed documentation, you do not have to include every interaction. When developing models early to support requirements engineering and high-level design, there will be many interactions that depend on implementation decisions. For example, how to get the user identifier to check authorization is an implementation detail that can be left out of an early-stage sequence diagram.