FINAL PROJECT: Software MVP

1. Product Overview

TL;DR

DoseMate is a mobile app that helps adults managing chronic conditions stay consistent with their medications through smart reminders, simple medication tracking, and accessible education about side effects. It reduces stress, prevents missed doses, and builds medication confidence using adaptive notifications, progress tracking, and clear, plain-language guidance.

Repos

• Backend: DoseMate-backend
• Frontend: DoseMate-mobile

Jobs To Be Done (JTBD)

• Tracking
  As a patient managing multiple chronic conditions, I want to easily add and track my medications so I can follow my regimen with confidence and accuracy.
  Value: reduces errors, maintains clear medication history.

• Smart Reminders
  As a busy patient, I want adaptive reminders that fit around my lifestyle so I can stay consistent without feeling overwhelmed.
  Value: increases adherence, reduces missed doses.

• Education & Side-Effect Understanding
  As a patient concerned about side effects, I want clear explanations of my medications so I feel reassured and better understand their importance.
  Value: decreases anxiety, increases trust in care.

Core Customer User Journeys (CUJs)

• Account Creation – onboarding, profile setup, Google OAuth sign-in

• Easily Adding Medications – search, scan, confirm dosage, schedule reminders

• Understanding Medication Through Education – purpose, side-effects, plain-language info

• Staying on Track With Smart Reminders – adaptive alerts, snooze, tracking streaks

2. MVP Development Justification

Initial Hypothesis

Core problem: Adults with chronic conditions routinely miss medications due to schedule complexity, poor reminder tools, and anxiety about side effects.

Initial idea: A medication-tracking app with reminders and education cards.

Key assumptions:

• Users struggle with tracking schedules manually.

• Reminder fatigue causes ignored notifications.

• Users want very simple medication explanations.

• Users will adopt the app if onboarding is frictionless (OAuth, simple UI).

Key Learnings & Pivots

• Learning 1 (User Survey – 46–75 aged adults)
  75% miss doses weekly, 69% stop medications without consulting a doctor.
  Pivot: Invest heavily in reminders + adherence tracking dashboards.
• Learning 2
  21% fear side effects and 58% feel stressed managing meds.
  Pivot: Add medication education module + side-effect view.
• Learning 3
  Users value care-team visibility (90% want to share data).
  Pivot: Add adherence report sharing.
• Learning 4
  Users want fast onboarding and hate forms.
  Pivot: Add Google OAuth early to reduce friction.
• Learning 5
  Medication entry must be quick, and users want image upload or scan.
  Pivot: Integrate OpenFDA + camera upload for medication search.

Justification of Final MVP

Our final MVP includes:

• Account creation + Google OAuth → validates identity with low friction

• Medication search + scan + OpenFDA ingestion → directly addresses the biggest JTBD: easy tracking

• Plain-language education module → validated by user anxiety around side effects

• Smart reminders → supports adherence, preventing missed doses

• Adherence stats (daily/weekly/monthly) → reflects user desire for confidence and progress tracking

• These features form the smallest possible set that solves the verified needs: accuracy, confidence, stress reduction, and adherence.

3. Functional and Dynamic MVP

Core Functionality

Our MVP delivers an end-to-end, working version of DoseMate across a Python/FastAPI backend and a React Native (Expo) mobile client. In its current state, users can:

1. Account & Profile

• Sign up using email/password or Google OAuth.
• Review and accept a privacy notice before proceeding into the main app.
• Personalize their profile by entering age, conditions, allergies, and lifestyle factors.

2. Medication Management

• Search for medications by name using an autocomplete search connected to a medication API.
• Use camera-based recognition of medication packaging to pre-fill medication information.
• View a list of matching medications and select the correct one.
• Confirm dosage details: strength and quantity.
• Configure a schedule: times of day, days of the week, PRN (“as needed”) vs recurring schedules.
• Save medications to the user’s profile, with a persistent history of active medications.

3. Education & Side Effect Tracking

