For this assignment we are going to implement the Smallsville Library Management System that we designed in Homework 3. Please note that neither your design or your implementation should incorporate the AV items discussed in the requirements document. These will be address in a future assignment.

For the purposes of this assignment you will need to create a user interface menu that matches your design as well as implement each of the entities as classes in C++. Not we will be using C++ and you will need to use the g++ version of the compiler.

You may not use any of the C++ STL at this time. You may NOT use Inheritance at this time. It is STRONGLY recommended, in fact it is required, that you use a pattern-based solution such as the transaction pattern we have discussed. Other methods or designs will significantly increase your development time, stress level, as well as the degree of difficulty for this assignment. And you will lose a portion of the points since it is required. Be sure that your implementation reflects the information in your updated UML design.

You may need to modify your design from Homework 3 based on grader comments and class discussion. You will need to turn this updated design in as well as use it for the basis of your program Be sure to attend class lectures, as we will discuss many of the topics you will need to complete the assignment! Program Requirements Your program will be written in C++ not any other computer language. You will include the steps in your algorithm in your code. You may, of course, paraphrase them if you like. Your program will be graded based largely upon whether it works correctly on a CSE Department Linux machine. Your program will also be graded upon your program style. At the very least your program should include: A consistent indentation style as recommended in the textbook and in class. It should also use meaningful variable names. A block header comment section that includes: Your Name and Email Address, and a brief description of the program. You must also submit your updated UML Design file, and a short report about your efforts. Each class should have its own header (.h) and code (.cpp) file as well as a .cpp for main and, if needed, a .h file for main if any other functions of constants are needed. This means you will be turning in 2 PDFs (updated UML document and report) , 7 cpp files (6 classes and 1 main) and at least 6 header files (1 for each class) if you create a .h for main then you will have 7 header files.