Milestones and Feedback
In this section, we present the documents created throughout the project, including presentations and reports for each milestone. We also highlight the feedback received from our professors and the adjustments we made to improve our work based on their insights.
Calendar
Note: This calendar can be subject to change in the future.
Milestone 1
On this milestone, we were asked to present an overview of our project, such as the project's context, its main problems and goals, and some of the related work. Moreover, we were also required to show the project's calendar.
Milestone's File
Feedback and Improvements
For this milestone, we received feedback from our professors highlighting areas for improvement, including poor time management, as we exceeded the allotted presentation time. To address this, we began conducting practice runs with our tutor to refine our delivery. Additionally, we were questioned about whether our project was solely focused on API implementation. In response, we emphasized that our work not only involved developing APIs but also deploying various services to ensure a comprehensive solution.
Additionally, we also made sure to point out, in an email sent to the course's regent, that as we were working with a fairly new technology aimed at the industry, and not academic research, the quantity of research papers was reduced which meant we were going to use mostly white papers and press releases. Moreover, we also asked the course's regent if there would be any impact if we did not show a graphic interface, as our project is not aimed at a final client that would work with a User Interface, instead it is aimed at developers that would integrate our solution with their product. We were told that it would not have any impact; however, we had to show the result of our work over the semester.
Milestone 2
On this milestone, we were required to present a brief overview of our project, a more in-depth view on the state of the art, the requirements we gathered (functional and non-functional) and our system's architecture.