nus-se-script
commented
1 year ago Team's Response
CAUSE:
This is a mistake made when AUTOM8 Development Team was learning how to use Plant UML for the first time (which was not formally taught).
Development Team initially dismissed this as PUML limitations. But upon further inspection of this issue based lack of familiarity to Plant UML.
This is caused due to lack of PUML training and the team apologizes.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Class diagram for logic component is unclear regarding the Logic interface
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 class diagram used to describe the Logic component is unclear. Namely, the interface Logic is not implemented by LogicManager, or any other classes. Neither is it a dependancy of any other class.
[original: nus-cs2103-AY2223S2/pe-interim#15] [original labels: severity.Low type.DocumentationBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
CAUSE:
This is a mistake made when AUTOM8 Development Team was learning how to use Plant UML for the first time (which was not formally taught).
Development Team initially dismissed this as PUML limitations. But upon further inspection of this issue based on this report, the team realized that Plant UML implicitly sets Package names as a label which caused this error to occur.
This is caused due to lack of PUML training and the team apologizes.
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)
- [x] I disagree
Reason for disagreement: This might be a duplicated issue you face, but not the duplicated issue i reported.
The arrow outside the model is confusing , does not add much infomation to the diagram.