Page 102 - FULL REPORT 30012024

4.2.6 Database Modelling

This section delves into the comprehensive design of the database, outlining
its architecture, components, and the interactions between them.

i. Data Model
In MySQL, a relational database, data is organized using a table-based

model. This database will be used to keep the prediction data input by
user. The essential reason of choosing MySQL is because it is the most

compatible database and easy to implement in most web hosting. Table
4.3 display the data model of the user’s prediction data.

Table 4.3 Data model of userdata’s table.
Attributes Data Type Description
user_id int(11) The prediction ID
gender varchar(10) Gender of the user
age varchar(11) Age of the user
hypertension varchar(10) Presence of hypertension
heart_disease varchar(10) Presence of heart disease
weight varchar(10) Weight of the user
height varchar(10) Height of the user
bmi varchar(10) Body Mass Index
smoking_status varchar(50) Smoking status
ever_married varchar(10) Marital status
work_type varchar(50) Type of work
residence_type varchar(50) Type of residence
stroke_level varchar(10) Level of stroke risk
stroke_risk varchar(10) Stroke risk status

4.3 Application Design

This section delves into the structural and functional blueprint of the web

application with a particular focus on two core modules: the Dashboard
Module and the Prediction Module.

85