Sqat - Revenue Tier Project

REVENUE TIER PROJECT

1. Missing or ambiguous requirements:

• What revenue tiers will the customer fall into if their invoice is negative (that is, they overpaid their last invoice and thus the company owes the customer)?

• How are items between tiers handled? Eg. Does an invoice amount of $1567.50 fall under Tier 1 or Tier 2.

• #5 Business Rule. If data models are flexible, does that mean that the dollar range for each group is also flexible? Because if you can add as many groups as you want, that can lead to misuse of the tiers. Same argument can be used for #6 Business Rule because adding/deleting services between areas allows for manipulation of the tiers.

• Also, there is no dollar amount associated to an individual service as we only know the dollar amount for the groups.

• #4 Business Rule. If the Total Invoice includes all services and may include more items that just the services listed, then what are those other services? Are these other individual services and, if yes, what are they and how many are allowed per customer?

• What happens if there are promotions/specials? Is Revenue Tier determined by the promotional price or the regular price of the service?

• The purpose of the revenue tier module was not defined at all. It would be helpful for testers and programmers if there was a little write-up as to what this module is intended to do.

1. Incorrect business requirements with respect to “writing testable requirements”

• #2 Business Rule. That rule implies that if invoice is $0 then it falls in Revenue Tier #1. So if accounts are disabled or on hold, they will all default to Tier #1. That is incorrect because it will add all the accounts with credits or accounts that are disabled/on hold to Tier #1 and it will distort the accounts for reporting purposes.

• The Total Invoice group is linked to only one service titled “All”. We do not know...