• See a plain-language medication overview pulled from OpenAI API.
• View side-effect information separated into common vs serious effects.
• See tips and “seek help” markers that flag when the user should contact a provider or go to emergency care.

4. Smart Reminders / Adherence

• Receive push notifications that include medication name, dosage, and key instructions at scheduled times.
• From the notification or in-app reminders, tap “Taken” or “Snooze” for each dose.
• Use adaptive reminders that adjust based on time (and optionally snooze behaviour) to better match real routines.

5. Adherence Tracking & Reporting

• View an adherence tracking dashboard with summaries of doses taken vs scheduled.
• See streaks and basic progress indicators to positively reinforce consistent use.
• Generate adherence summaries that can be shared with caregivers or providers (via PDF).

Dynamic vs. Static Content

Dynamic (backed by real data and logic)

• Account & profile: email + Google auth flows, privacy notice gating, and profile storage (age, conditions, allergies, lifestyle).
• Medication search and selection: autocomplete search against a medication API, listing matches, and saving selected medications to the user’s profile.
• Camera-based packaging scan: triggers real logic and data flow.
• Medication schedule: saving times, days, and PRN/recurring patterns to the backend and using them to compute upcoming doses.
• Medication details & education: fetching and displaying overview, side effects, and “seek help” markers from the backend/medication service.
• Reminders: creating reminder schedules, triggering notifications, and updating state when users tap “Taken” or “Snooze”.
• Adherence logging: persisting “taken” events, updating adherence stats, and reflecting them in the dashboard view.
• Caregiver/provider report generation: using real adherence data (PDF/email export).

Static / Semi-Static (scaffolded or partially implemented)

• There are no core CUJs implemented as static mockups; all primary user journeys (account creation, medication setup, viewing details, receiving reminders, logging doses, and viewing adherence) are fully dynamic and integrated with backend services.

4. Test Coverage

Code Coverage

Backend

• Backend coverage is measured using pytest and the coverage plugin.
  pytest --cov=app --cov-report=term-missing --cov-report=xml
• At the time of the final release, our backend test suite achieves 66%, which exceeds the course requirement of ≥65% coverage.

Frontend

• For the mobile app, Jest’s coverage reporting is enabled.
  npm test -- --coverage
• At the time of the final release, our frontend test suite achieves 71%, which exceeds the course requirement of ≥65% coverage.

CI and Coverage Reporting

We use GitHub Actions as our CI pipeline to enforce tests and coverage on every push and pull request to the main branch:

The CI workflow

1. Checks out the repository.
2. Installs backend and frontend dependencies.
3. Runs database migrations or sets up a test database.
4. Executes:

• Backend tests with coverage: pytest --cov=app --cov-report=term-missing --cov-report=xml
• Frontend tests with coverage: npm test -- --coverage

The pipeline

• Fails the build if tests fail.
• Generates a coverage.xml report for the backend (and Jest coverage for the frontend) that is stored as a CI artifact and uploaded.

Example CI run with coverage report

• Backend: Successful CI Run

• 

• Frontend: Successful CI Run

• 

5. Demo

dosemate.demo.mp4

Key Features to Test

User Login

• Google OAuth
• Email login

Onboarding Flow

• Privacy & security terms
• Patient info: age, conditions, allergies, sleep schedule, activity levels

Medicine Management

• Add medicine via:
  • Text search
  • Manual entry
  • Image/OCR upload (work-in-progress)
• Fill out dosage, frequency, and customizable days
• Verify scheduled reminders appear at the correct time

Reminders

• Standard reminders with “Taken” and “Snooze” options
• Smart/adaptive reminders that adjust based on user patterns

In-App Medicine Education

• Open a scheduled medicine to view:
  • Overview
  • Side effects
  • Interactions

Progress Tracking

• Dashboard showing:
  • Taken vs missed doses
  • Adherence percentage
  • Recent activity
• Ability to set adherence targets

Report Generation

• Weekly and monthly adherence reports
• Export-ready summaries for patients and healthcare providers

Highlights of Our Work

