Entity Relationship Diagram – Video PIVC

An Entity–relationship model (ER model) describes the structure of a

database with the help of a diagram, which is known as Entity
Relationship Diagram (ER Diagram). An ER model is a design or
blueprint of a database that can later be implemented as a database.
The main components of E-R model are: entity set and relationship
set.

Entity Sets - • A database can be modeled as: – a collection of entities,

– relationships among entities.
• An entity is an object that exists and is distinguishable from other
objects. Example: specific person, company, event, plant
• An entity set is a set of entities of the same type that share the same
properties. Example: set of all persons, companies, trees, holidays.

The Entity-Relationship (ER) diagram presented for the Video PIVC

project is essential for several reasons pertaining to database design
and development:

Data Modeling: The ER diagram visually represents the project's data

model, outlining entities, attributes, and their relationships. This
model aids in understanding the data structure and how different
elements relate to each other within the database.

Requirement Analysis: By capturing all relevant entities and

attributes, the ER diagram ensures alignment with project
requirements. It serves as a blueprint for database design,
guaranteeing that the database schema addresses the project's
objectives and user needs effectively.

Normalization: The ER diagram assists in the normalization process

by identifying relationships between entities. Normalization
principles are applied to eliminate data redundancy and maintain
data integrity, resulting in a well-structured and efficient database
schema.
List OF Possible Entities Required in Video PIVC -

1. User/Customer
2. Language
3. DOB (Date of Birth)
4. Questionnaire
5. Product
6. Health Questions
7. OTP
8. Report
9. Admin
10.Super Admin
11.Dashboard

List OF Possible Attributes Required

User: UserID, Name, Mobile Number, Email, PAN Number,

Aadhaar Number, KYC Number, Loan Number, Occupation,
Age, Address
Language: LanguageName eg-English , Hindi , Bengali,
Marathi , Punjabi
DOB: DOB
Product: ProductID, ProductName
Health Questions: QuestionID, QuestionText, ProductID
OTP: UserID, EncryptedOTP
Report: ReportID, TotalHits, CompletedCases, PendingCases,
CompletionPercentage
Admin: AdminID, Username, Password
Super Admin: SuperAdminID, Username, Password
Dashboard: DashboardID, PremiumAmount, RefNo,
RAGStatus

Relationships:

User - Language (One-to-Many)

User - DOB (One-to-One)
User - OTP (One-to-One)
User - Report (One-to-One)
Super Admin - Admin (One-to-Many)
Admin - Link Trigger (One-to-Many)
Admin - Report (One-to-Many)
Dashboard - Report (One-to-One)
Dashboard - User (One-to-Many)

Entities in Video Pivc:

User: Represents individuals using the system. Contains

attributes such as UserID, Name, Mobile Number, Email,
PAN Number, Aadhaar Number, KYC Number, Loan Number,
Occupation, Age, Address
Language: Represents the languages preferred by users. It
has a one-to-many relationship with the User entity, as a
user can prefer multiple languages.
DOB: Represents the date of birth of users. It has a one-to-
one relationship with the User entity, as each user has only
one date of birth.
Product: Represents products within the system. Contains
attributes like ProductID and ProductName.
Health Questions: Contains questions related to health that
are associated with specific products. It has a one-to-many
relationship with the Product entity.
OTP: Represents one-time passwords generated for users. It
has a one-to-one relationship with the User entity.
Report: Contains reports generated by the system. It has a
one-to-one relationship with the User entity, indicating each
user can have one report.
Admin: Represents administrators of the system. Contains
attributes like AdminID, Username, and Password.
Super Admin: Represents super administrators with higher
privileges. It has a one-to-many relationship with the Admin
entity, indicating multiple admins can be managed by one
super admin.
Dashboard: Represents a dashboard within the system.
Contains attributes like DashboardID, PremiumAmount, etc.
It has a one-to-one relationship with the Report entity and a
one-to-many relationship with the User entity.

Relationships:

User - Language: One user can prefer multiple languages,

represented by a one-to-many relationship.
User - DOB: Each user has only one date of birth,
represented by a one-to-one relationship.
User - OTP: Each user has one OTP, represented by a one-to-
one relationship.
User - Report: Each user has one report, represented by a
one-to-one relationship.
Admin - Super Admin: One super admin can manage
multiple admins, represented by a one-to-many relationship.
Admin - Link Trigger: One admin can have multiple link
triggers, represented by a one-to-many relationship.
Admin - Report: One admin can generate multiple reports,
represented by a one-to-many relationship.
Dashboard - Report: Each dashboard is associated with one
report, represented by a one-to-one relationship.
Dashboard - User: Each dashboard can monitor multiple
users, represented by a one-to-many relationship.
 EncryptedOT
UserID, Name, Mobile
Number, Email, PAN Prefers Language
Number, Aadhaar Number,
KYC Number, Loan Number,
Name
Occupation, Age, Address

includes
QuestionID,
QuestionText,
ProductID, ProductID
ProductName

UserID,
EncryptedOTP

ReportID, TotalHits,
CompletedCases,
PendingCases,
DashboardID, s CompletionPercentage
PremiumAmount,
RefNo, RAGStatus

:
AdminID, Username,
SuperAdminID, manages
Password
Username, Password