nus-se-script
commented
1 year ago Team's Response
As our target audience is SMEs, it is unlikely that projects have such a high budget. We may agree that inserting commas could make the budget clearer but this is more like a suggestion rather than a bug. Our functionalities and features still work as specified in the user guide and we cannot consider this as a bug, hence we decided to reject this issue.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Users input the budget so it can be easily found and read. However, in this case, it is hard to read and the user will have a hard time counting the number of zeros, therefore it doesn't fit well with your product. Yes, you may argue that the case is unlikely to happen to SMEs but surely there will be SMEs large enough to take on a 1 million or 10 million dollar project. There are like a lot of SMEs especially in the construction industry that has this kind of large project budget. Its too hard to read and doesn't fit well for the product, hence it was deemed as a feature flaw.
:question: Issue type
Team chose [type.FunctionalityBug]
Originally [type.FeatureFlaw]
- [x] I disagree
Reason for disagreement:
It is a feature flaw as it does not fit well with the product. Moreover, it doesn't solve the intended issue for the users. Users input budget so it can be easily found and read. However, in this case, it is hard to read and user will have a hard time counting the number of zeros, therefore it doesn't fit well with your product.
Too many digits in budget and it may be hard for user to read or understand as it is not separated with comma or anything. Another more realistic approach might be to change 1000000 to 1 MIL in the budget field instead