Date: 16 Mar 2025

• Başar Temiz
• Eren Akçin
• Samed Kızılhan
• Umut Şendağ
• Ceyda Irwin
• Mert Kirman
• Ömer Faruk Çelik
• Berkay Ak
• Bora Toprak Temir
• Mustafa Ocak
• Cenk Yılmaz

• The main discussion was on the completing, and patching up the shortcomings of the current Class Diagram. Previously a 4-person group prepared the class diagrams and another 5-person group reviewed and updated it. Details on the progression can be found here
• The reviewed class diagrams will be reviewed again as a group, finalized, and then put to the wiki in another meeting very soon this week
• The seperate use case diagrams will be combined into one and put on the wiki (see issue #68)
• Requirement 2.2.2 is changed from an obligation to an optional feature, as discussed with the assistant.
• We went over the requirements again to discuss what our current diagram lacks, and how can we reflect these funcionalities in the next meeting where we will update the class diagram.

• Requirement 3.1.1 isn't satisfied in the class Class diagram, we will add that functionality to the diagram in the following meeting
• The Class diagram isn't explicit about how the user's previous savings are stored and evaluated. We should add a data storage mechanism
• The Class diagram lacks specification on how different kinds of wastes will be given points, we thought of adding a "Waste" class that contains information about the types of the wastes, (the previous 2 points can be merged into storing the savings as members of waste class that are saved)
• Requirement 3.1.3 has a use case diagram but no specification on functionality, and isn't on class diagram
• Requirement 3.3.3: profiles and waste reduction statistics should be connected to the data storage mechanism in the updated class diagram
• Requirement 3.4.3: reporting functionality will be handled as a user-accessible report function of the "Challenges" class
• Requirement 4.3.2: similar to the previous point, "Post" class will have a report function

• Başar will handle combining the use case diagrams and transfer the result to the wiki.
• The next meeting will be held this Tuesday, where we expect the participation of everyone.