Deliverable 3 Report

Deliverable 3 – Web Frontend, Architecture Modeling

Due Date: March 24th, 2019 23:30

1. Architecture Modeling
2. Implementation of Web Frontend
3. Integration of Web Frontend with Backend Services
4. Build System, Continuous Integration and Delivery
5. Project Management and Project Report

Total hours spent on different tasks

Tasks	Total hours
Architecture Modeling	5
Implementation of Web Frontend	15
Integration of Web Frontend with Backend Services	32
Build System, Continuous Integration and Delivery	4
Project Management and Project Report	4
Total	60

Meeting #7

Date: 12th March 2019
Time: 1h30
Report:
Sprint 2 Retrospective
Correction of some issues from sprint 2
sendReminders() method was not working correctly, Julien was assigned to correct it

Meeting #8

Date: 18th March 2019
Time: 1h
Report:
Sprint 3 Planning, Zenhub updated with the new issues for Deliverable 3
We decided to integrate 4 of the 5 User Cases developed for the previous deliverable in the frontend.
Each member is responsible for the same service as the one developed for Deliverable 2.
We decided that for UC5 (send reminders to problematic student), the reminders will be sent automatically. Therefore, a frontend integration will not be needed: we used Heroku Scheduler, a Heroku add-on, to send GET request, to the API used to send the reminders. Every day at 9am, we send a request to the API and the problematic students receive a reminder.

Meeting #9

Date: 22nd March 2019
Time: 2h
Report:
We finished the implementation and integration of web frontend
This meeting was used to help some members with specific issues about the implementation of their service