Meeting Notes #5

Meeting 5

Details

🗓️ Date: 19/03/2023
🕖 Time: 18.00 - 19.00
📍 Location: Zoom
📝 Note Takers: Begüm Arslan

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

1. Review the previous req.
2. system req, gorev dagilimi
3. Milestones

Meeting Notes (Numbering is done according to the agenda)

1. Reviewed the previous requirements.

• System requirements are connected to user requirements.

2. System requirements: deciding on roles:

• profile is assigned to Mehmet.
• feedback system is assigned to Merve.
  • Feedback system is for informing the admin about false information, and banning the users related to it.
  • It can also be used for approving a need or resource, this way these items can be above in a list.
• Resource is assigned to Burak and Begüm for revision.
  • Resource type should be flexible. There are constant types and an other type.
  • There should be an upper class for boots and shoes as an example.
  • Resources should be updated based on discussion.
• Event and Action is assigned to Cahid and Aras.
  • Event and action difference is asked to Alper hoca. It will be shared with the group.
• Need is assigned to Merve and Şahin.
• Map is assigned to Hasan.
• If one wants to comment on an issue assigned to someone else, they can write it on the page inside paranthesis with their names.
• Or they can write it to under issue.
• Annotaion is assigned to Emin
• Administration is assigned to Şahin, Hasan.
• Notification should be revised and first two points should be deleted.

3. Mock Ups

• Each page should be carried into another mockup if storage error is encountered.
  • They should be saved into github.
• Map Mockup is added by Hasan.
• Event and Action mock ups should be prepared by Halil and Hasan is the reviewer.
• Actions should be added into main page mock up.

Glossary should be written after some points are discussed.

• Entity of information can be used to imply a resource, need, event and action.
• Need is decided against demand by unanimity .   We can have a little meeting before the class. Use of Whatsapp should be reduced.

Action Items

Action	Issue	Assignee(s)	Deadline
Action	link	Member	DD/MM @ HH.MM
Issue: Annotation	-	Mehmet Emin İpekdal	21/03
Issue: Needs	-	Merve Gürbüz, Aras	21/03
Issue: Resources	-	Begüm and Burak	21/03
Issue: Event and Action	-	Aras and Cahid	21/03
Issue: Feedback System	-	Merve Gürbüz	21/03
Issue: New mockups	-	Halil İbrahim Gürbüz	21/03