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.
The sequence diagram explaining how the timetable is printed out in pages 19-20 of the DG spans a page break, and its length can hinder readability. Consider splitting it up into parts, and maybe omitting parameters from the method calls shown?
Overly long diagram may hinder readability, but the diagram itself should still be a singular diagram without being divided in two to retain the logic it is conveying.
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.
The sequence diagram explaining how the timetable is printed out in pages 19-20 of the DG spans a page break, and its length can hinder readability. Consider splitting it up into parts, and maybe omitting parameters from the method calls shown?
[original: nus-cs2113-AY2122S2/pe-interim#1239] [original labels: severity.Low type.DocumentationBug]