The interactive interface of the app, which will allow the student to navigate between features.
The information about the university's classrooms.
The information about every curricular unit the student is enrolled in.
The information about every professor related to the curricular units the student is enrolled in.
The student's grades, which are obtained from the Sigarra Database.
The student's profile, which is obtained from the Sigarra Database.
The student's schedule, which is obtained from the Sigarra Database.
Database from where we get the data relevant to the student.
The app to which the schedule will be exported.
The actual machine owned by the user. Will run the app and allow the user to access all the apps functionalities.
The graphical user interface of the app tailored to allow a easy and intuitive navigation.
The "brain" of our app. Manages all the logic behind the functionalities being the centerpiece of our project and its mainly developed in Fluter.
In direct contact with the User Client Machine this part is responsible for all the connecting between the logic and the user. As said before developed in Flutter with ease of use and accesibility in mind.
The key part of the app logic in direct connecion with FEUP Servers, handles all the requests recived by the users and returns with the correspondent actions or information.
Since exporting to Google Calendar is a selling point of our project this artifact is a must since it will be responsible for handling such matters.
The necessary google connection to allow the export feature to work.
The exporting target of our feature.
University Servers with all the information necessary to make our app work.
API resposible for colecting information.
To verify all our various decisions so far, we created a small prototype of the login app page, using the flutter framework and dart language. Our current implementation is simply visual so that we could test its logic and functionality.
