-
Notifications
You must be signed in to change notification settings - Fork 0
Customer Meeting 1
muhammetsami edited this page Feb 19, 2026
·
2 revisions
Date
- 19/02/2026
Time
- 10:30
Via
- Online
| Member | Participation |
|---|---|
| Amin Abu-Hilga | ✓ |
| Övgü Su Afşar | ✓ |
| Halis Tunay Aslan | |
| Muhammet Sami Çakmak | ✓ |
| Beratcan Doğan | ✓ |
| İbrahim Kayan | ✓ |
| Burak Öğüt | ✓ |
| Mehmet Bora Sarıoğlu | ✓ |
- There are no strict usage restrictions or predefined user classifications at this stage.
- Both mentors and mentees will complete a survey to create their profiles.
- Self-registration will be supported and email verification will be required.
- Mentors will define their own available time intervals; mentees can request meetings accordingly. Scheduling is nice-to-have.
- The platform should be responsive and easy to use. Design standards will be discussed next week.
- The system will not manually verify how many mentees a mentor has; reliability will be determined automatically. Rating is possible but not preferred. Bookmarking was mentioned.
- When a mentor and mentee are matched, a defined workflow will be created. Progress will be tracked and images may be shared to show development.
- Users will have levels based on participation in workflows and meetings. Mentors can receive comments.
- No punishment mechanism; positive progress may be rewarded.
- A recommendation-based matching algorithm will be used. A priority mechanism may be added later. Users can define their own conditions. Example mentee profiles may be shown.
- Built-in messaging and peer-to-peer communication are nice-to-have but not first priority; they should still be considered in the design.
- Meeting structure should include automatic notifications. Notification messages are nice-to-have. A Moodle-like meeting structure was referenced.
- Goal management does not have to be visible in the first version.
- The system should be able to send alerts to the admin when necessary.
Team Members
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (18/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting Notes Template
- Lab Meeting 1 (12.02.2026)
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (24.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (23.03.2026)
- Weekly Meeting 6 (29.03.2026)
- Weekly Meeting 7 (11.04.2026)
- Weekly Meeting 8 (28.04.2026)
- Weekly Meeting 9 (10.05.2026)
- Use Case Diagram 1 (New Mentor User for Mobile Scenario)
- Use Case Diagram 2 (Mentor-Mentee Matching Scenario)
- Use Case Diagram 3 (New Mentee User Scenario)
- Final Use Case Diagram
- MVP Use Case Diagram
- All Sequence Diagrams
- Sequence Diagram: Mentee Matching
- Sequence Diagram: Mentor Matching
- Sequence Diagram: Mentorship Management
- Sequence Diagram: Registration
- Sequence Diagram: Cancelling Mentorship Relationship and Auto Ban
- Sequence Diagram: Login-Logout
- Sequence Diagram: Reporting-User
- Sequence Diagram: Mentor Profile Management
- MVP Sequence Diagrams
- Test Plan & Coverage (MVP)
- Acceptance Testing Strategy
- Acceptance Tests
- Test Data Strategy
- Web Frontend Test Report
- Amin Abu-Hilga
- Övgü Su Afşar
- Muhammet Sami Çakmak
- Beratcan Doğan
- İbrahim Kayan
- Burak Ögüt
- Mehmet Bora Sarıoğlu
- Future Work (reference, not a deliverable)