ENTITY-RELATIONSHIP DIAGRAM

M.Sc. (Data Analyst) Dissertation Submitted to

CHRIST UNIVERSITY
Masters of Science
By
A.LAHARI
Roll Number: 2139465
submitted to
RAJESH.R

Department of Computer Science

CHRIST UNIVERSITY Banglore, Karnataka-560029
(DEEMED TO BE UNIVERSITY)
September , 2021
 ER DIAGRAM: ENTITY RELATIONSHIP DIAGRAM
MODEL
INTRODUCTION:
 In 1967 PETER CHEN developed ER MODEL. It is a high-level data model used for
developing the conceptual design of the database. ER diagram helps designers
understand and specify the desired components of database and the relationship
among them. It must be flexible enough so that it can be used and understood
in any environment where info is modelled

What is ER Diagram?
 ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram
that displays the relationship of entity sets stored in a database. In other words, ER
diagrams help to explain the logical structure of databases. ER diagrams are created
based on three basic concepts: entities, attributes, and relationships.
 ER Diagrams contain different symbols that use rectangles to represent entities,
ovals to define attributes and diamond shapes to represent relationships.
 At first look, an ER diagram looks remarkably similar to the flowchart. However, ER
Diagram includes many specialized symbols, and its meanings make this model
unique. The purpose of ER Diagram is to represent the entity framework
infrastructure.

EXAMPLE:
ER DIAGRAMS SYMBOLS & NOTATIONS:

S.NO MEANING NOTATION ALTERNATIVE NOTATION

1 ENTITY

2 WEAK ENTITY

3 ATTRIBUTE

4 PRIMARY

ATTRIBUTE

5 PARTIAL

ATTRIBUTE

6 MULTI-VALUED

ATTRIBUTE
 7 RELATIONSHIP

8 WEAK-

RELATIONSHIP

COMPONENTS OF THE ER DIAGRAM:

This ER model consists of three basic concepts:

 Entities
 Attributes
 Relationships
Online Shopping System ER Diagram /Entity
Relationship Diagram:
 PROJECT NAME: Online Shopping system
 OBJECTIVE: To make a project based on online
shopping system by using My sql (Oracle).
 GOAL:
I have choosen online shopping system to create my project.
To make a project based on online shopping system by using
my sql. This project mainly based on database. So that our
principle goal is to connect database with sql

 Data Description: This database consists of

1. Users: User and Admin information is added to database with
Unique ID based on their roles.
2. Shopping: Complete products information is stored in this
table.
3. Orders: Customer ordered products, status and delivery
information is stored in this table.

 DESCRIPTION:
 Any member can register and view available products.
 Only registered member can purchase multiple products
regardless of quantity.
 Can contact admin page is available to contact Admin for
queries.
 There are three roles available: customer, supplier and
Admin.
 Visitor can view available products.
 User can view and purchase products.
 An Admin has some extra privilege including all
privilege of visitor and user.

 Admin can add products, edit product information and

add/remove product.
  Admin can add user, edit user information and can remove
user.
 Admin can ship order to user based on order placed by
sending confirmation mail.

 Minimum Software Requirement:

 ERDPlus

The software I have choosen to draw the ER diagram is ERDplus .This software
is mainly a web-based data modeling ER diagram tool which easily represents
relational database drawings and makes complex database structures to be
easily understandable.

 Features

1. Automatically convert ER Diagrams into Relational Schemas.

2. Export standard SQL.
3. Include all the shapes required to denote each & every item in an
ERD.
 PRICE:
1. Free of cost
 ELEMENTS:
a) Entity Sets:
a. Website/ Mobile Application
b. Customer
c. Product
d. Admin/server
e. Supplier
f. registration or login.
 B) Customer:
Attributes:
a. User name (varchar 10)
b. Password (varchar 10)
c. Email address (varchar 10)
d. Mobile number (number 15)
e. Country name (varchar 10)
f. District (varchar 10)
g. Address (varchar)
h. C_id (number)
 C) Products:
Attributes:
a. Product id (number 5)
b. P_name (varchar 10)
c. P_catagory (varchar 10)
d. P_price (number 5)
e. P_availibility (number 5)
 d) Admin/server:
Attributes:
a. User name (varchar 10)
b. Password (varchar 10)
c. A_id (Number
  WHAT IS AN ENTITY?

 An entity can be a person, place, event, or object that is relevant to a given

system. For example, a school system may include students, teachers, major
courses, subjects, fees, and other items
 Entities are represented in ER diagrams by a rectangle and named using
singular nouns.

 WEAK ENTITY:
A weak entity is the one which is dependent on another entity. It is portrayed by a double
rectangle.
ATTRIBUTE:
 Attribute - A property or description of an entity. A toy department
employee entity could have attributes describing the students name,
class, and year.

KEY ATTRIBUTE:

The key attribute is capable of uniquely identifying an entity

from an entity set
COMPOSITE ATTRIBUTE:
A composite attribute refers to an attribute which is composed of various
other attributes. It is portrayed by an eclipse, which is linked with other
eclipses.

MULTI-VALUED ATTRIBUTE:

A multivalued attribute consists of more than one value. Multivalued attributes are
represented by a double oval. For instance, any customer can have one or more
than phone numbers.
DERIVED ATTRIBUTE:
Any attribute which can be acquired by any other attribute is considered as a
derived attribute. It is portrayed by a dashed ellipse. For instance, the age of the
person can be changed with time and can even be derived from any other
attribute such as Date of Birth.

ER Diagram Primary Key :

 ERD is actually a higher-levels conceptual details design diagram. Entity-Relation
version is founded on the notion of genuine-community organizations and the
relationship between the two. ER modeling helps you to analyze details needs
systematically to generate a nicely-made database.
RELATIONSHIPS AND RELATIONSHIP SETS:

 A relationship is an association among two or more entities.

 For example, we may have the relationship that jay works
in the pharmacy department.
 As with entities, we may wish to collect a set of similar relationships
into a relationship set.

Types of relationships:
 One-to-one: When only a single instance of an entity is associated with the
relationship, it is termed as '1:1'.

 One-to-many: When more than one instance of an entity is related

and linked with a relationship, it is termed as '1:N'.

 Many-to-one: When more than one instance of an entity is linked

with the relationship, it is termed as 'N:1'.

 Many-to-many: When more than one instance of an entity on the left

and more than one instance of an entity on the right can be linked with the
relationship, then it is termed as N:N relationship.
RELATIONSHIP:
DIAGRAM FOR ONLINE SHOPPING SYSTEM
Diagram for Online Shopping System
CONCLUSION:
ER diagrams constitute a very useful framework for creating and manipulating
databases. First, ER diagrams are easy to understand and do not require a
person to undergo extensive training to be able to work with it efficiently and
accurately.hence, I have taken the dataset of online shopping and created an
ER diagram which is easy communicate with developers, customers, and end
users, regardless of their IT proficiency. Second, ER diagrams are readily
translatable into relational tables which can be used to quickly build databases.
In addition, ER diagrams can directly be used by database developers as the
blueprint for implementing data in specific software applications. Lastly, ER
diagrams may be applied in other contexts such as describing the different
relationships and operations within an organization.

REFERENCES:
1. Anne Boehm, Joel Murach, Murach’s ASP.NET 4 Web Programming with
C# 2010, 4th Edition, Murach, 2010.

2. Bryan Syverson, Joel Murach, Murach’s SQL Server 2012 for developers,
Murach, 2012.

https://www.guru99.com/er-diagram-tutorial-dbms.html

http://www.tekkom.dk/w/images/5/5f/ER-Diagrams.pdf

https://www.w3schools.in/dbms/er-model/