Meeting Notes ‐ 3
📅 Date: 2025-02-21
📍 Location: Google Meets and Slack
⏰ Time: 20:00 - 21:30
⏳ Duration: 90 Minutes
| Member | Participated |
|---|---|
| Yusuf AKIN | ✔️ |
| Nuri BAŞAR | ✔️ |
| Berkay BİLEN | ✔️ |
| Fatih Furkan BİLSEL | ✔️ |
| Mete DAMAR | ✔️ |
| Berk GÖKTAŞ | ✔️ |
| Hasancan KELEŞ | ✔️ |
| Onur KÜÇÜK | ✔️ |
| Arda SAYGAN | ✔️ |
| Taha TOPALOĞLU | ✔️ |
| Yusuf Anıl YAZICI | ✔️ |
- Project selection
- Sharing tasks for project
- Coming up with requirements
- Writing elicitation questions
- Creating scenarios
After project descriptions had been posted on Moodle, we as a team decided to look through them and decided on one. Further details on this are already on Meeting Notes 2. In order to make sure our arguments are orderly, we opened a discussion page.
- Results: After voting was done and some of our group members offered their opinions, we decided on taking project number 9, Affordable & Healthy Eating Hub.
In 3 drafts (last one is currently up to date) team members briefly described the characteristics and features of the program.
- Functional Requirements: The ones that describe the functionaly of the software system.
- Non-Functional Requirements: The requirements that are not related to functional aspects.
Elicitation is an important(and first) step of the requirement engineering process. To this end, team members came up with what users can expect from the product and system's boundaries. For this they came up with 4 categories:
- Budget Related
- Balanced Diet
- Recipes
- Local Food Stores
Last but not least, scenarios are another important part in which they help us simulate what kind of experiences customer or developer may go through and with this we can prepare accordingly.
- Scenario 1: Describes the app and goes into details about how app can help in different scenarios.
- Scenario 2: Describes how a user with low budget can use the app.
- Scenario 3: Step by step describes how another user with low budget can prepare a healthy meal according to their preferences.
| Action | Asignee | Linked Issues | Deadline |
|---|---|---|---|
| Creating draft requirements | Mete Damar, Berk Göktaş, Furkan Bilsel, Nuri Başar | #41 | 27 Feb, Thur, 24:00 |
| Creating Scenarios | Arda Saygan, Berkay Bilen, Hasancan Keleş, Yusuf Akın | #42 | 27 Feb, Thur, 24:00 |
| Creating Elicitation Questions | Taha Topaloğlu, Onur Küçük, Yusuf Anıl Yazıcı | #44 | 27 Feb, Thur, 24:00 |
-
Use Cases:
- Template
- Scenario 1: Community Sharing
- Scenario 2: For a Dietitian
- Scenario 3: Maintaining a Personal Inventory (as a Producer)
- Scenario 4: Proposing a Product and Adding a Recipe to Weekly Meal Plan
- Scenario 5: Creating a Meal Plan
- Scenario 6: Resetting Password
- Scenario 7: Moderator Actions
- Scenario 8: Searching for and Proposing a New Food Item
- Scenario 9: Budget-Conscious Grocery Shopping
- Scenario 10: Creating a New Store
- Scenario 11: User Profile Management
- Git: In a Nutshell
- Example GitHub Repositories
- System Modeling & UML
- Frontend Tutorial
- Frontend Roadmap
- Frontend Styling Guide
- Docker Summary
- Writing Endpoints
- Yusuf AKIN
- Arda SAYGAN
- Fatih Furkan Bilsel
- Berk GOKTAS
- Berkay BILEN
- Yusuf Anıl YAZICI
- Taha Topaloglu
- Nuri Basar
- Onur Kucuk
- Hasancan Keles
- Mete Damar