Meeting Notes #10 - bounswe/bounswe2024group9 GitHub Wiki
Meeting Information
Date: 28.03.2024.
Time: 21:00
Online/Offline: Online
Location: Discord
Duration: 1 hour 10 minutes
Note Taker: Kristina Trajkovski
Attendees
- Mehmet Emin İpekdal
- Mustafa Atak
- Ahmet Burak Çiçek
- Eray Eroğlu
- Huriye Ceylin Gebeş
- Halil Karabacak
- Muhammet Berkay Keskin
- Özgür Özerdem
- Yiğit Kağan Poyrazoğlu
- Taha Topaloğlu
- Kristina Trajkovski
Agenda
- Go over the feedback given by the professor.
- Clearly state the corrections needed and assign them.
- Talk about different diagrams and plan their completion.
Discussions
Important points received from the feedback meeting:
- Revise the structure of meeting notes (keep just a few in homepage and the rest with a link or in sidebar only)
- Elaborate on the personas in scenarios
- Add more details from Wikidata in search results (more resources, links, info, etc.)
- Sync mockup designs and colors
- Revise the elicitation questions - some were too complex (need revision or deletion), think of more answers, structure them
- Revise the requirements - check the format, go over the hierarchy, delete requirements which describe what a user/system cannot or should not do (add only what they can or should do), add meanings of unclear actions/entities to the Glossary
- Add reviewers to issues
- Create more templates
Besides the feedback, we talked about creating use-case, class, and sequence diagrams. We quickly went over of how they should be done (check lecture "design" slides) and discussed how we should sync. We decided to use a platform where we will be able to see each other's work at all times with Figma and Lucid charts as examples (the actual site of use is to be determined).
We also noted that we should start implementing our application soon, so learning how to use and implement Wikidata API into our designs and pages shall be explored.
Action Items
| Item | Responsible Person | Due Date | Relevant Issue | Reviewer(s) |
|---|---|---|---|---|
| Revise the requirements (structure, glossary, details + open/assign other issues to team members as necessary) | Mutti, Halil | 07.04.2024. | #111 | Kristina |
| Change colors of login/signup mockups | Berkay, Ahmet | 07.04.2024. | #112 | Emin |
| Revise elicitation questions (format, structure, deletion, answers) | Ceylin, Yiğit Kağan | 07.04.2024. | #113 | Özgür |
| Login and Signup Diagrams | Ceylin, Taha | 14.04.2024. | #118 | Berkay, Ahmet |
| Feed Diagrams | Mutti, Eray | 14.04.2024. | #115 | Kristina, Halil |
| Search Results Diagrams | Kristina, Halil | 14.04.2024. | #114 | Mutti, Eray |
| Route Creation Diagrams | Ahmet, Berkay | 14.04.2024. | #117 | Yiğit Kağan, Özgür |
| Route Details Diagrams | Emin | 14.04.2024. | [ADD ISSUE] | Ceylin, Taha |
| Profile Diagrams | Yiğit Kağan, Özgür | 14.04.2024. | #116 | Emin |
Conclusions
The feedback corrections shall be done as soon as possible. The diagrams are due at the end of the break; they are assigned to pairs for now, but will be discussed at the next meeting. If necessary, help will be provided across different teams.