Lab 3 Report ‐ 26.02.2026

Lab 3 Report

Wiki Pages for Use Case Diagrams

• Use Case Diagram for Scenerio 1 ‐ Sub‐group 2
• Use Case Diagram for Scenerio 2 ‐ Sub‐group 3
• Use Case Diagram for Scenerio 3 ‐ Sub‐group 1

Individual Contributions

Sub-group 1: Berat Sayın – Alper Kartkaya

• Analyzed the Account & Health Profile scenario.
• Identified main functional components such as account creation, profile completion, health data entry, and privacy settings.
• Created the Use Case Diagram for this scenario.
• Used «include» and «extend» relationships where necessary.
• Modeled the interaction with the Email Service for verification.
• Identified ambiguities in the scenario (mandatory vs. optional profile fields, privacy configuration timing, emergency-only visibility rules, and update permissions).
• Documented design assumptions regarding connectivity requirements, minimum registration fields, optional live location sharing, and external email verification.
• Participated in peer review and diagram improvements.

Sub-group 2: Ethem Erinç Cengiz – Kağan Can – Mehmet Can Gürbüz

• Analyzed the help request and automatic assignment scenario.
• Modeled the request creation and matching process.
• Represented offline behavior (saving locally and syncing when online).
• Included external actors such as Device Location Service and Network.
• Modeled automatic assignment and notification as system actions.
• Revised include/extend relationships based on scenario assumptions.
• Identified ambiguities in the scenario (offline handling, cancellation, location updates, status lifecycle, notification logic) and explicitly documented corresponding design assumptions.
• Defined assumptions regarding cancellation flow, periodic location updates, automatic notifications, and internal status transitions.
• Participated in peer review and diagram improvements.

Sub-group 3: Rojhat Delibaş – Gülce Tahtasız

• Analyzed the volunteer-side request handling process.
• Modeled viewing, accepting, and rejecting assigned requests.
• Represented status updates (In Progress / Resolved).
• Modeled availability declaration and synchronization.
• Refined use case relationships to match the scenario logic.
• Identified ambiguities in the scenario related to assignment notifications, volunteer interaction flow, and request lifecycle.
• Documented corresponding design assumptions to clarify status transitions and interaction behavior.
• Participated in peer review and diagram improvements.

---