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.
Description:
The sequence diagram on page 4 of the Developer Guide does not flow well and would confuse developers who are reading this for the first time.
As seen in the screenshot below, Parser -> Command, 4 Execute, I assume the Parser calls the execute method in Command, however, it shows that Command->Storage 5 Save Logs to File afterwards.
The next line is then Parser->Scanner for the input, and does not show if the Storage returns to Command, which then returns to the Parser.
Editing to add the second diagram below, under Log Package, which is very hard to follow.
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.
Description: The sequence diagram on page 4 of the Developer Guide does not flow well and would confuse developers who are reading this for the first time.
As seen in the screenshot below,
Parser -> Command, 4 Execute
, I assume theParser
calls the execute method inCommand
, however, it shows thatCommand->Storage 5 Save Logs to File
afterwards.The next line is then
Parser->Scanner
for the input, and does not show if theStorage
returns toCommand
, which then returns to theParser
.Editing to add the second diagram below, under
Log Package
, which is very hard to follow.Screenshot:
[original: nus-cs2113-AY2324S2/pe-interim#823] [original labels: severity.Medium type.DocumentationBug]