Online Dating Decision Services Solutions
Hi Business Rules Vendors and Consultants!
Consider the following situation. You have been approached by an online dating service that wants to use a rules engine to improve its process for matching people. Below is a brief explanation of “business logic” behind their online dating services:
- Each person creates a profile defining their preferences
- The rules check the profiles to determine all the possible matches for a person
- The matches are scored. Higher scores indicate a better match
- Scoring (once the matching criteria are met) is based on the age difference and the number of matching interests
Each profile includes:
- Name
- Gender
- City
- Age
- List of interests
- Minimum and Maximum acceptable age
- Acceptable genders
- Minimum number of matching interests.
And here are the rules (applied to both persons):
- Gender of the other person must be one of the acceptable genders
- Age of the other person must be within the acceptable range
- City must match exactly
- Matching interests of the other person must match at least the number specified
They even provided an example of a compatible match:
- Jane (age 26, lives in Seattle, interests are skydiving, knitting, reading) is looking for a male age 28-32 with at least one of those interests
- Jim (age 29, lives in Seattle, interests are skydiving, soccer, knitting) is looking for a female age 24-29 with at least two of those interests
Now, you need to build a working prototype to win their business. Can you do it? If yes, send your solution to decisionmanagementcommunity@gmail.com.
- Executable English – submitted by Adrian Walker from Reengineering LLC
- InteliOps – submitted by Dr. Vijay Bandekar (DMCommunity members can use a promotion code “DMC30F” to run the service and to try the IDE)
- DMN with Drools – submitted by Edson Tirelli from Red Hat (DMN XML)
- Corticon – submitted by Mike Parish
- MiniZinc – submitted by Hakan Kjellerstrand
You must be logged in to post a comment.