Weekly Meeting #3 Report

Lab 3 – Weekly Meeting

Date: 04.03.2026
Time: 20:00 – 21:00

---

Participants

• Ali Akkaya ✅
• Bora Aydemir ✅
• Ömer Belemir Delier ✅
• Arif Evren ✅
• Ulaş Sertan Kemeç ✅
• Ekin Kılıç ✅
• Baran Önder ✅

---

Agenda

1. Review of the prototype application prepared voluntarily by Ali Akkaya.
2. Discussion on how the prototype can be extended and integrated into the project architecture.
3. Review of open GitHub issues and remaining tasks.
4. Discussion of elementary system classes for Prelab 4.
5. Sharing ideas and feedback regarding system design and class structure.

---

Discussion Items

Prototype Demonstration

Ali Akkaya voluntarily prepared a small prototype application demonstrating a basic structure of the Neighborhood Accessibility Mapper system. The team reviewed the prototype and discussed how its components could evolve into a more complete implementation. Particular attention was given to how the prototype reflects the main system workflows such as map interaction and obstacle reporting.

System Development Direction

Based on the prototype, the team discussed possible directions for extending the system. Ideas were shared regarding improving modularity, separating services logically, and structuring the system so that future features (such as advanced routing or indoor navigation) can be integrated smoothly.

Issue Review

The team reviewed the remaining GitHub issues related to the project repository. Existing tasks were revisited and clarified, and feedback was provided on how to resolve open issues. This helped ensure that the team maintains progress toward the next deliverables.

Elementary Class Discussion (Prelab 4)

The team discussed the key classes required to represent the system’s main functionality. Different ideas were shared regarding the responsibilities of classes such as User, ObstacleReport, Route, and MobilityProfile. The discussion focused on identifying essential attributes and methods while keeping the design simple at this early stage.

Design Feedback and Collaboration

All team members shared their opinions regarding the preliminary class design and how it relates to the previously defined scenarios and requirements. The discussion helped ensure consistency between the system’s conceptual design, use cases, and the emerging class structure.

---

Action Steps

• Ali Akkaya: Share the prototype application and participate in reviewing the proposed class structure.
• Ömer Belemir Delier: Document the meeting discussion and contribute feedback on the class diagram design.
• Bora Aydemir: Revisit the identified system classes and provide suggestions for improving their relationships.
• Baran Önder: Review the class structure and ensure consistency with the previously defined scenarios.
• Ulaş Sertan Kemeç: Examine the class diagram and provide feedback on the organization of the system components.
• Ekin Kılıç: Review terminology and concepts used in the class design to ensure clarity in the documentation.
• Arif Evren: Review elementary classes and contribute feedback on the class diagram.