Requirements List
This Requirements List defines the essential features, functionalities, and constraints for Who?Cares. It serves as a guiding document to ensure that our smart monitoring system aligns with the needs of caregivers and their loved ones. By outlining key technical and user requirements, this list helps maintain focus throughout the development process, ensuring a practical and effective final product.
Functional Requirements
Describes what the product must do, including functionalities and features:
• The wearable device must detect falls using an accelerometer and gyroscope.
• The system must provide real-time location tracking of the user within an indoor environment using BLE beacons.
• The system must monitor weight changes on the bed and sofa to detect presence.
• The magnetic door sensor must detect when a door is opened or closed.
• The Raspberry Pi must process sensor data and trigger alerts when necessary.
• Alerts must be sent to a visualization interface for caregivers.
• The system must support wireless communication via Wi-Fi and BLE.
Non-Functional Requirements
Details how the product should perform, covering performance, usability, reliability, scalability, security, and compliance:
• The system must update data in real time, with a minimum latency of one minute, to optimize energy consumption.
• The wearable device should have a battery life sufficient to demonstrate its functionality during the demo day, with the potential to be scaled for extended operation in future implementations
• Data processing must be performed efficiently on the Raspberry Pi to minimize delays.
• The device must be lightweight and comfortable for continuous wear.
• Security measures should ensure encrypted communication between devices.
Business Requirements
Defines high-level objectives such as market needs, customer expectations, cost constraints, revenue targets, and strategic alignment:
• The system should be cost-effective and competitive within the elder care technology market.
• The product should be scalable for future features, including GPS for outdoor tracking.
• The solution should provide an innovative and affordable alternative to existing caregiver monitoring systems.
• The final prototype should be demonstrated effectively during the demo day.
Technical Requirements
Specifies technical aspects such as technology stacks, integration points, data storage solutions, network requirements, and hardware considerations:
• The wearable device must use an ESP32 microcontroller for BLE and Wi-Fi communication.
• The Raspberry Pi 4 must be used as the central processing unit for edge computing.
• Load cell sensors must be connected to ESP32 and processed via an HX711 amplifier.
• Each home sensor must be connected to an ESP32 to collect data and transmit it to the local Raspberry Pi.
• The system must enable communication between the Raspberry Pi and ESP32 devices using a Wi-Fi-based protocol such as MQTT or HTTP.
• Data visualization should be presented through a simulated dashboard.
User Requirements
Focuses on user needs gathered through research or feedback, including personas, use cases, UX design principles, accessibility standards, and interface guidelines:
• Caregivers must be able to monitor the system through an intuitive and clear dashboard.
• Alerts must be clearly visible and distinguishable for emergency cases.
• The wearable device must be comfortable for elderly individuals with limited mobility.
• The system must be easy to set up and require minimal user intervention.
Regulatory Requirements
Lists legal and regulatory standards for different regions:
• The system must comply with CE and FCC certifications for electronic consumer devices.
• The wireless communication must adhere to Bluetooth and Wi-Fi regulatory guidelines.
• Data privacy and protection measures must align with GDPR (General Data Protection Regulation).
Environmental Requirements
Conditions related to where the product will be used or operated:
• The wearable device must be functional in indoor environments with obstacles such as walls.
• The device must withstand normal household conditions, including mild humidity and temperature variations.
Maintenance Requirements
Details post-launch maintenance, such as update frequency and support plans:
• The system should allow for remote software updates on the Raspberry Pi and ESP32.
• Regular battery charging should be required but minimized to once per day.
• The system should be easily repairable, with modular replaceable components.
Constraints
Limitations affecting how requirements can be met, such as budget constraints and deadlines:
• The total cost of components should not exceed the budget allocated by the professor.
• The project must be completed and demonstrated within the academic semester.
• The system must be assembled using readily available components from Mauser.
Assumptions & Dependencies
Assumptions requiring validation later in the process; dependencies on other projects or teams:
• Assumes BLE beacons provide sufficient accuracy for indoor localization.
• Assumes a stable Wi-Fi connection is available for communication.
• Assumes the elderly individual will wear the device consistently.
• Dependent on the availability of all required components from suppliers.
A well-defined list of requirements ensures mutual understanding among stakeholders to reduce ambiguities and communication failures throughout the development process.