DG diagram page 8

[trpmy]

This diagram is spliced in two due to a broken import of the meatball menu header, causing difficulty in comprehending the diagram. If this was cosmetic only, it deserves VeryLow. However, because it splices the diagram in two itself, it affects comprehension, so I put it at Low.

Worse yet, especially because the (dis)continuity of the activation bars is the very essence of sequence diagrams, this splicing introduces not just visual confusion, but even confusion in the meaning and content of the diagram itself. As such, I elevated it to Medium to reflect the particularly egregious oversight for this particular diagram.

[nus-pe-bot]

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

DG: formatting issues

the following image has formatting issues with the UML diagram (unnecessary zoom in ):

---

_{[original: nus-cs2103-AY2425S1/pe-interim#2098] [original labels: type.DocumentationBug severity.VeryLow]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

We accept this as we did not check on our part for the DG.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue severity

Team chose [severity.VeryLow]
Originally [severity.Medium]

• I disagree

Reason for disagreement: As in my original report:

This diagram is spliced in two due to a broken import of the meatball menu header, causing difficulty in comprehending the diagram. If this was cosmetic only, it deserves VeryLow. However, because it splices the diagram in two itself, it affects comprehension, so I put it at Low.

Worse yet, especially because the (dis)continuity of the activation bars is the very essence of sequence diagrams, this splicing introduces not just visual confusion, but even confusion in the meaning and content of the diagram itself. As such, I elevated it to Medium to reflect the particularly egregious oversight for this particular diagram.

I do not believe this is "purely cosmetic", as explained. The Team has offered no explanation as to why the semantic confusion from the broken bars and the difficulty of comprehension should be disregarded entirely in their comments.

I maintain the position that this warrants a Medium. Had the splicing error happened to other diagrams (i.e NOT sequence diagrams), I believe that would've been a Low.

Consulting the course page:

And I believe that this particular diagram type is extra vulnerable to and affected by splicing, as I've maintained. It's impossible (or at least, extremely difficult) for a user to definitively determine what bars are connected, what bars are not, and to make the connections in their head themselves. The team, in this matter, has offered no rebuttal on this point.

---