Databases Concepts and C++ Programming

Below is the description of project. I need simple console application on Visual Studio 2012 (preferable) but 2010 or above will work. Project Description Below: what to submit: 1. source file 2. a file with sample running results 3. a readme file explaining how to compile/run your program 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. II. Data Manipulation part: a. users can input new tuples to all tables, your system should deny those that violate FDs. The foreign key designation may demand additional tuples in other tables (see the example in I.c). b. users can delete a tuple based on key value, and again take care of the cross-table dependencies c. users can perform actions below for one table: i) find attribute(s) for tuples which satisfy conditions for some attributes ii) group tuples based on one or several chosen attribute d. users can choose to perform the following operators for two tables: cross join, natural join, union, intersection, difference e. users can delete a table and ensure the across-table integrity. To reduce the complexity of your program, the following constraints are in effect: 1. _at most_ four attributes for a table. 2. single character (upper case) attribute names. 3. the type for ALL attributes is either string or integer. Please let me know how quick you can finish it. Thanks