• Built a full medication scheduling system with flexible dose and frequency options
• Designed a user-centric onboarding flow to personalize reminders
• Implemented early-stage OCR for image-to-text medicine ...

General Functionality and Future Scope + User Research

Deliverables

• Slide Deck (Figma)

PRs

• Store profile data (Frontend)
• Store profile data (Backend)
• Medication Education API (Backend)
• Display Medication Education (Frontend)

---

Roadmap Update

Since the last release (v1.0.10), the DoseMate team focused on strengthening and integrating the core medication workflow built across previous assignments. This release (v1.0.11) finalizes major end-to-end functionality: Google OAuth login, onboarding, medicine input via search and OCR, medicine display, scheduling and reminders, progress tracking, dashboard insights, and medication education content.

Our goal was to ensure that every part of the user journey—from account creation to daily reminder notifications—works consistently, reliably, and intuitively.

The team also prepared the foundation for upcoming premium enhancements, including exporting reports, adaptive reminders, robust testing, and healthcare professional support.

---

Summary of Changes

Frontend

• Implemented Google OAuth login and improved onboarding flow.
• Added medicine search and OCR-based extraction for fast, low-effort input.
• Built medicine display screens with details and adherence history.
• Added scheduling UI for dosage times, frequencies, and instructions.
• Integrated functional reminder notifications (frontend ↔ backend).
• Developed progress tracking (daily/weekly adherence views).
• Redesigned dashboard with today’s schedule + adherence summaries.
• Added medication education content cards for improved safety and understanding.

Backend

• Finalized Google OAuth verification and secure user authentication.
• Added APIs for medicine search, OCR ingestion, and user-specific storage.
• Implemented reminder scheduling API and connected it to notification systems.
• Added dose tracking endpoints for actions (taken, missed, snoozed).
• Expanded education content generation (static + dynamic modules).
• Improved error handling, schema reliability, and concurrency support.

---

Roadmap Change Details

UI/UX

• Streamlined the onboarding flow for clarity and speed.
• Simplified OCR confirmation and medicine input flow.
• Updated dashboard hierarchy with a clear “Today’s Overview” section.
• Improved readability and segmentation of education cards.
• Enhanced accessibility (contrast, spacing, typography).

Backend Architecture

• Final OAuth authentication pipeline implemented.
• Modularized medicine ingestion (search + OCR).
• Added /schedule, /tracking, and /notifications endpoints.
• Strengthened async job scheduling for reminders.
• Prepared backend modules for premium features (analytics, exporting).

Research & Decisions Log

A lightweight CUJ was conducted with a classmate and family member(s) to test onboarding, OCR flow, and dashboard usability.

Findings:

• OCR significantly reduced manual typing.
• Users wanted all reminders visible from the dashboard.
• Education cards increased confidence in medication usage.

Actions:

• Added unified dashboard reminder section.
• Simplified OCR edit/confirmation step.
• Expanded education card content (side effects, usage guidelines).

Decisions:

• Prioritize reliability and user clarity before premium features.
• Retain dynamic education content generation modules.
• Continue refining reminder and tracking logic via user testing.

---

Milestone Update

✅ Completed

• Google OAuth login + onboarding
• Medicine search & OCR
• Medicine display + details
• Scheduling + reminders
• Functional notification system
• Dashboard summary interface
• Medication education content
• Progress tracking base features

🔄 In Progress

• UI/UX refinement based on CUJ findings
• Backend cleanup and optimization

🔜 Next Milestones

• Premium features:
  • Exporting reports
  • Adaptive reminders
  • Clinician support tools
• Robust automated testing
• Expanded adherence analytics and insights

---

Roadmap Adjustments

Short-Term

• Improve reminder accuracy + timezone/sleep edge-case handling.
• Polish onboarding-to-first-medicine flow.
• Add analytics to track usage of reminders and education cards.
• Prepare UI for premium features.

Long-Term

• Implement report exporting + adherence summaries.
• Introduce adaptive reminders for smarter medication management.
• Enable optional healthcare professional management features.
• Strengthen end-to-end and reliability testing.

