DG: Add booking use case lacks important use case

[samuelim01]

Given that this is a hotel booking, an important use case that is missing is the case where the details are valid but the booking date has no more rooms, or the room is not available at the given time. This is slightly different from the booking details being invalid themselves. Perhaps this could be clarified, or split into two separate use cases, as it is currently unclear.

[soc-se-bot]

Team's Response

Issue not in scope of v1.4

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: It is not clear to me why this issue is not in scope of v1.4. From what I understand, the team means that this use case was not related to the features delivered in v1.4. I believe this is untrue, since the program does handle cases where the user details are valid, but the room is currently full. As shown below, the use case for adding a booking (erroneously named delete a person) lacks an extension for rooms that are not available at the given time.

Screenshot below shows the application support for detecting and rejecting rooms that are already full:

---