REQUIREMENTS

1. Functional Requirements

1.1 Registration and Profile Requirements

1.1.1 Sign-Up

• 1.1.1.1 Users shall be able to sign up by providing their email address and creating a password.
• 1.1.1.2 Users shall be required to verify their email address before activating their account.
• 1.1.1.3 Users shall be able to provide their full name during registration.
• 1.1.1.4 Users shall be able to provide their phone number during registration.
• 1.1.1.5 Users shall be required to accept the terms and conditions during registration.

1.1.2 Personal Information

• 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 Health Information

• 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 Location Information

• 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 Privacy and Security

• 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.

1.2 Availability and Help Assignment Requirements

1.2.1 Availability Management

• 1.2.1.1 Users shall be able to declare their availability to provide help by activating an “Available to Help” status.
• 1.2.1.2 Users shall be able to deactivate their availability status at any time.

1.2.2 Offline Support and Synchronization

• 1.2.2.1 The system shall store changes to availability status locally when internet connectivity is unavailable.
• 1.2.2.2 The system shall synchronize locally stored availability status updates automatically when internet connectivity is restored.
• 1.2.2.3 Users shall be able to create a help request while offline.
• 1.2.2.4 Users shall be able to choose their need type creating their help request.
• 1.2.2.5 Users shall be able to enter a short description for their help request.
• 1.2.2.6 The system shall warn users when critical request info is missing (e.g., location or need type), yet proceeding with defaults.
• 1.2.2.7 The system shall store help requests locally until connectivity is available.
• 1.2.2.8 The system shall synchronize pending help requests automatically when connectivity returns.
• 1.2.2.9 The system shall match help requests when connectivity returns, using the automatic assignment and matching process defined in Section 1.2.3.

1.2.3 Automatic Assignment and Matching

• 1.2.3.1 The system shall automatically evaluate active help requests for assignment to available users.
• 1.2.3.2 The system shall assign help requests to available users based on declared skills and urgency level of the request.
• 1.2.3.3 The system shall assign a help request only if the user’s declared skills match the required skill category of the request.
• 1.2.3.4 The system shall display the request status (Pending Sync / Synced / Matched / Resolved).