-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #278 from bounswe/egecans-lab_report_1
Add files via upload
- Loading branch information
Showing
1 changed file
with
63 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| # Project Development Weekly Progress Report | ||
|
|
||
| **Team Name:** Disaster Response Platform (DaRP) | ||
|
|
||
| **Date:** 03.10.2023 | ||
|
|
||
| ## Progress Summary | ||
|
|
||
| **Our objective for the following week** is to review the requirements and organize them in the appropriate format; then accordingly updating the use-case, class, and sequence diagrams. We will also define the technologies to be used by the Mobile, Back-end, and Front-end teams. Additionally, we will update the Wiki pages and issues. Moreover, we will evaluate the feedback received to minimize the mistakes made by the team in the previous semester. | ||
|
|
||
| ## What was planned for the week? How did it go? | ||
|
|
||
| | Description | Issue | Assignee | Due | PR | Estimated Duration | Actual Duration | | ||
| | ----------- | ----- | -------- | --- | --- | ------------------ | --------------- | | ||
|
|
||
| ## Completed tasks that were not planned for the week | ||
|
|
||
| | Description | Issue | Assignee | Due | PR | | ||
| | ----------- | ----- | -------- | --- | --- | | ||
|
|
||
| ## Planned vs. Actual | ||
|
|
||
| ## Your plans for the next week | ||
|
|
||
| | Description | Issue | Assignee | Due | Estimated Duration | | ||
| | -------------------------------------------------------------------------- | --------------------------------------------------------------- | ---------------- | ---------- | ------------------ | | ||
| | Revise issues on not closed past | [#260](https://github.com/bounswe/bounswe2023group2/issues/260) | Merve & Begüm | 06.10.2023 | 15 min | | ||
| | Create personal pages for newbies | [#262](https://github.com/bounswe/bounswe2023group2/issues/262) | Aziza, Buse, Can | 09.10.2023 | 1 hr | | ||
| | Presentation to newbies | [#263](https://github.com/bounswe/bounswe2023group2/issues/263) | Team | 03.10.2023 | 30 min | | ||
| | Re-verify the requirements | [#264](https://github.com/bounswe/bounswe2023group2/issues/264) | Team | 07.10.2023 | 3 hr | | ||
| | Update the class diagram w.r.t. the changes in the requirements | [#265](https://github.com/bounswe/bounswe2023group2/issues/265) | Team | 09.10.2023 | 1.5 hr | | ||
| | Update the use case diagram w.r.t. the changes in the requirements | [#266](https://github.com/bounswe/bounswe2023group2/issues/266) | Team | 09.10.2023 | 1.5 hr | | ||
| | Update the sequence diagram w.r.t. the changes in the requirements | [#267](https://github.com/bounswe/bounswe2023group2/issues/267) | Team | 09.10.2023 | 1.5 hr | | ||
| | Creating a communication plan | [#268](https://github.com/bounswe/bounswe2023group2/issues/268) | Merve | 08.10.2023 | 1 hr | | ||
| | Select a sub-team | [#269](https://github.com/bounswe/bounswe2023group2/issues/269) | Team | 06.10.2023 | 15 min | | ||
| | Decide on what technologies are going to be used for the front-end | [#270](https://github.com/bounswe/bounswe2023group2/issues/270) | Front-Team | 08.10.2023 | 30 min | | ||
| | Decide on what technologies are going to be used for the back-end | [#271](https://github.com/bounswe/bounswe2023group2/issues/271) | Back-Team | 08.10.2023 | 30 min | | ||
| | Decide on what technologies are going to be used for the mobile | [#272](https://github.com/bounswe/bounswe2023group2/issues/272) | Mobile-Team | 08.10.2023 | 30 min | | ||
| | Update side-bar | [#273](https://github.com/bounswe/bounswe2023group2/issues/273) | Egecan | 03.10.2023 | 15 min | | ||
| | Update readMe | [#275](https://github.com/bounswe/bounswe2023group2/issues/275) | Halil | 05.10.2023 | 15 min | | ||
| | Update Wiki Home | [#274](https://github.com/bounswe/bounswe2023group2/issues/274) | Burak | 05.10.2023 | 15 min | | ||
| | Evaluate Feedbacks from last year | [#276](https://github.com/bounswe/bounswe2023group2/issues/276) | Team | 06.10.2023 | 30 min | | ||
| | Cross-team technology sync - verify that these technologies are compatible | [#277](https://github.com/bounswe/bounswe2023group2/issues/277) | Team | 08.10.2023 | 15 min | | ||
|
|
||
| ## Risks | ||
|
|
||
| - Updates on requirements may be too much, therefore time for updating the use-case, class diagrams and sequence diagrams will be over | ||
| - 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. | ||
| - Participants who select a team can not have enough knowledge, they can spend much time learning technologies. | ||
| ... | ||
|
|
||
| ## Participants | ||
|
|
||
| - Egecan Serbester (Writer) | ||
| - Begüm Arslan (Reviewer) | ||
| - Merve Gürbüz | ||
| - Cahid Enes Keleş | ||
| - Aziza | ||
| - Buse Tolunay | ||
| - Mehmet Kuzulugil | ||
| - Ramazan Burak Sarıtaş | ||
| - Halil İbrahim Gürbüz | ||
| - Can Bora |