Technical Problem Solving + User Research

Deliverables

• Slide Deck

Overview

This release (v1.0.10) builds on v1.0.9 with major improvements to medication education and user reminder workflows. Key updates include:

• GPT-powered Medication Education Cards
• Personalized Reminder Management

These updates enhance the user experience and support our core Jobs To Be Done (JTBD) goals.

Summary of Changes

Frontend

• Added Medication Education Cards generated via GPT
  • PR #19
• Implemented Reminder Management UI (create, edit, track reminders)
  • PR #20
• Updated navigation for seamless access to new features
• Added unit tests for education cards and reminder components

Backend

• Added GPT-powered Content API for dynamic medication education cards
• Implemented Reminder Scheduling API with database persistence
• Added backend tests for content generation and reminder logic
• Improved error handling and logging across new endpoints

UI/UX Improvements

• Redesigned medication details view with interactive education cards
• Added streamlined reminder creation and management interface
• Improved visual hierarchy and accessibility

Backend Architecture Updates

• Added /medication/details endpoint with GPT integration
• Implemented /reminders endpoints for CRUD and scheduling
• Updated database schema to support user-specific reminders
• Enhanced async and concurrency handling

Research & Decisions Log

• Conducted lightweight CUJ testing with two classmates
• Findings:
  • Users preferred concise, segmented education cards
  • Users appreciated centralized reminder management
• Actions Taken:
  • Simplified card layout for readability
  • Added summary view for upcoming reminders
• Decision: Continue GPT-based education content while optimizing API calls

Milestones

• GPT-powered Medication Education Cards
• Reminder creation and management
• Updated frontend and backend tests
• UI/UX refinements based on early feedback
• Next: Push notification support
• Next: Analytics for education card engagement

Short-Term Roadmap

• Optimize GPT content generation for speed and consistency
• Implement push notifications for reminders
• Conduct additional CUJ testing for educational clarity and workflow validation
• Enhance UI/UX polish for all new features

Competitive CUJ

Overview of This Release

Added Assignment 7 - Competitve CUJ Document

• Assignment 7 - Competitive CUJ.pdf

Progress & Assignment Contents

Since our last release, our team has completed Assignment 7 – Competitive CUJ, which focuses on analyzing a competitor (Medisafe) and evaluating its medicine reminder customer-use-journey. Our team examined Medisafe’s onboarding flow, medication-input experience, reminder reliability, and overall usability. We documented strengths such as accurate reminders and a strong drug database, along with weaknesses including intrusive ads, cluttered interface, and limited free-tier functionality.
We also produced a full end-to-end CUJ walkthrough, highlights/lowlights table, competitor comparison, and product recommendations for DoseMate.

Roadmap / Architecture / Use Case Changes

No major changes to DoseMate’s architecture or feature roadmap occurred during this release.
This assignment contributed research insights but did not alter existing system design.

Issue Summary

No major issues were encountered during this release.
The CUJ evaluation and documentation proceeded smoothly.

Testing Infrastructure Setup and Add Medicine Functionality

Direct Links

Presentation Deck

Backend

• GitHub Repository: DoseMate-backend
• Pull Request: Update README with full quick setup instructions — #5
• Pull Request: add unit test and coverage test, making full coverage 86% — #6
• Pull Request: Add medicine api call— #7

Submitted Files

• README.md
• tests/test_models.py
• tests/conftest.py
• app/db/models.py
• app/main.py

Frontend

• GitHub Repository: DoseMate-mobile
• Pull Request: Frontend UI Implementation — #3
• Pull Request: Ci and setting up GitHub Actions checks — #4
• Pull Request: Frontend testing using Jest — #5
• Pull Request: updated CI workflows + added check to tests passing — #8
• Pull Request: Add medication search — #10

Submitted Files

