Skip to content

Latest commit

 

History

History
72 lines (61 loc) · 6.31 KB

lab_report_4.md

File metadata and controls

72 lines (61 loc) · 6.31 KB

Project Development Weekly Progress Report

Team Name: ResQ (Disaster Response Platform)
Date: 24.10.2023

Progress Summary

This week focused on updating design documents and establishing the project's core structure. We improved the codebase for the back-end, the front-end, and the mobile in a way that they work consistently . Our objective for the following week will be to improve our code to satisfy more requirements and prepare for the milestone presentation.

What was planned for the week? How did it go?

Description Issue Assignee Due PR Actual Duration Estimated Duration
Update RAM #268 Team 24.10.2023 -- 3hr 3 hr
Continue on the revising diagrams #242, #243, #244 Back-end Team 24.10.2023 -- 3hr 2 hr
Reviewing mock-ups considering web page design #269 Front-end Team 24.10.2023 -- 1hr 2 hr
Reset the branches that are used for practice app, and create new base branches. Planned, not done. #263 Team 24.10.2023 -- 1 hr
Login screen, registration #275 Harun 24.10.2023 -- 8hr 10 hr
Main screen navigation bar #277 Alperen 24.10.2023 -- 5hr 10 hr
User profile screen #278 Çağrı 24.10.2023 -- 6hr 10 hr
Setting and notification page screen #280 Elif 24.10.2023 -- 1hr 10 hr
Deployment of backend #281 Back-end Team 24.10.2023 -- 1hr 4 hr
Frontend Investigate and Implement Authentication Stack #282 Front-end Team 24.10.2023 -- 6hr 10 hr
Design API for victim functionalities #283 Back-end Team 24.10.2023 -- 3hr 4 hr
 Frontend Login and Registration Pages #279 Front-end Team 24.10.2023 -- 6hr 4 hr
Frontend Implement Draft Map Page #284 Front-end Team 24.10.2023 -- 4hr 6 hr
Implement location services via keeping location info on database #285 Back-end Team 24.10.2023 -- 1hr 3 hr

Completed tasks that were not planned for the week

Description Issue Assignee Due PR
Class diagram revisit #243 Volkan 24.10.2023
Implementation of database relations #259 Ali 24.10.2023 [#287]

Planned vs. Actual

  • We planned to finish (#275, #277, #278, #280, #281) issues last week, but they are a little more challenging than we anticipated so we will be still working on them even though we didn't plan that way.

Your plans for the next week

Description Issue Assignee Due Estimated Duration
Main screen navigation bar continue #277 Alperen 31.10.2023 5 hr
User profile screen continue #278 Çağrı 31.10.2023 4 hr
Setting and notification page screen continue #280 Elif 31.10.2023 9 hr
Login screen, registration continue #275 Harun 31.10.2023 2 hr
Deployment of backend continue #281 Türker 31.10.2023 3 hr
Creat User case scenario #298 Mobile Team 31.10.2023 8hr
Design API for victim functionalities #283 Volkan 31.10.2023 3hr
Reviewing mock-ups considering web page design continue #269 Front-end Team 31.10.2023 4hr
Design API for responder functionalities #296 Furkan 31.10.2023 4 hr
Creat User case scenario #299 Frontend Team 31.10.2023 12hr
Implement jwt based authentication for login and queries #300 Kübra 31.10.2023 12hr
Frontend Implement Draft Map Page #284 Ilgaz 31.10.2023 10hr
Finalizing category tree #297 Ali 31.10.2023 3hr

Risks

  • Extended user roles (e.g., facilitator, responder) may require additional fields that we did not consider in the initial design. We will address these issues as they arise.
  • It is a great possibility that frontend team can face challenges at jwt bassed authentiction because it requires new technical learning process.
  • The map library we have chosen does not natively integrate with react. It has proven difficult to integrate it with react, which is why the issue is ongoing. These difficulties might persist. ...

Participants

  • Alperen Dağı
  • Ali Topcu
  • Çağrı Gülbeycan
  • Elif Tokluoğlu
  • Furkan Bülbül
  • Harun Reşid Ergen
  • Ilgaz Er
  • Kübra Aksu
  • Orkan Akısu
  • Volkan Öztürk