Personal Health Monitoring System | Team 7

Software Design Descriptions

for

Personal Health Monitoring System

Version 1.0 approved

Prepared by Team 7
Team Members
Abhay Sharma (100445768)
Aniket Bagga (100435498)
Joshua Okotore (100396280)
Jaideep Singh (100439747)

October 05, 2024

1
 Personal Health Monitoring System | Team 7

Table of Contents
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 Scope ........................................................................................................................................... 1
1.3 Intended audience ........................................................................................................................ 1
1.4 Reference ..................................................................................................................................... 1
1.5 Summary ...................................................................................................................................... 1
2. Definitions .................................................................................................................................1
3. Design viewpoints .....................................................................................................................1
3.1 Logical viewpoint..................................................................................................................................
3.2 Information viewpoint...........................................................................................................................
3.3 Algorithm viewpoint..............................................................................................................................
Appendix A: Glossary..............................................................................................................................

2
 Personal Health Monitoring System | Team 7

1. Introduction
This Software Design Description report thoroughly explains the purpose and scope of the
Personal Health Monitoring System. Also, includes information about the logical design view of
the System. This document serves as a comprehensive guide for developers, stakeholders, and
users, detailing the system's objectives, key components, and technical specifications, ensuring a
robust and user-friendly experience that prioritizes both functionality and data security.
1.1 Purpose
The purpose of the Personal Health Monitoring System (PHMS) desktop version is to provide
individuals with an efficient and user-friendly tool for managing their health and wellness. The
system aims to provide users a platform to manage their health personally, by inputting
information such as test results, test date, daily activities, etc. Ultimately, the goal is to support
users in making informed health decisions, improving their overall quality of life.

1.2 Scope
The scope of the Personal Health Monitoring System (PHMS) desktop version focuses on the
development of a user-centric application aimed at enhancing personal health management. Key
components of the scope include:

 Health Metric Logging: Users can easily track important health information like their
weight, exercise routines, eating habits, sleep quality, and vital signs such as heart rate
and blood pressure. This means you can keep a close eye on how you’re doing health-
wise!
 Graphical User Interface (GUI): The app will have a simple and attractive layout that
makes it super easy to use. You’ll find colorful dashboards with interactive charts and
graphs that show your health data clearly, so you can quickly see trends and changes over
time.
 Goal Setting and Reminders: You can set personal health goals, like drinking more
water or exercising regularly, and the app will remind you to stay on track. This helps you
build healthy habits and keeps you motivated!
 Data Analysis and Insights: The system will analyze your health data and give you
helpful insights. For example, it can help you notice patterns, like how your sleep affects
your energy levels, allowing you to make better decisions about your health.
 Security and Compliance: The application will implement industry-standard security
protocols to ensure the protection of sensitive health information, adhering to applicable
privacy regulations such as HIPAA.

1.3 Intended audience Who The intended audience for this document includes:

1. Developers: The software engineers and programmers who will build and code the
Personal Health Monitoring System (PHMS). They’ll need this document to grasp what
the system should do and how it should be designed.

3
 Personal Health Monitoring System | Team 7

2. Project Managers: The people overseeing the project who make sure everything stays
on track and meets deadlines. They’ll use this document to manage resources and ensure
the project aligns with its goals.
3. Stakeholders: Investors or organizational leaders who are interested in the project’s
outcomes and how it can impact health management. They’ll look for insights on the
system’s value and potential benefits.
4. Healthcare Professionals: Doctors, nurses, and health coaches who might recommend
the system to their patients or clients for better health tracking. They’ll want to
understand its features and how it can support their work.
5. End Users: Individuals looking for a tool to help them manage their health. While this
document is more technical, it also outlines features that will improve their experience
and usability.
6. Quality Assurance Teams: The folks responsible for testing the application to ensure it
works properly and meets all the specified requirements.

1.4 Reference
 draw.io - free flowchart maker and diagrams online. (n.d.). https://app.diagrams.net/
 GeeksforGeeks. (2024, June 25). What is Systems Design Learn System Design.

GeeksforGeeks. https://www.geeksforgeeks.org/what-is-system-design-learn-system-

design/

 Nishadha, & Creately. (2022, November 25). UML Class Diagram Relationships

Explained with Examples. Creately. https://creately.com/guides/class-diagram-

relationships/

1.5 Summary
The Personal Health Monitoring System (PHMS) desktop version is designed to help users take
charge of their health in a simple and effective way. This document covers the system’s goals,
features, and target audience, highlighting how it allows users to log important health metrics.
The system also provides insights based on the tracked data, encouraging users to make informed
health decisions. This document is a key resource for developers, project managers, healthcare
professionals, and users, guiding the collaborative effort to build a valuable tool for personal
health management.
2. Definitions
 logical design: refers to the abstract representation of the system, focusing on how data is
