Charts

You are given the following description of a software system:

Create a set of C++ classes that can be used to implement this program. This will express the high-level design of the program.

• Coding style Each class will consist of a .hpp file (example: Stuff.hpp) with the class definition, and a .cpp file (example: Stuff.cpp) with the definition of the methods. Yes, you must use include guards.
• Use Doxygen commments Use Doxygen comments in your code. Refer to my examples in the class Stuff. Use the style of Doxygen tags as given in my examples.
• No main In OOP programs, the main is not that important (unlike in structured programs). Do not include a main.
• Make sure it compiles Compile each class .cpp file to object code. Look at the example Makefile) for the g++ command to use.
• No constructors Do not declare or implement constructors of any kind. If you need functionality, create a method. We are looking at high-level design (although expressing it directly in C++). The choice of whether to implement something in a constructor or a member function (or even a free function) is a lower-level design issue
• Empty methods Do not implement the methods. Put in only enough code so that the methods will compile, e.g., return 0;.
• Polish your design Spend time on issues such class names, method names, parameters, etc. Keep in mind the issues of object models including abstraction, encapsulation, modularity, hierarchy, typing, concurrency, and persistence. Consider how your design would effect using multiple developers on the project and for testing individual parts.
• Required Readme file In a Readme file, discuss your design. Include any alternative decisions that you had to make, or issues that you changed over time.