Lab 3 Report

Lab 2 Report (26/02/2026)

---

Wiki Pages for Use Case Diagrams

• Diagram 1 : Scenario 1 Diagram
• Diagram 2 : Scenario 2 Diagram
• Diagram 3 : Scenario 3 Diagram

---

Individual Contributions

Berat Sayın – Alper Kartkaya

• Analyzed the predefined Account & Health Profile scenario and mapped it into structured system behavior.
• Identified core functional components related to account creation, profile completion, health data entry, and privacy configuration.
• Modeled user interactions and system responsibilities through a comprehensive Use Case Diagram.
• Defined relationships between use cases (include / extend) to reflect mandatory and conditional system behavior.
• Structured external actor interaction (Email Service) for email verification flow.
• Ensured consistency between the scenario narrative and UML modeling.
• Participated in diagram refinement and peer review discussions for alignment with overall system architecture.

Ethem Erinç Cengiz – Kağan Can – Mehmet Can Gürbüz

• Analyzed the help request lifecycle within an offline-first PWA architecture.
• Modeled the complete request creation flow, including location provision, request form completion, validation, and submission behavior.
• Structured offline handling logic by modeling local request storage and deferred synchronization mechanisms.
• Designed synchronization behavior (“Sync Pending Requests when online”) and its interaction with automatic assignment logic.
• Modeled automatic helper assignment based on need type, proximity, and availability as a system-driven process.
• Defined notification behavior as a mandatory outcome of the assignment process using «include» relationships.
• Integrated device-level and external actors (Device Location Service, Network Connectivity) into the system boundary to reflect real-world dependencies.
• Modeled periodic background location updates and last-known-location usage for offline compatibility.
• Structured resident-side and helper-side interactions separately (request tracking, availability management, skill updates).
• Refined include/extend relationships to distinguish between mandatory flows (assignment, validation, notification) and conditional behaviors (location usage, cancellation).
• Ensured alignment between offline-first design principles, automatic matching logic, and system-level requirements.
• Participated in diagram review and structural refinement to maintain consistency with other scenarios.

Rojhat Delibaş – Gülce Tahtasız

• Analyzed the predefined help request lifecycle scenario and formalized the interaction between Requester and Volunteer roles.
• Modeled the end-to-end request handling process, including request creation, automatic matching, and assignment notification.
• Structured system-driven processes (Auto Match & Assign, Assignment Notification) separately from user-initiated actions.
• Designed conditional behavior for availability synchronization using «extend» to reflect online-dependent logic.
• Modeled volunteer-side request management, including viewing assigned requests, accepting or rejecting assignments.
• Defined status transition logic (In Progress / Resolved) and represented mandatory system updates using «include» relationships.
• Ensured proper separation between user-triggered use cases and internal system processes in accordance with UML standards.
• Refined use case relationships (include / extend) to accurately reflect mandatory vs. conditional behavior.
• Participated in diagram review and consistency checks to align the flow with overall system requirements.