Lab Report Week 2

Project Development Weekly Progress Report

Team Name: Web Info Aggregator Date: 03.10.2023

Progress Summary

This week We did some revisions on our previous design artifacts. Removed some unnecessary requirements and clarified some of the ambiguous requirements. We applied these changes to our mock-ups and use case diagrams. We also refined some parts of our sequence and class diagrams. However, this work is not complete yet since we notice new possible changes to our design as we think on the practical applications of our design points.

Each member of the team decided on which part of the development they will work (web, back-end, mobile).

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

Description	Issue	Assignee	Due	Artifact	Estimated Duration	Actual Duration
Each member will be assigned to at least one group.	#189	All	04.10.2023	Who We are	20 min	30 min
Reorganize the wiki to accommodate 451	#190	Bahadir	05.10.2023	---	3hr	50 min
Each member will vote for course-related roles.	#191	All	05.10.2023	---	1hr	5 min
Revising requirement specifications.	#192	Egemen, Baki, Bahadır	09.10.2023	Requirements	15hr	5hr / requires feedback
Revisiting the use-case diagram.	#193	Meriç, Bahri	08.10.2023	Use Case Diagrams	3hr	1hr
Revisiting the mock-ups.	#194	Furkan, Ömer, Begüm, Sude	08.10.2023	Mock-ups	5hr	1.5hr
Revisiting class diagrams.	#195	Miraç	08.10.2023	---	3hr	---
Revisiting sequence diagram.	#196	Begüm, Sude, Egemen	08.10.2023	Sequence Diagrams	5hr	2hr

Completed tasks that were not planned for the week

Description	Issue	Assignee	Due	PR
Added lab reports in the repo under reports folder	#197	Bahadır	09.10.2023	#198
Fix and create folders for the upcoming project	#199	Bahadır	09.10.2023	#200

Planned vs. Actual

• We planned to decide on the structure of group organization by voting on the communicator and dividing team members by subgroups. Even if the organizational decisions can change later for practical reasons, organizational issues can said to be complete.
• Besides that, the main problems that need to be solved in this week were revision and refactoring of project artifacts. We changed deficient parts of requirements and also took notes about parts that are not completely clear among the group. We arranged the class diagram, the sequence diagram, the use case diagram and the mockups according to mentioned changes in requirements. However, we realized that it is not possible for us to complete the revision of requirements without having another meeting with customer. @bakikucukcakiroglu held a question session with customers after Tuesday's lecture to clarify ambiguous parts. Then, we postponed completion of revision issues to the next week since all revisions are dependent of revision of requirements.

Your plans for the next week

Description	Issue	Assignee	Due	Estimated Duration
Decide on what technologies are going to be used for the front-end	#5	Front-Team	02.10.2023	1hr
Create resource, user, and action data models together with their CRUD operations	#10	Ayse	05.10.2023	2hr
Create facilitator, responder, coordinator, and victim data models by extending the user data model	#11	Ali	07.10.2023	3.5hr
Create an EC2 host machine and write a GitHub action that will sync the host machine when there is a push to the main/release branch	#12	Alice	07.10.2023	15mins

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. ...

Participants

Name	Participation
Bahadır Gezer	✅
Hasan Baki Küçükçakıroğlu	✅
Egemen Kaplan	✅
İbrahim Furkan Özçelik	✅
Ömer Faruk Çelik	✅
Begüm Yivli	✅
Enes Yıldız	✅
Sude Konyalıoğlu	✅
Bahri Alabey	✅
Orkun Mahir Kılıç	❌
Miraç Öztürk	✅
Meriç Keskin	✅