Iteration Plan week 3 - Sidduri2025/RehabEdge GitHub Wiki
Project: RehabEdge – Remote Physical Therapy with Edge AI
1. What tasks from the previous iteration plan did not get completed?
All tasks from the previous iteration were completed successfully. The full user flow—including user registration, login, forgot password, OTP verification, and reset password—was implemented and tested. Authentication middleware was applied to all protected backend routes, and duplicate and demo controller directories were completely cleaned up.
2. Why did they not get completed?
Not applicable, as all tasks from the previous iteration were completed.
3. Which tasks from the previous iteration plan were moved to this current plan?
No tasks were carried forward from the previous iteration. The current iteration focused on new functionality.
4. Tasks planned for the current iteration (Doctor Dashboard)
The focus of this iteration was to design and implement the Doctor Dashboard. This dashboard allows doctors to securely log in, view assigned patients, check appointment details, and access patient-related information required for therapy management.
5. Assignment of tasks and plan for verification
| Student Name | Task Assigned | Verification Method |
|---|---|---|
| Akshara | Develop backend APIs to support Doctor Dashboard features such as patient and appointment data; handle database queries efficiently for fetching and updating patient and appointment information | API endpoints returned correct data when tested using Postman; database queries returned expected results and updates were correctly reflected |
| Pranetha | Design and implement the Doctor Dashboard user interface and page routing | Doctor Dashboard page loaded correctly with proper layout and navigation |
| Sidduri | Connect the Doctor Dashboard user interface with backend APIs | Dashboard displayed correct patient and appointment data from the backend |
| Chaithanya | Design and implement the login interface, connect it with backend authentication APIs, and ensure page routing works correctly after login | Login page authenticated users successfully, backend APIs were called correctly, and users were redirected to the appropriate dashboard |
6. Concrete plan for demonstrating task completion
A live demonstration was conducted showing a doctor user logging into the system using the login interface. After successful authentication, the user was redirected to the Doctor Dashboard. Patient and appointment details were displayed correctly. GitHub commit history was reviewed to confirm task completion by each group member, followed by a short walkthrough explaining the dashboard features and login flow.