structured and how different components interact without worrying about the specifics of
implementation. It’s about planning the overall architecture and flow of information.

4
 Personal Health Monitoring System | Team 7

 Health Metric Logging: the process of collecting and recording various health-related
data points, such as heart rate, blood pressure, weight, and glucose levels. This
information is essential for tracking a patient's health over time and can be used to
analyze trends or make informed decisions.
 Graphical User Interface (GUI): The Graphical User Interface (GUI) is the visual part
of the application that users interact with. It includes buttons, menus, charts, and other
elements that make it easy for users to input data, view metrics, and navigate through the
software.
 End Users: he people who will actually use the software. In this context, they might
include patients logging their health metrics, healthcare professionals accessing patient
data, or anyone using the system to monitor health.
 Developers: the individuals or teams responsible for designing, building, and maintaining
the software. They write the code, create the functionality, and ensure that everything
works as intended.
 Project Managers: oversee the project, ensuring it stays on track, within budget, and
meets deadlines. They coordinate between different teams, manage resources, and
facilitate communication among stakeholders.
 Healthcare Professionals: include doctors, nurses, and other medical staff who use the
software to monitor patient health, analyze data, and provide care. They rely on accurate
health metrics to make informed decisions about treatment.
 Algorithms: step-by-step procedures or formulas for solving a problem or performing a
task. In this project, algorithms might be used to analyze health data, detect anomalies, or
generate reports based on logged metrics.
 Classes: are blueprints in object-oriented programming that define the properties (attributes) and
behaviors (methods) of objects. For example, a Patient class might have attributes like name
and email and methods for logging metrics.
 Interfaces: define a contract or a set of methods that a class must implement. They allow different
parts of the system to communicate with each other without needing to know the details of each
other's implementation.
 Objects: instances of classes that contain actual data.
 Metadata: data that provides information about other data.

3. Design viewpoints
This section describes different design stances for the Personal Health Monitoring System
(PHMS), offering in-depth illustrations of the architecture, data structures, and algorithms of the
system.

3.1 Logical viewpoint

The Logical Viewpoint aims to clarify and expound upon the intended types, together with their
realizations as classes and interfaces, encompassing their structural and static interrelationships.
The relationships between classes, interfaces, and objects in the system are represented using
UML class diagrams to do this.

5
 Personal Health Monitoring System | Team 7

Overview of the Class Diagram

The PHMS has identified the following major classes, which work together to meet the needs of
the system:
 USER (Abstract Class)
Attributes: userID, userName, userType, password, email
Methods: login(), logout()

 PATIENTS (Inherits from User)

Attributes: UserID, PatientID, PatientName, Address, Password, testResults[],
Testreminders[]
Methods: enterTestResults(), generateReport(), modifyResults()
 DOCTORS (Inherits from User)
Attributes: DoctorID, DoctorName, Address, Password, testResults[], Testreminders[]
Methods: viewTestResults(), viewReport(), provideFeedback()
 ACTIVITY_LOG
Attributes: ActivityID, PatientID, Log_Date(), FoodIntake(), MedicineIntake(),
Feelings(),
Methods: adddailyLog(), ModifyLog(), DeleteLog()
 SYSTEM
Attributes: SystemID, UserID, actionType
Methods: StoresUserInfo(), LogUserActivity(), generateAlert(), TriggerTestReminder(),
EncryptionMethod()
 TEST_RESULTS
Attributes: TestResultID, PatientID, DoctorID, TestName, TestDate, Results
Methods: validateResult(), matchWithMonitoringItems()
 TEST_REMINDERS
Attributes: reminderID, reminderDate, reminderDescription
Methods: triggerReminder()
 TEST_REPORTS
Attributes: reportID,UserID, reportType, reportDate, reportContent

6
 Personal Health Monitoring System | Team 7

Methods: generateReport()

UML DIAGRAM:

In this schematic:
PATIENTS uses the abstract User class as its base class.
To control alarms, reminders, and report production, the System communicates with the
TestResult, Reminder, and Report objects.
3.2 Information viewpoint
Data access mechanisms, metadata definitions, data management tactics, and persistent data
structures are the main areas of emphasis for the Information Viewpoint. To hold persistent data,
such as test results, reminders, and reports, the PHMS makes use of a MySQL database.

7
 Personal Health Monitoring System | Team 7

USER TABLE:

