search

tigerting98 / pe

0 stars 0 forks source link

'Find' cannot search through both warehouses and suppliers for products simultaneously #5

Open tigerting98 opened 3 years ago

tigerting98 commented 3 years ago

image.png

The find feature only allows for searching through warehouses and suppliers individually, which forces the user to perform two searches if for example they wanted to find all warehouses that stock 'panadol' and all suppliers who supply 'panadol' in order to compare these warehouses and suppliers. This can slow down productivity in some cases.

nus-pe-bot commented 3 years ago

Team's Response

Our team did consider this possibility as well.

However, due to time contraints, we could only implement the functionality to search for either relevant suppliers or relevant warehouses. We also considered the fact that some users may have already searched for relevant warehouses storing panadol and that they may want to search for relevant suppliers selling masks without changing the displayed warehouses list on the GUI. This was why we decided to prioritise finding separately instead of finding both suppliers and warehouses at once.

In addition, with the command history feature of the app, users are able to rerun the latest find command with minor modifications to the ct/ prefix and this enables them to find the relevant suppliers and relevant warehouses quickly with the same criteria. Since our target users are proficient with using the keyboard, the command history helps to migitate this issue.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: First of all, I do not believe a time constraint alone is grounds enough to reject this FeatureFlaw. An unfinished product will have flaws, and saying that this was due to a time constraint is tantamount to admitting that more could have been done. While the team's explanation regarding the use of the command history feature to mitigate this flaw is valid, the flaw is still present. The application could still be made more convenient to the user if the proposed feature had been implemented. Thus I belive that it is unreasonable for the team to outright reject this issue.