search

triciiaaa / pe

0 stars 0 forks source link

UML diagram stretches across multiple pages in DG #13

Open triciiaaa opened 4 months ago

triciiaaa commented 4 months ago

Description

UML diagram stretches across multiple pages, which may potentially hinder the user as they look at the diagram to understand the flow.

Screenshots

image.png

nus-se-script commented 4 months ago

Team's Response

Refer to #5056, same UML diagram.

The 'Original' Bug

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

Can have this diagram in a page

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

Would look nicer if in one page

Current state:

Screenshot 2024-04-19 at 5.35.51 PM.png

[original: nus-cs2103-AY2324S2/pe-interim#4656] [original labels: type.DocumentationBug severity.VeryLow]

Their Response to the 'Original' Bug

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

Hi thanks for the report. While it is unfortunate that the image has been broken apart, it is specified on the CS2103t website that 'page breaks need not be optimised' so long as they do not hinder the reader. Given that the diagram is still readable and no information is lost, we believe that it meets the requirement image.png

Items for the Tester to Verify

:question: Issue duplicate status

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

Reason for disagreement: [replace this with your explanation]

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** Thanks for the response! While I agree with the team's response that the bug is mainly a cosmetic issue, but according to the CS2103T website, a disagreement with the bug severity given by the tester is not a valid reason to reject the bug. Hence, I believe this should be response.Accepted alongside your team's decision for the bug severity label. ![image.png](https://raw.githubusercontent.com/triciiaaa/pe/main/files/3db53944-32cf-4229-8687-3dd7bb921552.png)
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]