Software Requirements

Specifications
For
Smart Health Tracker
Version 1.0

Prepared by
Prerna kandpal
2301010251

Instructor : Dr. Mansi Kajal

Course : Software Engineering
Teaching Assistant : Dr. Mansi Kajal
Date : 25 August 2025
 Table of Content

1. INTRODUCTION
1.1 Document Purpose
1.2 Product Scope
1.3 Intended Audience and Document Overview
1.4 Definitions, Acronyms and Abbreviations
1.5 Document Conventions
1.6 References and Acknowledgements
2. OVERALL DESCRIPTION
2.1 Product Overview
2.2 Product Functionality
2.3 Design and Implementation Constraints
2.4 Assumptions and Dependencies
3. SPECIFIC REQUIREMENTS
3.1 External Interface Requirements
3.2 Functional Requirements
3.3 Use Case Model
4. OTHER NON-FUNCTIONAL REQUIREMENTS
4.1 Performance Requirements
4.2 Safety and Security Requirements
4.3 Software Quality Attributes
5. OTHER REQUIREMENTS (optional)
APPENDIX A – Data Dictionary
APPENDIX B – Solo Log
INTRODUCTION
The Smart Health Tracker is a mobile and web application that helps users monitor and improve
their health by tracking steps, calories burned, water intake, and sleep, while also providing
reminders, personalized insights, and progress visualizations. This document introduces the project,
outlining its purpose, scope, intended audience, and structure, with detailed system requirements,
functionalities, interfaces, and non-functional requirements covered in later sections.

1.1 Document Purpose

The Software Requirements Specification (SRS) for the Smart Health Tracker – Version 1.0
defines the system requirements for a mobile and web application that tracks daily health
activities such as steps, calories, water intake, and sleep. It outlines the product’s scope,
features, and constraints, ensuring all stakeholders—including developers, testers, and
users—share a common understanding of the system’s objectives. Serving as an official
record, this document specifies both functional and non-functional requirements and provides
a foundation for design, development, validation, and future enhancements.

1.2 Product Scope

The Smart Health Tracker is a cross-platform mobile and web application designed to help
users monitor daily health habits by tracking steps, calories, water intake, and sleep, either
manually or via wearable integration. It provides reminders, personalized insights, and visual
reports to encourage healthier lifestyle choices. The main objectives are to simplify health
tracking, promote consistency, and deliver data-driven insights for better decision-making.
Benefits include supporting fitness goals, improving routines, and enabling long-term
monitoring, while the system remains user-friendly, secure, scalable, and adaptable for future
features like AI-driven recommendations or healthcare integration.

1.3 Intended Audience and Document Overview

Intended Readers:
• Developers → for implementation
• Testers → for validation & test cases
• Instructor/Professor (Client) → for evaluation of clarity & completeness
• End Users → to understand features & benefits

Document Structure:

• Introduction → purpose, scope, definitions

• Overall Description → functionality, constraints, assumptions
 • Specific Requirements → functional & interface details
• Non-functional Requirements → performance, security, quality
• Other Requirements & Appendices → supporting info (data dictionary, logs)

Reading Guide:

• Start with Introduction & Overall Description for context

• Developers/Testers → focus on requirements & use cases
• Instructors → review full document for completeness

1.4 Definitions , Acronyms and Abbreviations

• API – Application Programming Interface: A set of functions and protocols that allow
interaction between software components.
• BMI – Body Mass Index: A value derived from the weight and height of a person,
used as an indicator of body fat.
• CSV – Comma Separated Values: A file format used for exporting and storing tabular
data.
• DBMS – Database Management System: Software used to store, manage, and query
structured data.
• GDPR – General Data Protection Regulation: A regulation on data protection and
privacy in the European Union.
• HTTPS – Hypertext Transfer Protocol Secure: A protocol used for secure
communication over the internet.
• UI – User Interface: The part of the software that the user interacts with.
• UML – Unified Modeling Language: A standardized modeling language for software
system design.

1.5 Document Conventions

Standard: Follows IEEE SRS guidelines
Formatting: Arial 11, single-spaced, 1-inch margins, bold numbered titles, bullet/numbered
lists
Naming:
• Functional → FRx (FR1, FR2)
• Non-functional → NFRx (NFR1, NFR2)
• Use cases → Ux (U1, U2)
• Acronyms → full form first, then abbreviated
 Highlighting: Italics for notes, Bold for IDs & headings

Purpose: Ensures consistency, readability, easy reference

1.6 Refernces and Acknowledgment

References
• IEEE Standard for Software Requirements Specifications (IEEE Std 830-1998).
• Google Fit – Official Documentation: https://support.google.com/fit
• Apple Health – Official Documentation: https://support.apple.com/explore/health
• React Native Documentation: https://reactnative.dev/docs
• MySQL Official Documentation: https://dev.mysql.com/doc

Acknowledgments

This project draws inspiration from existing health tracking applications like Google Fit and
Apple Health. The template and structure of this SRS are based on the IEEE SRS standard.
Guidance from academic instructors and publicly available resources was valuable in shaping
this document.
OVERALL DESCRIPTION
2.1 Product Overview

