Class Definition Document

[shawncrook411]

Describe all of the classes in your project, including interfaces, base classes, and abstract classes. Make sure your class design is properly modular with loose coupling (i.e. no user interface code in the data model classes or "business logic" classes). Proper class design should also make sure classes are divided appropriately without one class becoming too big or unwieldy. (If you have a class that has more than five fields and/or ten functions it is probably a good candidate to subdivide into multiple classes). In your document, each class should have additional documentation for the following: purpose of the class, purpose of each function, description of any input parameters for the function, description of return value (if any), pre- and post-conditions for the function. Remember you can use LucidChart as described in the class video as a handy tool to create a UML class diagram for this requirement (but not necessary).