And here is what the librarydriver looks like
Next week, you will have to write a class Library and a driver file libraryDriver.cpp The Library class will have to have the following two private data members an array of Book objects books an array of User objects users . e Unlike the other two classes, we will not be providing specific data members or methods we want your Library class to have. Part Il will require you to design a Library class. The program libraryDriver.cpp will need to make use of functions in the Library class to allow users to interact with a book recommendation system. The libraryDriver program will need to have the following features . Load book data and user data from text files. A user must be created for every user in the users file, and a book must be created for every book in the book file Full details on the format of these files will be provided in Part lI Add a new user . .Login. (There are no passwords. Anyone can log in as anyone else simply by providing their name.) Quit. This must automatically save all updated data to your users file View all your own ratings. Rate a book. See recommended books. (A specific metric to compare users to each other will be provided in Part II). e . . For 5 points we would like you to fill the libraryDriver.cpp file we have provided with pseudocode (in comments) describing the algorithms you think you will need to implement the above features. You should specifically address all of the features outlined above to receive full points. You will be allowed to change your approach as you move forward into Part Il without penalty To help you out, here are a few hypothetical runs representing what we want to be possible by the end of Part ll. (Don't pay too much attention to the specific wording, as that may change). These runs all show the default scenario, or the happy paths where nothing goes wrong. You, however, should also consider what will happen when errors occur. For example, what happens if a user accidentally inputs a book rating of 10000? Next week, you will have to write a class Library and a driver file libraryDriver.cpp The Library class will have to have the following two private data members an array of Book objects books an array of User objects users . e Unlike the other two classes, we will not be providing specific data members or methods we want your Library class to have. Part Il will require you to design a Library class. The program libraryDriver.cpp will need to make use of functions in the Library class to allow users to interact with a book recommendation system. The libraryDriver program will need to have the following features . Load book data and user data from text files. A user must be created for every user in the users file, and a book must be created for every book in the book file Full details on the format of these files will be provided in Part lI Add a new user . .Login. (There are no passwords. Anyone can log in as anyone else simply by providing their name.) Quit. This must automatically save all updated data to your users file View all your own ratings. Rate a book. See recommended books. (A specific metric to compare users to each other will be provided in Part II). e . . For 5 points we would like you to fill the libraryDriver.cpp file we have provided with pseudocode (in comments) describing the algorithms you think you will need to implement the above features. You should specifically address all of the features outlined above to receive full points. You will be allowed to change your approach as you move forward into Part Il without penalty To help you out, here are a few hypothetical runs representing what we want to be possible by the end of Part ll. (Don't pay too much attention to the specific wording, as that may change). These runs all show the default scenario, or the happy paths where nothing goes wrong. You, however, should also consider what will happen when errors occur. For example, what happens if a user accidentally inputs a book rating of 10000
