Milestone Project 1 Submission Due:November15 by 11:59 PM Milestone Project 2 Submission Due:November 24 by 11:59 PM Final SubmissionDue:December4 by11:59 PM Instructions For this project you will be designing and implementing a system, in C or C++ to store employee data. Your system should act as a database and allow the user to load in multiple tables of data, run basic queries on the data, and thenstore the data off forlater use.Additionally, sample input files willbe uploaded to canvas in the Project2Instructions and Submissions module.Further, you will need to utilize the GitLab code repository located athttps://apollo.cse.unt.edu/. You may access it fromthe website, the terminal, or an IDE of your choice. Remember while accessing the repository you must use UNT VPNotherwise you may not access it.Also, as a reminder, all the work for this project must be the sole product of the group. You may not share code with othergroups, or download solutions off the internet, as doing so will be considered cheating. If you are struggling with a conceptor implementation, you are encouraged to contact the instructor or your TA’s for aid.RequirementsThis assignment has two parts: a wiki portion and an implementation portion.WikiFor the wiki portion, the group must generate documentation describing their system using the wiki functionality providedby GitLab. The wiki must contain at least one page that provides a high-level description of the entire system and mustcontain at least one page for each of the major functionality components (i.e. if there are four major functionalitycomponents, there should be at least four pages).For the high-level description page, the team must provide a brief description of each of the major functionalitycomponents, how they work together, and some of the major data structures across the entire project. This informationshould not be copied and pasted from the project instructions. The page must also contain a diagram of the entire system,based on the one created during recitations. The diagram must be created digitally (i.e. using PowerPoint, Photoshop,Paint.net, UMLet, etc.), must be easy to read and understand, and cannot a photographed or scanned image.For each major functionality component page, the student accountable for that component must provide a detaileddescription of their component. This description should have three labeled sections: a brief description of the purpose ofthe component, a description of how data was stored and maintained for this component, and a description of thefunctionality for the component. They might also consider including diagrams to more easily visualize how all of the piecesfit together.For the data storage and maintenance section, there should be an explanation of how data was stored and maintained intheir component. What, if any, objects or structs were created to store data? How were they organized and managed?What types of formal data structures did were made use of (trees, graphs, arrays, hashes, etc)?For the functionality component, there should be an explanation of the major functions in the component. How is datamoved and transformed? How is it read in? How is it output? What are the various major functions constructed and howdo they work?Descriptions and explanations should be primarily in prose and paragraph format, not bulleted lists. Code snippets arealso acceptable, but must be used as an enhancement to the explanation of functionality not as a substitution for it.Your grade forthe wiki will partly be based on apparent effort, so please be thorough in your descriptions. Additionally,because this is a wiki, the high-level description page must have links to all of the major functionality component pages.ImplementationYour program must provide the following functionality and adhere to the following constraints:•Your int main() should be in its own .c/.cpp file•All .c/.cpp files, except your main.c/main.cpp, must have associated header files. You may not #include a .c/.cppfile, only header files•Allow the user to choose the file describing the initial setup of the databaseoDoNOThardcode the filename into your programoThe first set of lines in this file will provide a space delimited pair of a file name and a table name thatshould be used for the data within that file. There will be one pair per line, and the pairs may be inany orderoThe next line will be an empty lineoThe remaining lines will be basic operations including INSERT, UPDATE, SELECT, DELETE, DISPLAY andWRITE•For each table file:oThe first line will list the table’s keysoThe second line will list the table’s schemeoAll other lines willbedelimited rows of data to be inserted into the table•While the data may change for different sets of input files, the schemes will always be identical for each table•Each table shouldbeimplemented as a hash tableoYou must have one unique table class per tableoA table class must be defined in its own .cpp and headeroAn entry in a table may be defined either as a class or a struct, and may be a private inner class/structoYou must implement your own hash table and hash function?You may choose your collision strategy from the strategies we have covered in class?You may choose your hashing function from the strategies we have covered in class?Each table must have a different hashing function and collision strategy?The hash function must be implemented as a separate function?You must indicate which hash function and collision strategy your table uses via commentsoYou may not use the map, unordered_map, or any other hash table from any of the C/C++ libraries,STL, or Boost librariesbut can use vectoroYou may not use the hash function or any other hashing function from any of the C/C++ libraries, STL,or Boost librariesbut can use vector•All .cpp files, except your main.cpp, must have associated header files. Youmay not #include a .cpp file, onlyheader files•The queries should be implemented as individual functions in the following way:oDISPLAY()?DISPLAY should output the current state of each table to the user in a tabular format?Be sure to include the attribute names for each tableoQueries must be processed via a regular expressionoINSERT(string ,string) where the first string is a tuple of values, and second string is the table name?INSERT should report to the user and not overwrite the data if there is already an entry withthat key value?Otherwise INSERT should add the data to the table and report a successful insertion to the user?Be sure to specify the tuple and the table when reporting to the useroUPDATE(string ,string) where the first string is a tuple of values, and second string is the table name?UPDATE should report to the user and notupdatethe data if there is no entry with that keyvalue?Otherwise UPDATE should alter the data that key points to and report a successful update to theuser?Be sure to specify the tuple and the tablewhen reportingto the useroSELECT(string ,string), where the first string is a tuple that can have either a value or * for eachcomponent, and second string is the table name?SELECT should report to the user if no rows match the query?Otherwise SELECT should report to the user all rows that match the query?Be sure to specify the tuple and the table when reporting to the useroDELETE(string ,string) where the first string is a tuple that can have either a value or * for eachcomponent,and second string is the table name?DELETE should report to user if no rows match the query?Otherwise DELETE should remove all rows that match the query and report a successfuldeletion to the user ?Be sure to specify the tuple and the table when reporting to the useroWRITE()?WRITE should write the data in each of the tables to a separate file in the same format theywere read in?The first line will list the table’s keys?The second line will list the table’s scheme?All other lines willbe,delimited rows of data in the table?The filename should be the different than the original file name to avoid overwriting•See the example output files for formatting of each of the outputs•Major functionality componentsmust be constructed in some function, or across some functions,thataredeclared and defined outside of yourmain.c/main.cpp. Remember, function declarations must be stored in aheader file, while definitions must be stored in a .c/.cpp file. You may have additional functionsthat support yourmajor functionality component function.•Your code must be well commented.•Each group member should be performing regular commits to the GitLab repository on the Apollo server withmeaningful commit messages. “Fixed bug” or “New code”are not meaningful, so try to be more specific aboutwhat was fixed or what was added.•Please do not commit the example input and output files to the remote server as that may cause a space issue onthe server.•You must provide a .txt format README file whichincludes:oThe names of all group membersoInstructions on how to compile your programoInstructions on how to run your programoAn indication on whether you implemented the bonus or not. By default, the TA’s will assume you didnot attempt the bonus unless you indicate otherwise.•Additionally, you may write a makefile, but please specify if it needs any additional flags to function properly•Each student must be accountable for one or moremajor functionalitycomponents andmay not swap after theysign upfor a component barring an exceptional circumstance. Failure to be accountable for any majorfunctionality component will result in a 0 for the coding portionsof theproject(milestone submission and/orfinal submission). Keep in mind that some componentsbuild on others, so be careful about who takes ownershipof which pieces and manage your time to avoid a crunch near the due date.Also, the group should strive tobalance the work across all members.The major functionality components are:1.Reading in the input file and organizing initial data storage, reading in queries, and outputthe datatothe screen2.Creating the tableto store theemployeedata, and developing functions to insert, update, select, delete,andwritethat datato file3.Creating the table to store thedepartmentdata, and developing functions to insert, update, select,delete, andwritethat datato file4.Creating the table to store theprojectdata, and developing functions to insert, update, select, delete,andwritethat datato fileMilestone Project1SubmissionYour program must provide all requested functionalityfor major functionality component 1 (green colored items above).At least one group membermust submit a .zip file containing the following:•All files necessary to compile and run your program(Please do not include any files not necessary to run theprogram on the CSE machines)•A .txtformat README file explaining how to compile and run your programMilestone Project 2 SubmissionYour program must provide all requested functionalityfor major functionality components 2,3, and 4 (light blue coloreditems above)along with milestone 1. At least one group membermust submit a .zip file containing the following:•All files necessary to compile and run your program(Please do not include any files not necessary to run theprogram on the CSE machines)•A .txt format README file explaining how to compile and run your programFinal Project SubmissionYour program must provide all requested functionalityfor major functionality components 2,3, and 4 (red colored itemsabove) along with milestone2.At least one group membermust submit a .zip file containing the following:•All files necessary to compile and run your program(Please do not include any files not necessary to run theprogram on the CSE machines)•A .txt format README file explaining how to compile and run your programBonus For 10 bonus points, your system must include the PROJECT(SELECT(string,string), string) operation. PROJECT shouldtake in the output from a SELECT statement and a list of columns, and only output data for the columns listed in thesecond string.RubricThe entire assignment is worth 100 points, and each student will receive a single grade with respect to both the entireproject and to the portions they were individually responsible for. The breakdown of those points is as follows.•10points:Project Expectations Document•10points:Project Design•15 (3 x 5 points) points: Project Check-ins•15points:Project Milestone 1 Submission•15points:Project Milestone 2 Submission•20points:Project Final Submissiono10 points:Implemented functionalityo5 points: Proper Commentingo5 points: Group Evaluation•5 points: GitLab Commits•10 points: Project Wiki•10 points: BonusIf your code fails to compile on the CSE machines you will not receive credit for the code portion of the assignment(milestone submission and/or final submission). I recommend not making changes to your code without checking forcompilation before you submit.