Class Diagram

This class diagram works off the model view controller layout with the addition of a web server interfacing the view with the controller (MVC) software design pattern for implementing. This format allows us to make changes on the fly without having to rework the entire program. We can change only the part’s that are needed, or make additions to existing part’s without breaking the previous model, given that the data structure and calling functions remain the same. In this model there has been a few simplifications added: There are several of the functions that variables such as user info, which is a package of information that fit data expected by the receiver. These have not all been specified in full detail but will be based off the root entity of the data being made. Ex. userInfo would include items such as username, id, password, phone, first and last names, and who created them. This was done to simplify the diagram to make it easier to read.

**Note the use of < --- > is being used to imply a vector of data or list, depending on the language used. The syntax used is sudocode for C++ with the use of * implying a pointer to data (where the data can be found) or & being used to pass a copy of the data into an object. Also the stereotypes are purposefully misspelled, due to tools being used to make the model override the appearance of the classes.