search

Joven-Heng / pe

0 stars 0 forks source link

Use of extensions as preconditions #9

Open Joven-Heng opened 3 years ago

Joven-Heng commented 3 years ago

image.png

For UC02, perhaps change it to a precondition? It is not really an extension. This also applies for UC05, 06, 09, 10,11,13.

nus-se-bot commented 3 years ago

Team's Response

The user can still use the command even if he is in the wishlist, hence we considered it as an extension.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: From the textbook: Extensions are "add-on"s to the MSS that describe exceptional/alternative flow of events. They describe variations of the scenario that can happen if certain things are not as expected by the MSS. Extensions appear below the MSS.

Preconditions specify the specific state you expect the system to be in before the use case starts.

I am not sure whether preconditions should be written as extensions, but this really feels like a precondition to me. It does not mean that as long as the command exists in that state = it should be considered as an extension. I believe if that is the case, if there would be multiple preconditions in the future, there would be just too many extensions. Furthermore, as there were no preconditions even written through the use cases makes me feel that the team did not consider using preconditions at all.