• .github/workflows/code_quality_check.yml
• .github/workflows/unit_tests_check.yml
• dosemate/tests/OnboardingStart.test.tsx
• dosemate/tests/onboarding/CreateAccount.test.tsx
• dosemate/tests/onboarding/PrivacyScreen.test.tsx
• dosemate/tests/onboarding/ProfileSetupScreen.test.tsx
• dosemate/tests/onboarding/TutorialScreen.test.tsx
• dosemate/tests/MainNavigationScreen.test.tsx
• dosemate/components/main-navigation/AddMedicationScreen.tsx
• dosemate/components/main-navigation/MedicationList.tsx
• dosemate/components/main-navigation/OCR.tsx

---

Roadmap Update

Since the last release (v1.0.7), the DoseMate team has expanded the app’s functionality and strengthened the testing infrastructure.
This release (v1.0.8) focuses on adding medicine management features and configuring testing pipelines for both frontend and backend.
We’ve integrated OpenFDA APIs for medicine data retrieval, implemented search and image upload capabilities, and configured Jest for test automation.

Summary of changes:
On the Frontend:

• Added the Add Medicine feature to search for medications through APIs or by uploading images (camera/gallery).
• Integrated calls to /autocomplete and /medicine/search APIs to fetch and display relevant medicine data.
• Implemented OpenFDA integration for retrieving medicine information.
• Configured Jest testing framework, enabling lint, type check, and format validation.
• Added unit and coverage tests for all core screens to ensure UI stability.

On the Backend:

• Added new backend routes for medicine search using OpenFDA API.
• Enhanced backend testing with expanded unit and integration coverage (now at 86%).
• Improved database logic for dynamic medicine ingestion.
• Refined environment configuration and CORS handling to support new APIs.

---

Roadmap Change Details

UI/UX

🧩 Issue: #14, #7, #20

• Developed and integrated the Add Medicine feature on mobile.
• Implemented medicine search via API and image upload (camera/gallery).
• Enhanced accessibility and layout consistency across medication and onboarding flows.
• Added OpenFDA data display within medication search results.

Backend Architecture

🧩 Issue: #14, #9, #20, #40

This issue established the infrastructure and testing foundation for medication APIs and CI/CD integration:

• Added /medicine/search and /autocomplete routes calling OpenFDA API.
• Improved async handling and error management in API layer.
• Expanded backend unit and integration test coverage to 86%.
• Integrated test utilities into CI workflow for automated coverage tracking.
• Implemented Jest and type-checking pipelines on frontend for unified testing.

---

Milestone Update

• ✅ Add Medicine API and UI completed.
• ✅ Jest testing configured and integrated into CI/CD.
• ✅ Backend test coverage increased to 86%.
• 🔄 Refining camera-based medicine recognition, create a medicines table in the database for tracking
• 🔜 Next milestone: Implement push notifications and reminder scheduling.

---

Roadmap Adjustments

Short-term:

• Improve image-based medicine recognition.
• Add scheduling functionality for the added medicines.
• Add push notifications and dosage reminders.
• Enhance UI/UX theme (nice to have!)

Authentication Integration and Early API Setup

Direct Links

Backend

• GitHub Repository: DoseMate
• OAuth Implementation Branch (auth-setup)
• .env.template** — 21 changes (15 additions, 6 deletions)
• app/auth/routes_google.py** — 92 changes (92 additions)
• app/core/config.py** — 14 changes (9 additions, 5 deletions)
• app/main.py** — 5 changes (2 additions, 3 deletions)

Mobile

• GitHub Repository: DoseMate-mobile
• Pull Request: Integrating Google Authentication — #2
• dosemate/app.json — 6 changes (5 additions, 1 deletion)
• dosemate/app/onboarding/create-account.tsx — 43 changes (37 additions, 6 deletions)
• dosemate/package.json — 6 changes (4 additions, 2 deletions)
• dosemate/package-lock.json — 89 additions (auto-generated changes)

---

Roadmap Update

