A company has a rules based pricing system that allows for different pricing strategies to be used based on different types of corporate policies:
* Lowest national price on all products for government customers.
* Price based on contract at highest hierarchical relationship.
* Lowest price for a particular category of products.
Customers are grouped by types such as government, preferred, or new. Hierarchy means a customer can have a contract with a vendor at levels such as global, regional or direct. Categories are properties of the product being priced such as safety, health, or clothing of which products may have more than one. The rules are organized into packages for each of the categories mentioned in this paragraph but are executed in different sequences based on the strategy that applies to the customer's order. The vendor has about 1000 customers and 3000 products.
In analyzing this situation, which set of business rule logic capabilities should an application developer choose to model this customer's pricing strategy?
Currently there are no comments in this discussion, be the first to comment!