Use cases too lengthy and repetitive sentences (for incorrect format)

[JustWeiHao]

[nus-se-script]

Team's Response

None of the commands uses the exact same full set of error handling. Each commands requires a different subset of error handing. We are handling different types of error to give a better user experience.

For the developers, they have to be clear about what errors are being handled for each type of commands, thus, it value adds to explicitly state the subset of errors for each command. Without such explicit use case extensions, the developers may be confused about what command is to be handled for each type of command.

Hence, it is important for us to list out all the different cases.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement:

The above image is taken from the textbook when teaching about use cases. Notice that the textbook only mentioned "entered data".

I think that the use cases should not be too detailed (too many branches) for just invalid input because imagine a case in which both invalid phone format and email format exist in the input. The branching of your use cases only solves one of them and resumes from step 2 which does not address the other invalid format.

Besides, there is ambiguity about what "no errors with the input" means. If the "input" means the specific field, then the use cases are incorrect for more than one invalid format. If the "input" means the entire input, it is also incorrect because the loop is until the user correctly types the correct format for that specific field. It should not fix other incorrect formats (if any).

---