Functional Requirements
Routine Tracking + Recommendations
Mental Exercises Game
Daily Life Question
Memory Scrapbook
Data Sharing for NOK
Local Event Scraping
Physical Activity Tracker
This rough outline helped the group identify what key features we wanted to include in our final product.
Data Flow Diagram Expanded (DFD Level 1)
To visualize the system's processes and data interactions, I developed an expanded Level 1 Data Flow Diagram. This DFD outlines the main processes:
User Management
Routine Tracking & Recommendations
Mental Exercises Module
Physical Exercises Module
Daily Life Questions
Memory Scrapbook
Event Scraping
Gamification & Leaderboard
Data Sharing with Next of Kin
This diagram helped the team understand the data flow between external entities, processes, and data stores, enabling us to identify potential bottlenecks and design improvements.
After evaluating the various design alternatives, we selected the following approach for our project:
Chosen Design Concept:
Architecture: Microservices Architecture
User Interface: Cross-Platform Mobile Application
Data Storage: Cloud-Based Storage with PostgreSQL
Interaction Methods: Standard Touch Interface with Accessibility Features
*Made using Draw.io*
Our final system architecture looks like:
System Architecture:
Microservices Breakdown:
User Management Service: Handles registration, authentication, and profile management.
Routine Tracking Service: Manages user routines and generates recommendations.
Exercise Services: Separate services for mental and physical exercises.
Memory Service: Allows users to store and retrieve memories.
Event Scraping Service: Collects and updates local community events.
Gamification Service: Manages leaderboards and achievements.
Data Sharing Service: Facilitates secure sharing of user data with next of kin.
Database Design:
Primary DB
PostgreSQL
Supports our needs, simple enough to use.
Media Storage
AWS Cloud Storage (?)
Store all user images and videos.
Software Specifications:
Database (PostgreSQL) (Redis)
Python (Flask)
Auth (OAuth?)
Hardware Requirements:
Wearable device
capable to tracking activity data
Expected Challenges
Data Integration from various wearable brands.
Data synchonization without extensive battery drain.
Our Test Plan is as follows:
Validate each microservice meets requirements.
Test various wearables for data upload.