By building the user workflow, also known as the ‘user journey’ or ‘story’ I’ve established the features and systems that need to be built. For example, the start of a user journey begins at the login screen, immediately exposing the need for strong authentication. This includes fine-grained permissions with many different per-feature permission levels; Administrators could create teacher users, and give them specific permissions, like only being able to view their current students locations (instead of being able to see the whole school). Then, users would be directed to a dashboard, full of the information aggregated from both APIs that could be connected to the app (Schoology, Illuminate ect.) This dashboard would organize and provide insights to the user. Analytics would include lists of students that attendance or grades are concerning and need to be addressed, locational data around students, and location metrics for students who are often skipping or not following school policy. Some of this data may need to be inputted manually, which would need its own system that is able to parse csv or json formats. All of this data would need to be stored in a secure database, either self hosted or a cloud solution (depending on what can be attained for this project). The most unique part of the app would be the location and camera system. This would require some form of containerized workers that would connect with security cameras and run ML / Deep learning systems to identify and sort faces and behavior. All of that would then be added to the database and in turn displayed in the site. Although each of these elements have their own complexities and challenges, I am excited to build production ready solutions.