-
Notifications
You must be signed in to change notification settings - Fork 1
Scenario 3: User Registration and Profile Setup
Gülce Tahtasız edited this page Feb 25, 2026
·
9 revisions
![]() |
Rena Çayır Resident / Community Member Female Lives in the neighborhood Wants to get help fast during an emergency Has limited internet access during disasters |
- Wants to create an account in the system
- Wants to securely store her personal and health information
- Wants to update her physical and medical data when necessary
- Wants to control who can see her information
- Wants her health data to be visible only during emergencies
- Wants her location to be stored for emergency matching
Pre-Conditions
- The PWA is installed and accessible
- The user has internet connectivity during initial registration
- The system database is operational
- The user has a valid email address and telephone number
- Opens the application
- Selects Sign-Up
- Enters email and creates password
- Provides full name and phone number
- Accepts terms and conditions
- Verifies email via confirmation link
- Completes profile setup:
- Enters height and weight
- Provides date of birth
- Selects gender (optional)
- Enters medical history
- Specifies chronic diseases (if any)
- Specifies allergies (if any)
- Provides country and city
- Optionally enables current location sharing
- Configures privacy settings:
- Chooses which data is public
- Sets health data visibility to emergency-only
- Saves profile
- The system securely stores the information
- User can later edit profile or delete account
- 1.1.2.1 Users shall be able to enter their height and weight during registration.
- 1.1.2.2 Users shall be able to provide their date of birth.
- 1.1.2.3 Users shall be able to provide their gender (optional).
- 1.1.2.4 Users shall be able to update their physical information after registration.
- 1.1.3.1 Users shall be able to enter their medical history during registration.
- 1.1.3.2 Users shall be able to specify chronic diseases (if any).
- 1.1.3.3 Users shall be able to specify allergies (if any).
- 1.1.3.4 Users shall be able to update their health information at any time.
- 1.1.3.5 Users shall be able to choose whether their health information is visible to other users or remains private.
- 1.1.4.1 Users shall be able to provide their country and city.
- 1.1.4.2 Users shall be able to share their current location (optional).
- 1.1.4.3 Users shall be able to update their location information.
- 1.1.5.1 Users shall be able to control which personal information is publicly visible.
- 1.1.5.2 The system shall securely store all personal and health-related data.
- 1.1.5.3 The system shall encrypt sensitive user information.
- 1.1.5.4 Users shall be able to delete their account and associated personal data.
🎓 Team Members
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (25.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (18.03.2026)
- Weekly Meeting 6 (25.03.2026)
- Weekly Meeting 7 (01.04.2026)
- Weekly Meeting 8 (08.04.2026)
- Weekly Meeting 9 (15.04.2026)
- Weekly Meeting 10 (29.04.2026)
- Weekly Meeting 11 (06.05.2026)
- Weekly Meeting 12 (13.05.2026)
- 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 (16/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Scenario 1: Injured Neighbor
- Scenario 2: Volunteer Users Help Offer
- Scenario 3: User Registration and Profile Setup
- Use Case Diagram (Final)
- 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
- Sequence Diagram - Alper Kartkaya
- Sequence Diagram - Kağan Can
- Sequence Diagram - Mehmet Can Gürbüz
- Sequence Diagram - Ethem Erinç Cengiz
- Sequence Diagram - Berat Sayın
- Sequence Diagram - Gülce Tahtasız
- Sequence Diagram - Rojhat Delibaş
