Meeting Notes #7 30.03.2023

Meeting

Details

🗓️ Date: 30/03/2023
🕖 Time: 17.00 - 18.50
📍 Location: CMPE çatı
📝 Note Taker: Merve Gürbüz

Attendees

• Aras Güngöre
• Begüm Arslan
• Cahid Enes Keleş
• Egecan Serbester
• Halil İbrahim Gürbüz
• Hasan Bingölbali
• Mehmet Emin İpekdal
• Mehmet Kuzulugil
• Merve Gürbüz
• Ömer Şahin Albayram
• Ramazan Burak Sarıtaş

Agenda

• Finalizing Discussion #63
• How to improve communication between us
• Should we prepare proposition template for tendering our ideas to group
• [Proposed] Ideas about enriching the wiki main page issue (As @Sahin-Albayram mentioned in his comment)
• [Proposed] UML Diagrams to prepare
• Planning non-functional requirements
• Reviewing & improving mock-ups (Notification Mockups)

Meeting Notes

1. Discussion #63 has been completed. Action can use resources and needs as input and output. Resources and needs can be used or created while creating actions.

• 1.1 Events can be related to the actions but they are not functioning like resources or needs. So we decided to put an optional select field that a user can select a related issue to the action.
• 1.2 Keeping the last updated time for actions will help app to show users whether it is up to date or not.
• 1.3 There will be estimated time of completion of actions.

2. Notifications can be done via tags, a user can want notifications about the tags such as accomadation or food. Tags can also be used in filtering.

• 2.1 We did not write this in the requirements, it is need to be added.

3. We should show the amount of needs and resources in order to prevent waste. For example, we should show how many blanket we have as a resources and how many is needed.
4. User types are changed:

• 4.1 Guest user: only create emergency typed needs (what is the emergency and what kind of information is wanted from the user ?)
• 4.2 Authorized user: The user that registered to the system, !! phone number and email should be interchangeable.
• 4.3 Verified user (Role-based user): The name should be changed. Verified user shall have a role and we can provide a place that a user can upload a proof of its proficiency.
• 4.4 Superuser : This type of userhas to be approved by admin. This user has location-based privileges since their information is more reliable and they can be organization level volunteers (such as mayor of the city, director of ahbap)

5. Use cases will be listed in an issue and each member should write additional use cases. Any team member are encouraged to creat an issue for implementing use case diagram.
6. The issues related to use case diagram will be gathered in usecase milestone.
7. Requirements shall be editted according to meeting decisions.

Action Items

Action	Issue	Assignee(s)	Deadline
Create listing use cases issue	#78	burak Sarıtaş	04/04
Revise action related requirements		Cahid Enes Keleş	04/04
Revise notification related requirements		Begum Arslan	04/04
Revise user actions requirements	#79	Şahin Albayram	04/04
Revise notification related requirements		Begum Arslan	04/04
Start creating use cases		Group Work	04/04