This is a class diagram depicting the core flow of information and logic throughout the Teatime Tracker application. The yellow boxes represent the main models/database tables. Note: the identity user contains more fields and is auto-generated by AspNetCore Identity. The blue boxes are interfaces and the orange boxes are services that implement those interfaces. The red box is my main controller, “DashboardController”. It requires many services and manages control between the view and the data.

Here is part of the homepage of the application. Showing the Register/Login functions and the main navigation menu.

This is the top part of the dashboard which is the heart of the application. From this page the users can quickly see their main statistics and add/edit cups of tea. Further down the page is a recommendation section that recommends the user's next cup of tea depending on the time and their caffeine intake. Finally at the bottom there is the reports section.

The reports section is lower down on the dashboard page. As of writing this there are three reports available to generate; cups per day, caffeine per day, and number of cups by type. Shown here is an example of the caffeine per day report.

This page allows the user to add a cup of tea. First they select a type of tea from the database-populated list (black, green, herbal), once their selection is made the variety list populates with varieties of teas from the selected type. Then the user enters the date they had that cup of tea and hits save.

The edit page is very similar, first the user enters the date of the cup they want to edit and the page produces a list of teas from that day (very similar looking to the reports list). The user then clicks the cup and the edit page pre-populates the dropdowns which the user can then edit.