New and updated diagrams

[leandrumartin]

Pull Request Summary

A brief description/summary of your PR here. What does it add? Why is it necessary? How was the change made, and how was it tested?

• Database structure diagram updated with lines to visually show connections between database items. For example, a line is added from the boneset bones array to the bone id field to visually show that the array contains a list of strings corresponding exactly to the IDs of various bones.
• New backend and overall data flow diagrams are added to show new project architectural direction

Detailed Description

A more detailed description and any additional information.

We will be moving the project away from storing our data in a branch on GitHub. Instead, it will be stored in a folder on the server. This will:

• remove points of failure, making our project more reliable and less prone to failure
• make our project more secure by eliminating attacks on GitHub as a way to attack our app
• allow us to develop faster and easier. If you're working on a feature and it requires that data be updated, you would be able to make the appropriate changes in the same app instead of making a pull request and needing it to be accepted before you can even verify whether the change achieved the result you want.

[leandrumartin]

@Joishee05 @Brehana-Naidu Let me know whether you think the diagrams are clear and understandable, and if you have any questions on them or about the project direction.

(As a side note, this project direction should be reflected in our showcase presentation. Hopefully we will be able to move the data from GitHub onto our server by the end of the semester.)

[Brehana-Naidu]

It looks good, but I honestly can't see any difference between the old and new overall data flow files.

[Joishee05]

Everything looks good to me!