Open GWphua opened 2 years ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Missing steps in Use cases
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.
There are missing actions from the application after step 1. Adding something like "Trace2Gather gathers and displays all vacant rooms." would probably be better.The following screenshots show the other use cases where I feel there are missing steps. The recommended fixes to these are similar to the one above.
[original: nus-cs2103-AY2122S1/pe-interim#3066] [original labels: severity.VeryLow type.DocumentationBug]
[This is the team's response to the above 'original' bug]
We believe that our current MSS is sufficient to describe the externally visible behavior given that the User is able to view the retrieved information as our MSS describes the most straightforward interaction for a given use case. Nonetheless can see the value such a statement might add.
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
Team chose [response.NotInScope
]
Reason for disagreement: Team should be well aware of how to write Use Cases with all the CS2103T materials provided.
No mention of the app at all.