Since the last release (v1.0.6), the DoseMate team has made significant progress on both the backend and mobile sides of the application. This release (v1.0.7) centers on frontend+backend project initialization, UI prototype, and enabling secure user authentication using Google OAuth 2.0, laying the foundation for personalized user experiences. Our work this cycle was divided into two main areas — backend infrastructure and mobile integration — each addressing a distinct issue linked to this release.

Summary of changes:
On the Frontend:

• We have a React Native application set up with an appropriate README File. (We are building a cross-platform mobile app)
• We have created an onboarding flow that includes: signup/login page, profile, dashboard, and tutorial screens. We also created basic tabs for medications, reminders, and progress.
• After having a frontend prototype, we integrated the Google authentication to open the app via Gmail Account.

On the Backend:

• Initialized a FastAPI project and added a README file for instructions to run the server.
• Set up the Database connection (PostgreSQL) with SSL security and created a user model (CRUD), allowed CORS so the frontend from other URLS can access the backend.
• Added backend routes to handle Google login (OAuth).

---

Roadmap Change Details

UI/UX

🧩 Issue: #25, #4, #23

• Initialised a React Native App + Expo Go for testing
• We have designed and implemented a complete onboarding flow for users. This includes a signup and login page, a user profile page, a dashboard, and tutorial screens to guide new users through the app. In addition, we have created basic navigation tabs for core features such as medications, reminders, and progress tracking, providing a structured and easy-to-use interface.
• Once the frontend prototype was ready, we enhanced the app by integrating Google authentication. This allows users to log in or open the app using their Gmail account, simplifying the login process and improving user experience.

Backend Architecture

🧩 Issue: dcsil/DoseMate-backend#1, #26, #44

This issue consists of setting up async Postgres Engine, DB Initialization Scripts, and Test Utilities:

• Set up a secure async PostgreSQL database
• Add scripts to manage and test users
• Built a User model with CRUD functions
• Updated the app to auto-create tables with CORS support

Issue: dcsil/DoseMate-backend#2

This issue established the infrastructure and environment configuration required for Google authentication:

• Added Google OAuth credentials and redirect URIs in .env.template.
• Integrated OAuth libraries and dependencies within the backend environment.
• Defined endpoint structure for authentication and callback handling. The backend now communicates with Google’s OAuth 2.0 API using httpx, securely handling tokens and user information before issuing an internal JWT for the mobile client.

Milestone Update

• ✅ OAuth API endpoints complete.
• ✅ Mobile onboarding flow functional.
• 🔄 Creating and finalizing frontend mockups: #3
• 🔜 Next milestone: Setup minimal testing infastructure (frontend and backend)

Roadmap Adjustments:

Short-term: Added Signup (Auth functionality), Onboarding Tutorial

User Research

We surveyed adults aged 46–75 taking 3+ medications, which confirmed that patients struggle with complex medication schedules, with 75% missing doses weekly and 25% missing 3+ times weekly, while 21% fear side effects and 58% feel stressed managing medications. Most use reminder tools (72%), yet gaps remain in confidence and adherence, with 69% stopping medications without consulting a doctor. Users highly value progress tracking (28%) and sharing data with healthcare providers (90%), while 46% require caregiver support due to stress (89%). Hence, through the survey we acquired valuable insights into customer needs (reliable medication management, restore confidence, and multi-user support are critical needs) that guide us to implement our app effectively.

---

Full Changelog: 1.0.5...1.0.7

Tech Choices, Architecture Diagram, Roadmap

Overview of This Release

Added product_requirements.md, architecture details, roadmap.md, DoseMate GitHub Projects.

• product_requirements.md
• architecture folder
• roadmap.md
• DoseMate GitHub Projects

Progress & Assignment Contents

Since the last release, our team has completed Assignment 4 – Product Requirements & Architecture. We collaboratively developed our product requirements based on our JTBD and CUJs, ensuring they align with the overall vision for our MVP. We created four CUJs that describe key product interactions, and we tied them back to specific JTBD statements. On the technical side, we defined our initial architecture diagram and documented ADRs for each major stack decision. Each ADR includes rationale for the chosen tools as well as alternatives considered but not selected. Finally, we established a roadmap in GitHub Projects with milestones representing short-term, medium-term, and long-term goals. This roadmap includes immediate implementation tasks, user research activities, infrastructure development, and a low-fidelity plan for a future launch date.

