19 02 2026 ‐ Lab02 Report

Lab 2 Report (19/02/2026)

---

Wiki Pages for Scenarios & Mock-ups

• Scenario 1: Injured Neighbor
• Scenario 2: Volunteer Users Help Offer
• Scenario 3: User Registration and Profile Setup

---

Link to Requirements Wiki Page

• Requirements Wiki Page

---

Individual Contributions

Berat Sayın – Alper Kartkaya

• Developed the scenario1: “Injured Neighbor”

• Defined the user persona, including profile details, goals, and pre-conditions.

• Structured the offline-first request creation flow and defined draft handling behavior.

• Identified and formalized functional requirements derived from the scenario (1.1–1.8).

• Defined automatic synchronization and status tracking behavior (Pending Sync / Synced / Matched / Resolved).

• Designed the mock-up for:

  • Help Request Creation screen
  • Offline save confirmation
  • Request status display

• Ensured alignment between scenario flow, offline handling logic, and SRS requirements.

• Participated in peer review and refinement discussions for consistency across scenarios.

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

• Developed the scenario2: “Volunteer Users Help Offer”

• Defined the Doctor persona, including goals and pre-conditions.

• Structured and organized the “Availability and Help Assignment Requirements” section (1.2).

• Converted scenario outcomes into enumerated SRS-compliant functional requirements.

• Defined availability declaration, offline synchronization, and automatic assignment logic.

• Designed the main dashboard mock-up including:

  • “I Am Available to Help” toggle
  • Help status section
  • Profile summary layout.

• Ensured alignment between scenario steps, mock-ups, and functional requirements.

• Reviewed and refined requirement consistency across the SRS document.

Rojhat Delibaş – Gülce Tahtasız

• Developed the scenario3: “User Registration and Profile Setup.”

• Defined the user persona, including goals related to secure data storage and emergency visibility control.

• Structured the complete registration flow, including email verification and profile completion steps.

• Identified and formalized personal information, health information, and location requirements (1.1.2 – 1.1.5).

• Defined privacy configuration behavior, including emergency-only visibility of health data.

• Designed the mock-ups for:

  • Sign-Up screen
  • Profile information form
  • Privacy settings configuration page

• Ensured alignment between scenario flow, SRS structure, and privacy/security requirements.

• Participated in peer review and requirement refinement discussions across all scenarios.