Hi all,
I was wondering if anyone might have any insights on a project I'm working on. I'm tasked to create a logical data model for a new system.
The system is an Option Configuration for Vehicle purchasing. Such as adding a High End Audio system to a car, or a Leather Interior package.
Where the design get's difficult is in modelling the rules. Every option might have rules associated with it. These rules define other options that must be purchased in addition to the given option, or options that can't be purchased in conjuction with the given option.
Examples of rules:
purchase option [AUD]- High End Stereo
requires purchase of
[SPK] - Bose Speaker package
excludes purchase of
[STR] - Basic car stereo
the rules can get more complicated:
[HTH] - Heated Drivers Seat
requires:
([LT] - Leather Seats
AND
[PWR] - Power Seats)
OR
[INT] - Interior Upgrade Package
Any insight on how to represent the rules in a Database so a program can automatically determine option relationships is appreciated.
PF
(On an infant's shirt): Already smarter than Bush