search

OVReader / pe

0 stars 0 forks source link

Age capped at 100 #5

Open OVReader opened 1 year ago

OVReader commented 1 year ago

Age is capped at 100 years old. Although rare, there are people who are older than 100 years old and such cases are not handled

image.png

soc-se-bot commented 1 year ago

Team's Response

Thanks for raising your issue!

Our target customers for this businesses are students in university as mentioned in DG, so I think 100 should be more than enough for upper limit.

image.png

The oldest person we could find graduated university at the age of 99.

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: To begin, this bug is reported during PE Phase 1 - Part I where testers focus lies on UG and manual testing section of DG as mentioned in module website as shown below.

image.png

Hence, target user profile was ignored. Instead "target users" are interpreted as "rental business managers who keep track of all of their customers" as stated in the introduction of UG as shown in picture below.

image.png

Since the transaction required "borrowerName" (interpreted as customer's name), this implies that when adding "user" (interpreted as customer), the person's age must be provided as shown in the picture below.

image.png

With this in mind, there are three reasons why age capped at 100 should be treated as a feature flaw (Low severity):

(1) "user" which can be interpreted as customers are no longer bounded by the reasoning provided by dev team.

(2) This is no guarantee that someone over 100 years old and is university student will not appear in the future.

(3) It is not a good practice to set such narrow margin/allowance for such parameters since cases like (1) and (2) can happened. Conversely, allowing a greater allowance will ensure smoother operations since unique cases are already factored.