The USER table holds general information about all users in the system, including patients and
system administrators.

 UserID: A unique identifier for each user (Primary Key).

 UserName: The first name and the last name of the user.
 UserType: This specifies if the user is a doctor or a patient.
 email: The user's email address for login and communication.
 password: The hashed password for authenticating the user.

PATIENTS Table:
Particular health-related information is kept in this table for users (patients) under observation.
 UserID: Links to the User table (Foreign Key), identifying the patient.
 PatientID: Something to uniquely identifies the patients.
 chronicConditions: A string that lists any chronic conditions the user may have (e.g.,
"Diabetes, Hypertension").
 healthMetrics: Stores the user's health metrics as a serialized string (e.g., heart rate, blood
pressure, etc.). In this case, it's a VARCHAR field to store complex data, which can be
parsed by the application.

8
 Personal Health Monitoring System | Team 7

SYSTEM Table
This table is used to manage system configurations that affect the functionality of the Personal
Health Monitoring System and to log system-level activities like alerts, reminders, and
notifications.
 systemID: A unique identifier for each system-level action or configuration (Primary
Key).
 actionType: Defines the type of system action (e.g., "Alert", "Reminder", "Notification").
 TriggeredAT: Specifies the date and time when the alert or reminder was generated.
 userID: Links to the User table (Foreign Key), identifying the user for whom the system
action was performed.
 configKey: (Optional) A configuration key, if the system is storing key-value pairs for
configuration settings (e.g., maxUsers, alertFrequency).
 configValue: (Optional) The value associated with the configuration key

TEST_RESULTS Table:

The TEST_RESULTS table stores medical test results for users in the Personal Health
Monitoring System (PHMS).

9
 Personal Health Monitoring System | Team 7

 resultID: Unique identifier for each test result (Primary Key).

 userID: Foreign key linking to the user in the User table, indicating who the test result
belongs to.
 testName: Name of the test performed (e.g., "Blood Test").
 resultValue: Numerical value of the test result (e.g., blood sugar level).
 testDate: Date when the test was conducted.
 TestResult: Abnormal or normal.

3.3 Algorithm viewpoint

Algorithm: Produce Annual or Monthly Report
Users can generate reports based on test results over a specified period of time (monthly or
annually) using the report generation capabilities. The following are the steps in the algorithm:

Input:
userID (INT) - ID of the user requesting the report.
reportType (VARCHAR) - Either "monthly" or "annual."
timeFrame (DATE RANGE) - The date range for which the report is to be generated.

Process:
 Select Time Frame:
If reportType is "monthly", set startDate and endDate to the first and last days of the
selected month.
If reportType is "annual", set startDate and endDate to the first and last days of the
selected year.

10
 Personal Health Monitoring System | Team 7

Query Test Results:

Fetch all test results from the TestResult table for the userID where the testDate falls
between startDate and endDate.
 Compile Data:
Compile the fetched test results into a structured report format, including any abnormal
values that exceeded predefined health thresholds.
 Generate Report:
Output the compiled data into a report, either in PDF format or displayed in the GUI.
 Store Report:
Save the report.
Appendix A: Glossary
Activity Log: A record of daily health-related activities, including food intake, medicine intake, and
feelings.

Data Analysis: The process of inspecting, cleaning, transforming, and modeling data to discover useful
information for decision-making.

Developers: Individuals or teams responsible for designing, coding, and maintaining the software.

End Users: Individuals who will use the software, such as patients, healthcare professionals, and
caregivers.

Goal Setting: The process of defining personal health objectives (e.g., increasing exercise) within the
application.

Graphical User Interface (GUI): The visual components of the application, including buttons, menus,
and charts, that facilitate user interaction.

Health Metric Logging: The process of collecting and recording health-related data points (e.g., weight,
blood pressure) for tracking and analysis.

HIPAA: Health Insurance Portability and Accountability Act; U.S. legislation that provides data privacy
and security provisions for safeguarding medical information.

Interfaces: Contracts that define a set of methods a class must implement, enabling communication
between different components of the system.
Logical Design: An abstract representation of the system, focusing on data structures and component
interactions without implementation specifics.

Security Protocols: Standards and procedures implemented to protect sensitive health information from
unauthorized access.

11
 Personal Health Monitoring System | Team 7

System: The overall software application that facilitates health monitoring and management

Test Results: Data collected from medical tests, recorded within the system for tracking and analysis.

Test Reminders: Notifications sent to users to remind them of upcoming health tests or actions

UML (Unified Modeling Language): A standardized modeling language used to visualize the design of
a system, often represented through diagrams.
Wellness: The overall state of health and well-being, encompassing physical, mental, and emotional
aspects.

12