search

Jargonx / pe

0 stars 0 forks source link

Odd choice of prefix #9

Open Jargonx opened 4 years ago

Jargonx commented 4 years ago

The issue describes a feature flaw with a odd choice of property prefix and bidder prefix, b/ and c/ respectively.

image.png

nus-se-bot commented 4 years ago

Team's Response

For the severity level, it should be low as the different choice of prefix does not affect the user in using the application as it it is a cosmetic change and it does not inconvienience the user when typing. The reason for using unique prefixes for bids is to differentiate the input parameters from bidder which are very similar in name by using subtle differences (intentional) to prevent confusion. While it may give increased difficulty in using (more notations to remember) it helps to differentiate clearly between commands better.

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: image.png

Here the prefixes for PROPERTY_ID and BIDDER_ID are b/ and c/ respectively.

image.png

Here the prefixes for PROPERTY_ID and BIDDER_ID are p/ and b/ respectively.

This is extremely confusing to a user as one would expect that the prefixes are the same for the same parameters that they need to enter.

:question: Issue severity

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

Reason for disagreement: image.png

image.png

Under your target user profile, you have stated that your user is meant to be handling significant number of bids and since the target audience is real estate agents, it is assumed that they will be using your meetings feature to organise their meetings.

Severity Low suggests that the FeatureFlaw (the inconsistent prefixes) are encountered rarely but this is not true based off of the assumptions of the target user profile.

I assigned it Severity Medium based off of the assumptions of the target user profile who are likely to handle large volumes of both these entities and likely to be confused by the inconsistent prefix naming. This will result in the users constantly needing to refer to the User Guide, which is inconvenient and not User friendly for your feature and shows that these two features do not integrate well with each other.