Roadmap / Architecture / Use Case Changes

Use Cases: Approved initial CUJs with clear JTBD alignment. No changes beyond scope reduction for MVP feasibility.

Architecture: Finalized draft architecture diagram including core infrastructure (frontend, backend, database, authentication, CI/CD, cloud hosting). ADRs created for selected tools and technologies.

Roadmap updated in GitHub Projects.

Issue Summary

No major issue during this release

Roadmap updated to include:

Short-term: implement MVP features, set up CI/CD pipeline, design database schema, and perform early-stage user interviews.

Medium-term: conduct broader user research, iterate UI/UX, integrate analytics, and optimize system design.

Long-term: prepare for beta testing, add scalability features, and plan low-fidelity product launch.

CUJ

Overview of This Release

Added A3 - CUJ Runthrough Document

• Assignment 3 - CUJ Runthrough + Demo.pdf

Progress & Assignment Contents

Since our last release, our team has completed Assignment 3 - CUJ Runthrough + Demo. For this assignment, our team explored a CUJ focused on building and demonstrating a backend API endpoint using Django. We worked collaboratively to understand the framework, document the process, and evaluate the developer experience. We ran through the CUJ together, simulating the workflow of a developer creating a new API endpoint from scratch. This included reading Django documentation, following tutorials, troubleshooting errors, and reflecting on what aspects of Django’s design made the process easier or more difficult.

Roadmap / Architecture / Use Case Changes

No major changes to the project’s architecture or use cases since the last release.

Issue Summary

No major issue during this release

Team Exploration - Bias and Diversity Reflection

Overview of This Release

Added diverisity.md

• diversity.md

Progress & Assignment Contents

Since our last release, our team has completed Assignment 2 - Team Exploration - Bias and Diversity Reflection. In this submission, we provide a detailed overview of our team’s collective strengths, weaknesses, and areas of expertise. We also identify subject matter experts within our team, outline where external expertise will be needed, and reflect on how diversity and unconscious bias may influence our project. The write-up demonstrates our awareness of both the advantages of our varied backgrounds and the limitations that may affect our ability to empathize with users globally.

Roadmap / Architecture / Use Case Changes

No major changes to the project’s architecture or use cases since the last release.

Issue Summary

No major issue during this release

Roadmap updated to include:

Consulting with medical subject matter experts.

Prioritizing accessibility testing with seniors and individuals with diverse needs.

Team Introduction, Team Setup

Team Update Summary

Company Logo & Name

Our team has established a clear and modern identity with a logo and name that represents innovation and collaboration. Company Logo & Name

---

Team Profiles

We compiled detailed team profiles for all CSC454 members, each including: Profile photo, Contact information, GitHub, LinkedIn, Website, and Resume links, Short biography, Strengths and weaknesses

• Elyse Ando, Computer Science
• Ajinkya Bhosale, Computer Science
• Prahlad Ranjit, Computer Science
• Neha Sohail, Computer Science
• Ping Lu, Computer Science

---

Leader Selection

Our team selected Prahlad Ranjit as the leader.

• Reason for selection: Demonstrated strong organizational skills, ability to balance technical direction with team inclusivity, and prior experience leading projects.
• Role: The leader coordinates meetings, ensures equitable work distribution, oversees deadlines, and represents the team when communicating with instructors.

---

Team Principles

The team developed a 1-page principles document outlining expectations and guidelines: Team Principles

---

Issues

No major issue during this release!

---

Participation & Teamwork

Each member contributed equitably by:

• Actively collaborating and sharing the workload.
• Communicating regularly and effectively through designated channels.
• Upholding the team principles in all interactions.
• Supporting one another with feedback, technical help, and inclusivity.

All members demonstrated teamwork and responsibility throughout this assignment.

---