MVP Demo Plan

DEMO STRUCTURE

The demo is structured to demonstrate how the NEPH platform enables interaction between users who need help and users who are available to provide assistance. The flow is designed around a realistic emergency scenario and includes both mobile and web interfaces.

The demo consists of three main parts:

1. Web – Information and Profile Interface
2. Mobile – Helper Availability
3. Mobile – Request Creation and Matching

USER SCENARIOS

Scenario 1: Web Interface Usage and Visualization

• A web user is already logged into the system.
• The user can view and edit their profile information.
• On the home page, the user can access announcements, important updates, and emergency contact numbers.
• This part of the demo highlights that the web platform serves as an information and management interface, complementing the mobile application where core interactions (availability and request creation) take place.

Scenario 2: Helper Becomes Available (Mobile)

• A Doctor user is already logged into the mobile application.
• The doctor activates the “Available to Help” feature from the home page.
• The system updates the doctor’s availability status.

Scenario 3: User Creates a Help Request (Mobile)

• A Requester user is already logged into the mobile app.
• The user presses the "Request Help" button.
• User fills in the request help form.
• The user submits a help request.
• The request is successfully created and becomes active.
• The system automatically matches the request with an available helper (e.g., a doctor who is marked as “Available to Help”).
• The user can view available helpers information.

SCRIPT

0:00 – 2:30 (Kagan): Scenario 1: Introduction + Web Interface

• Introduces the NEPH platform and its purpose.
• Starts the demo already logged into the web.
• Navigates to the home page and highlights announcements and emergency contact numbers.
• Shows profile editing functionality.
• Explains that the web platform is mainly used for information and profile management.

2:30 – 4:00 (Rojhat): Scenario 2 – Helper Becomes Available (Mobile)

• Switches to the mobile application (doctor user already logged in).
• Navigates to the home screen.
• Activates the “Available to Help” button.
• Explains that this action makes the doctor visible to the system for incoming requests.

4:00 – 6:30 (Alper): Scenario 3 – User Creates a Help Request (Mobile)

• Switches to the requester user.
• Presses the “Request Help” button from the home page.
• Submits a help request (e.g., medical assistance).
• Explains that the request becomes active in the system.
• Shows that available helper information can be viewed.

6:30– 8:00 (Berat): Matching Logic Explanation

• Explains how the system matches the request with an available helper.
• Emphasizes that the doctor marked as “Available” is selected.
• Highlights that availability directly affects matching logic.

DEMO DATA STRATEGY

User Roles

We created three users to support our demo scenario:

• Doctor User (Dr. Ayşe Yılmaz): A helper who is marked as “Available to Help”.
• Requester User (Mehmet Kaya): A user who creates a help request.
• Web User (Nil Peri): A user who accesses the system via the web interface for profile management and information viewing.

Pre-populated State

• Dr. Ayşe Yılmaz is already logged into the system and marked as “Available to Help” before the demo begins.
• Mehmet Kaya is already authenticated on the mobile application to quickly create a help request.
• Nil Peri is already logged into the web interface to demonstrate profile editing and access to announcements and emergency contact numbers.

This setup allows us to avoid time spent on login and ensures a smooth demo flow.

Request and Matching Setup

• When Mehmet Kaya creates a help request, the system immediately matches the request with Dr. Ayşe Yılmaz, who is already available.
• This demonstrates how availability directly affects the matching process.
• The requester can view basic helper information such as role and availability status.

ROLE ASSIGNMENTS

• Kağan Can – Presenter (Introduction and Web Interface)
• Rojhat Delibaş – Presenter (Helper Availability – Mobile)
• Alper Kartkaya – Presenter (Request Creation – Mobile)
• Berat Sayın – Presenter (Matching Logic Explanation)
• Ethem – Runs the application during the demo
• Mehmet Can Gürbüz – Observer (monitors audience reactions and takes notes)
• Gülce Tahtasız – Timekeeper