Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Missing MSS step for Use case for add a module

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 MSS is missing the crucial step of having the module list view first because otherwise it will be invalid.

_{[original: nus-cs2103-AY2122S1/pe-interim#2166] [original labels: severity.High type.DocumentationBug]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

The step of switching to the module list view is an implementation detail which should not be in the use case.

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: Based on the definition of duplicates of bugs given:

It is not the same bug as the "original bug" as the original bug is pertaining to the add use case whereas this is pertaining to delete use case
It is indeed similar bugs across the use cases but they can be fixed independently as the use cases are all separate and different cases on their own, which is also proven by the very fact that they are different use cases in the Developer Guide.
Not a diagram

Hence, even though the problems across all use cases reported seem similar, use cases are independent from each other and therefore should be considered bugs on their own respectively. And this independent nature invalidates the conclusion of this bug being a duplicate.

:question: Issue response

Team chose [response.Rejected]

[x] I disagree

Reason for disagreement: By referring to the response from the "original question", The step of switching to the module list view is an implementation detail which should not be in the use case.

Based on the definition of Use Case, it is A description of a set of sequences of actions, including variants, that a system performs to yield an observable result of value to an actor. Clearly without showing the details view before adding a lesson will result in definite failures of the execution of such commands. Furthermore, the missing detail is clearly an interaction detail between the system and users as the users have to specifically type in different list command in order to obtain the correct view, which has to be included in the use case. And it is definitely not just an implementation detail as the team claimed.

Also, the use cases are of great importance to the developers as they specify the requirements of the application and the missing details/steps may lead to false expectation and perception of the interactions between the system and users, which in turn lead to development hazards and system failures.

However, as developers may realise the missing specification from testing/other documents, it is more appropriate to rate the severity to be medium as it causes occasional inconvenience to the developers.

jackgugz / pe

Missing step in MSS for add a lesson #23