Your system contains the following functionality:
I. Data Definition part:
a. define new tables: table name, attribute names and types
b. for each defined table ask users to input possible constraints,
including Boolean conditions, FDs and MVDs (in this order):
The legitimacy of constrains should be checked:
1. ignore conflicting Boolean conditions such as age>10 and age<5 should be ignored;
2. trivial FDs should be weeded out, all FDs should be saved
in non-trivial format;
3. trivial MVD or MVD that is trivialized by an existing FD,
e.g., A->->B is trivialized by A->B.
4. foreign key designation, e.g., ssn in table roster is the
key in table student. If one wants to input a tuple in roster
and the ssn is non-existent, the user will be prompted to
either quit the input or inserting a new tuple to the student
table. if one wants to delete a record in table student,
corresponding tuples in roster should also be deleted.
c. ask users to define keys for each table, if the user-defined keys
disagree the keys reached by its FDs, deny them and make viable
suggestions to the users.
My budget is 80$ and I need it as soon as possible . So if you available only then contact me Thanks