The Smart Health Tracker is a standalone mobile and web application that helps users monitor daily
health habits. It collects data from smartphone sensors and wearable devices, processes and stores it in
a backend server, and provides insights through an easy-to-use interface. The system is composed of
three main subsystems:

1. Frontend (Mobile & Web App) – user interface for logging and viewing health data.

2. Backend (Server & Database) – handles storage, authentication, and analytics.

3. External Device Integration – connects with wearables via APIs for automatic data sync.

2.2 Product Functionality

The Smart Health Tracker offers:

• User Management: Account creation, login, and profile handling.

• Activity Tracking: Monitoring steps, calories, water intake, and sleep (manual or via
sensors).

• Reminders & Notifications: Personalized prompts for health activities.

 • Progress Visualization: Graphical reports showing trends and goal progress.

• Device Integration: Sync with smartwatches and fitness bands.

• Data Storage & Backup: Secure health record storage with optional cloud backup.

• Export & Sharing: Export data in CSV for offline use or professional sharing.

2.3 Design and Implementation Constraints

The Smart Health Tracker will operate under the following constraints:

• Platform & Hardware: Supports Android 9+, iOS 13+, and major browsers; performance
depends on device sensors and memory.

• Technology Stack: Frontend – React Native (mobile), ReactJS (web); Backend –

Node.js/Express; Database – MySQL; REST APIs for communication and device integration.

• Security & Privacy: HTTPS communication, encrypted storage/transmission, two-factor

authentication, GDPR-compliant data handling.

• Design & Standards: Follows COMET methodology and UML for modeling; modular
architecture for future enhancements.

• Performance: Backend supports 1000+ concurrent users.

2.4 Assumptions and Dependencies

Assumptions:

• Users have a smartphone or web access with internet.

• Users can operate apps and input health data manually if needed.

• Devices have working sensors for activity tracking.

• Cloud storage and third-party wearable APIs remain reliable.

Dependencies:

• Relies on third-party wearable APIs; changes may affect functionality.

• Backend server and MySQL database must be available and reliable.

• Requires secure HTTPS; SSL issues may block features.

• Future upgrades may depend on cloud providers for storage and scalability.
SPECIFIC REQUIREMENTS
3.1 External Interface Requirements

3.1.1 User Interfaces

• Clean, intuitive mobile and web interface with dashboards, menus, and forms.

• Dashboard: Shows daily stats (steps, calories, water, sleep) with charts and progress bars.

• Input Forms: Log health data manually.

• Navigation Menu: Access reports, reminders, settings, and profile.

• Graphs & Reports: Line, bar, and pie charts for weekly/monthly trends.

• Reminders & Notifications: Pop-ups and push alerts for hydration, activity, and rest.

• Interaction via touchscreen (mobile) or point-and-click (web) using buttons, sliders, and
dropdowns.

3.1.2 Hardware Interfaces

• Smartphone Sensors: Accelerometer/pedometer (steps), gyroscope (activity type),

touchscreen (I/O).

• Wearable Devices: Smartwatches and fitness bands provide steps, heart rate, calories, and
sleep data via Bluetooth/Wi-Fi.

• Server/Cloud Hardware: Database and application servers for storing and processing health
metrics.

• Units: Steps, calories (kcal), water (liters/ml), sleep (hours).

3.1.3 Software Interfaces

• Mobile & Web Frontend: React Native / ReactJS communicates with backend via REST
APIs.

• Backend & Database: Node.js/Express and MySQL for authentication, data processing, and
storage.

• Wearable APIs: Google Fit, Apple HealthKit, Fitbit API for health data via secure OAuth
connections.

• Notification Services: FCM (Android) and APNS (iOS) for personalized reminders.

• Cloud Backup (future): AWS, Azure, or GCP for secure data backup and device
synchronization.

3.2 Functional Requirements

FR1: User Account Management

• Register via email, phone, or social login.

• Secure login/logout and password reset.

• Update profile details.

FR2: Activity Tracking

• Automatic step tracking via sensors/wearables.

• Manual logging of calories, water, and sleep.

• Sync data from wearable APIs (Fitbit, Apple Health).

FR3: Reminders & Notifications

• Set custom reminders (e.g., drink water).

• Push notifications for reminders and daily updates.

• Motivational alerts if goals not met.

FR4: Reports & Visualization

• Daily, weekly, monthly reports for steps, calories, water, sleep.

• Graphs, charts, progress bars.

• Compare current vs past performance.

FR5: Data Export & Backup

• Export data in CSV format.

• Cloud backup and multi-device sync.

FR6: Security & Privacy

• Encrypt data in storage and transmission.

 • Two-factor authentication (2FA).

• Restrict access to authenticated users only.

FR7: System Administration (Optional/Future)

• Admin monitoring of system performance.

• Event logging for debugging and audit.

3.4 Use Case Model

OTHER NON-FUNCTIONAL REQUIREMENTS
4.1 Performance Requirements
• P1. Response Time: The system shall process and display user inputs (e.g., logging water
intake) within 2 seconds.
• P2. Dashboard Updates: Graphs and reports shall update in real-time (less than 3 seconds
delay after new data entry).

