SeanChinJunKai / pe

0 stars 0 forks source link

Mismatched components of User stories #9

Open SeanChinJunKai opened 1 year ago

SeanChinJunKai commented 1 year ago

Screenshot 2023-04-14 at 3.36.35 PM.png

For the add and delete user stories, the three parts do not match, for both add and delete the so that part should be so that i can add new military personnel to the system who have just enlisted quickly and remove military personnel who recently ORDed quickly respectively

nus-se-script commented 1 year ago

Team's Response

Hi Tester!

For the add user story, maybe you were looking for something more specific like "...so that I can add new military personnel to the system who have just enlisted quickly", rather than something generic like what we had.

However, consider the following scenario -- our recruit Jacob has just finished his Basic Military Training (BMT) and is posted to Specialist Cadet School (SCS). Supposing that BMT does not use AIMS but SCS does, the admin clerk in SCS will have to add Jacob to AIMS. Thus, it is slightly incorrect to say "I can add new military personnel to the system who have just enlisted quickly" as Jacob would have enlisted sometime ago already.

Likewise, for the delete user story, putting "remove military personnel who recently ORDed quickly" in the "so that" column may be slightly incorrect as the admin clerk may still keep the personal information of ORD-ed personnel to facilitate calling them up for reservist.

Hence, we did not put specific details for the add and delete commands in the "so that" column

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: I think what I was trying to highlight was not a specific scenario but rather the idea of using the add or delete command which is to maybe record a new personnel into the system for instance. Also, in the given user stories, there are two functions which is to type in a command and delete/add which makes it confusing.