[DG] Too much information in one sequence diagram

[raihahahan]

Overview

• Sequence diagrams are encouraged to be kept smaller with not too much information.
• The Sequence Diagram for your Export feature has too much information, resulting it to be too zoomed out.

Screenshot below (page 11 of DG)

Suggestions

• If there is too much information to cover, you may use Reference Diagrams to separate the Sequence Diagram into multiple Sequence diagrams.
• This is because UML uses ref frame to allow a segment of the interaction to be omitted and shown as a separate sequence diagram.
• Below are some diagram examples provided by the course textbook:

Notation for ref frames

Example:

Additional Notes

• As the Sequence Diagram is still correct, and it may still look normal on bigger screens, the severity will be set to Low.

[nus-se-script]

Team's Response

The sequence diagram is readable and understandable to people with knowledge of UML diagrams.

It is not too much information as you are still able to view all the details clearly without overlapping arrows or components.

At most, it is a cosmetic issue. Hence, the response will be severity.VeryLow.

Therefore, we will classify this bug response as Rejected.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---