• P3. Data Synchronization: Wearable device data shall be synced within 10 seconds of
initiating a connection.
• P4. Concurrent Users: The backend shall support at least 1000 concurrent active users
without performance degradation.
• P5. Storage Capacity: The system shall handle up to 5 years of health logs per user without
requiring manual data cleanup.
• P6. Availability: The system shall maintain 99% uptime to ensure uninterrupted access for
users.
• P7. Notification Delivery: Reminders and push notifications shall be delivered within 1 second
of the scheduled time.

4.2 Safety and Security Requirements

Safety Requirements

• S1. Data Integrity: Prevent data loss, corruption, or unauthorized modification.

• S2. Backup & Recovery: Daily automated backups with recovery options.

• S3. Fail-Safe Operations: Manual entry available if API/wearable fails.

Security Requirements

• SEC1. Secure Communication: HTTPS with SSL/TLS.

• SEC2. Authentication: Username + password, optional 2FA.

• SEC3. Data Encryption: Encrypt at rest and in transit.

• SEC4. Role-Based Access: User-only access; admins limited to monitoring.

• SEC5. Compliance: GDPR-like standards and best practices.

• SEC6. Session Management: Auto-expire after 15 mins inactivity.

• SEC7. Mobile Security: Block rooted/jailbroken devices.

4.3 Software Quality Attributes

4.3.1 Reliability

• 99% uptime under normal conditions.

• Automated error logging & monitoring.

• Offline local data view if server down.

4.3.2 Usability

• Intuitive interface with tooltips & error messages.

• First entry within 2 minutes of registration.

• Accessibility: large fonts, high-contrast, voice support.

4.3.3 Maintainability

• Modular architecture for easy feature addition.

• Industry coding standards & documentation.

• Unit + integration testing for smooth upgrades.

4.3.4 Portability

• Works on Android (v9+), iOS (v13+), web browsers.

• Minimal config changes for different cloud providers.

• Supports smartphones, tablets, laptops.

4.3.5 Interoperability

• Integrates with Google Fit, Apple Health, Fitbit (OAuth 2.0).

• CSV export compatible with Excel, Google Sheets, etc.

4.3.6 Adaptability (Design for Change)

• Easy to add new health metrics (e.g., heart rate, BMI).

• Notification engine supports new reminder types.

• Modular API integration for new wearables.

 APPENDIX A – Data Dictionary

Possible Values / Related Operations /

Name Type Description
States Requirements

Auto-incremented FR1 – Account creation

User_ID Integer Unique identifier for each user
numeric ID & management

Alphanumeric, 4–20
Username String User’s login name FR1 – Login/Register
characters

FR1, SEC2 –
Password String Encrypted password Hashed values only
Authentication

Number of steps recorded per

Steps Integer 0 – 100,000 FR2 – Activity Tracking
day

Calories Float Calories consumed/burned 0 – 10,000 kcal FR2 – Activity Tracking

Amount of water consumed 0 – 10 liters (or

Water_Intake Float FR2 – Activity Tracking
daily equivalent units)

Sleep_Hours Float Sleep duration logged 0 – 24 hours FR2 – Activity Tracking

Notification messages set by FR3 – Reminders &

Reminders String Text (max 100 chars)
users Notifications

Daily, Weekly, FR4 – Reports &

Reports Object Summary of user health metrics
Monthly Visualization

File Exported file of user’s health

Export_Data .csv format FR5 – Data Export
(CSV) logs

Status of synchronization with FR2, FR5 – Device

Sync_Status Boolean True / False
wearable devices Integration

Unique ID for each Auto-incremented

Notification_ID Integer FR3 – Notifications
notification/reminder numeric ID

Date and time when data was yyyy-mm-dd Applies to all FRs for
Timestamp Date/Time
logged hh:mm:ss logging
 APPENDIX B – Solo Log
As this project is completed individually, the following log summarizes the activities, progress,
and effort undertaken to produce this Software Requirements Specification (SRS) document for
the Smart Health Tracker project.

Date Activity

Aug 20, 2025 Selected project topic (Smart Health Tracker) and reviewed IEEE SRS template.
Aug 21, 2025 Drafted Introduction (Section 1.1 – 1.6) including purpose, scope, and definitions.
Aug 22, 2025 Completed Overall Description (Section 2.1 – 2.4) with system overview and assumptions.
Documented Specific Requirements (Section 3.1 – 3.3) including interfaces and use case
Aug 23, 2025
diagram.
Wrote Non-functional Requirements (Section 4.1 – 4.3) with performance, safety/security, and
Aug 24, 2025
quality attributes.
Finalized Other Requirements (Section 5), Data Dictionary (Appendix A), and Solo Log
Aug 25, 2025
(Appendix B).

Summary

• All requirements gathering, documentation, and system modeling activities were performed
independently.
• Additional creativity and research (Google Fit, Apple Health, IEEE templates) were used for
inspiration.
• The SRS is now complete and ready for submission.