alexwxh / pe

0 stars 0 forks source link

Viewing list of borrowers #1

Open alexwxh opened 4 years ago

alexwxh commented 4 years ago

There is no way of conveniently viewing the list of borrowers. It forces us to view the borrowerrecords.json file to find the full list of available borrowers.

nus-pe-bot commented 4 years ago

Team's Response

Thanks for testing our app.

This is not a bug nor a bug report. We did not state that we have a feature to see all the borrowers in the system. None of our application's features have become less useful to the intended target user due to the lack of this feature.

Nevertheless, thank you for your feature suggestion, however, it is clearly stated in the CS2103T instructions for PE not to post suggestions for v1.4. While you might opine that this a good feature to have, we did not include this feature in our v1.4 as it is not very useful to our target user of small town community librarians. There is no practical need for our target users to scroll through a long list of borrowers. When a borrower comes to the librarian to be served, he/she produces his library card/identification card/etc to the librarian which has his/her borrower ID. It is therefore not feasible for the librarian to browse through the list of borrowers to find that borrower standing in front of him/her.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: so you are going to implement a borrower feature with no way of accessing, viewing or editing it in your application? if we were to put it in the real life scnario that you have repeatedly stated, you are trying to say that there is no possible scenario that a librarian would ever need to check/edit a borrower's information. how about the borrower changing his phone number/email address? or the borrower losing his card? the program doesn't allow registering of 2 borrowers with the same phone/email. you can directly edit the .json storage file but your target audience are small town community librarians, not IT-related personnel.


:question: Issue severity

Team chose [severity.Medium]. Originally [severity.Low].

Reason for disagreement: