Sprint Specific Assignment: Architecture Diagram
The main task for this sprint was a framework for which we could build on, and more specifically an Architecture Diagram that would serve to highlight how the information will flow through our end product and demonstrate a little of how it will be used.
Below is this diagram, made according to standard flowchart symbolism and with attention paid specifically to how data and input flow from one part to another.
The diagram assumes a user will start in the top left corner when they actually open up the app. They first have the choice of whether they are a Visitor or if they would like to actually sign in with a TU Account.
If a user does not want to sign in they are directed to a Guest View with limited features. For example, they would be able to use the interactive map and find specific data about certain buildings. If a user signs in, they either sign in as a Facilitator or as a Student depending on their designation within the TU system. A User who is the former still can access the map information, but they can also create events that would get populated to the map of other users. The latter, students, would also be able to sync up their schedules to get class assignment notifications and the like, or if they want to follow an event they can be alerted when it starts.
All of these information requests and updates flow directly from the Mobile App that makes up our Front End into the React Native Environment that makes up our Back End. The Back End then gives out the requested information to the Front End when prompted by the User.
The Back End also makes requests to both query information from and update the information to our Database, which will naturally store information the Back End tells it to as well as return the queried information. The Database will initially be populated with data about the map from the developers and with information about the user's accounts from an external TU database if we are able to get access to it.