Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UML diagrams are not consistent #5

Open
hieunm1821 opened this issue Apr 16, 2022 · 1 comment
Open

UML diagrams are not consistent #5

hieunm1821 opened this issue Apr 16, 2022 · 1 comment

Comments

@hieunm1821
Copy link
Owner

hieunm1821 commented Apr 16, 2022

Two UML diagram both show how the command operation works with example but one does not include specific information from example inside the diagram.

Screenshot from 2022-04-16 15-27-58.png
Screenshot from 2022-04-16 15-30-16.png

@nus-se-script
Copy link

nus-se-script commented Apr 19, 2022

Team's Response

Unsure which sequence diagram for delete is the tester referencing. If Tester is referencing the first sequence diagram for delete (found in the logic component), the focus of the sequence diagram is to illustrate the interactions within the Logic component for the execute("delete class 2") API call.

The second sequence diagram for delete includes specific information from examples inside the diagram.

Screenshots

Sequence Diagram for logic component

image.png

Do refer to our Logic Component for more details.

Sequence Diagram for implementation of delete command

image.png

Do refer to our Delete Feature for more details.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

  • I disagree

Reason for disagreement: Both diagram are taken from the same section: Implementation
One from Add Feature and one from Delete Feature. So I think it is a mistake because it is not consistent.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants