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.
It is difficult to read all the various commands, as well as the different functions that are being carried out in this one Sequence diagram. Perhaps using refs to break down this sequence diagram would be more useful to developers.
Some sequence diagrams are also overly long, being nearly one page long. Perhaps it would be better to split them into separate diagrams for better readability.
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.
It is difficult to read all the various commands, as well as the different functions that are being carried out in this one Sequence diagram. Perhaps using
refs
to break down this sequence diagram would be more useful to developers.Some sequence diagrams are also overly long, being nearly one page long. Perhaps it would be better to split them into separate diagrams for better readability.
[original: nus-cs2113-AY2324S2/pe-interim#194] [original labels: severity.Low type.DocumentationBug]