INDEX

Sr. No. Content Page No.

ANNEXURE-I
1.0 Aims/Benefits of the Micro-Project 5

2.0 Course Outcomes Addressed 5

3.0 Proposed Methodology 5

4.0 Action Plan 6

5.0 Resources Required 6

ANNEXURE-II
Brief Introduction/Rationale
1.0 7-8

2.0 Components of a ER Diagram 9-15

3.0 Steps to Create an ERD 15-19

4.0 Course Outcomes Achieved 20

5.0 Actual Resources Used 20

6.0 Skill Developed / Learning outcomes of this Micro-Project 21

7.0 Conclusion of this Micro-Project 21

ANNEXURE-I

1
1.0 Aims/Benefits of the micro project
Introduction to ER Diagram with the help of diagram
Benefit Taken from this micro-project is understanding the concept of ER diagram notations

2.0 Course outcome addressed.

 Implement standard ER diagram by using notation.

 Implement various notation, attributes for ER diagram
 Gain Knowledge about The ER diagram

3.0 Proposed methodology

1. Focused on the selection of an appropriate topic for the micro-project.

2. Select the topic i.e. To Prepare a report on ER diagram notation
3. Brief study on our topic.
4. Gather all information based on the topic of the micro project.
5. Analysis and study of our topic in detail.
6. Following all the above methodologies we successfully completed our microproject.

4.0 Action Plan

2
 Sr. Plan start Plan finish Name of responsible
Detail of activity
No. date date team members

1 Searching the topic for micro-project 26-09-2023 30-09-2023 Shinde Srushti

Collect information from the internet

2 02-09-2023 05-09-2023 Kadyal Rajeshwari
and textbook

Collect information from the Data

3 Base management system 22319 07-10-2023 11-10-2023 Kutal Shravani
reference book

4 Arrange all information in MS word 12-10-2023 19-10-2023 Shinde Siddhi

5 Prepare a report on it using MS word 20-10-2023 22-10-2023 Shinde Srushti

6 Print micro project 25-10-2023 25-10-2023 Shinde Siddhi

5.0 Resources used

Sr. no. Name of resource material Specifications Quantity

1 Computer System 16 GB RAM, Windows 10 OS 1

1
2 Textbook/Manual DBMS Database Management System 22319

ANNEXURE-II

3
1.0 Brief Introduction/Rationale

Entity Relationship Diagram – ER Diagram in DBMS

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.

What is an Entity Relationship Diagram (ER Diagram)?

An ER diagram shows the relationship among entity sets. An entity set is a group of
similar entities and these entities can have attributes. In terms of DBMS, an entity is a
table or attribute of a table in database, so by showing relationship among tables and their
attributes, ER diagram shows the complete logical structure of a database. Lets have a
look at a simple ER diagram to understand this concept.

Facts about ER Diagram Model:

ER model allows you to draw Database Design
It is an easy to use graphical tool for modeling data
Widely used in Database Design
It is a GUI representation of the logical structure of a Database
It helps you to identifies the entities which exist in a system and the relationships between
those entities

Why use ER Diagrams?

Here, are prime reasons for using the ER Diagram

Helps you to define terms related to entity relationship modeling
Provide a preview of how all your tables should connect, what fields are going to be on
each table
Helps to describe entities, attributes, relationships
ER diagrams are translatable into relational tables which allows you to build databases
quickly ER diagrams can be used by database designers as a blueprint for implementing
data in specific software applications

A simple ER Diagram:
4
In the following diagram we have two entities Student and College and their relationship.
The relationship between Student and College is many to one as a college can have many
students however a student cannot study in multiple colleges at the same time. Student
entity has attributes such as Stu_Id, Stu_Name & Stu_Addr and College entity has
attributes such as Col_ID & Col_name.

Here are the geometric shapes and their meaning in an E-R Diagram. We will discuss
these terms in detail in the next section (Components of a ER Diagram) of this guide so
don’t worry too much about these terms now, just go through them once.

Rectangle: Represents Entity sets.

Ellipses: Attributes
Diamonds: Relationship Set
Lines: They link attributes to Entity Sets and Entity sets to Relationship Set
Double Ellipses: Multivalued Attributes
Dashed Ellipses: Derived Attributes
Double Rectangles: Weak Entity Sets
Double Lines: Total participation of an entity in a relationship set

5
 2.0 Components of a ER Diagram

As shown in the above diagram, an ER diagram has three main components:

1. Entity
2. Attribute
3. Relationship

1. Entity

An entity is an object or component of data. An entity is represented as rectangle in an

ER diagram.
For example: In the following ER diagram we have two entities Student and College
and these two entities have many to one relationship as many students study in a single
college. We will read more about relationships later, for now focus on entities.

6
Weak Entity:

An entity that cannot be uniquely identified by its own attributes and relies on the
relationship with other entity is called weak entity. The weak entity is represented by a
double rectangle. For example – a bank account cannot be uniquely identified without
knowing the bank to which the account belongs, so bank account
is a weak entity.

Weak Entities

A weak entity is a type of entity which doesn't have its key attribute. It can be identified
uniquely by considering the primary key of another entity. For that, weak entity sets
need to have participation.

7
In above example, "Trans No" is a discriminator within a group of transactions in an
ATM. Let's learn more about a weak entity by comparing it with a Strong Entity

Strong Entity Set Weak Entity Set

Strong entity set always has a primary It does not have enough attributes to build
key. a primary key.
It is represented by a rectangle symbol. It is represented by a double rectangle
symbol.
It contains a Primary key represented by It contains a Partial Key which is
the underline symbol. represented by a dashed underline symbol.
The member of a strong entity set is The member of a weak entity set called as
called as dominant entity set. a subordinate entity set.
Primary Key is one of its attributes which In a weak entity set, it is a combination of
helps to identify its member. primary key and partial key of the strong
entity set.
In the ER diagram the relationship The relationship between one strong and a
between two strong entity set shown by weak entity set shown by using the double
using a diamond symbol. diamond symbol.
The connecting line of the strong entity The line connecting the weak entity set
set with the relationship is single. for identifying relationship is double.

2. Attribute
An attribute describes the property of an entity. An attribute is represented as Oval in
an ER diagram. There are four types of attributes:
1. Key attribute
2. Composite attribute
3. Multivalued attribute
4. Derived attribute

8
1. Key attribute:

A key attribute can uniquely identify an entity from an entity set. For example, student
roll number can uniquely identify a student from a set of students. Key attribute is
represented by oval same as other attributes however the text of key
attribute is underlined.

2. Composite attribute: An attribute that is a combination of other attributes is known

as composite attribute. For example, In student entity, the student address is a composite
attribute as an address is composed of other attributes such as pin code,
state, country.

3. Multivalued attribute:

An attribute that can hold multiple values is known as multivalued attribute. It is

represented with double ovals in an ER Diagram. For example – A person can have
more than one phone numbers so the phone number attribute is multivalued.

9
 4. Derived attribute:

A derived attribute is one whose value is dynamic and derived from another attribute. It
is represented by dashed oval in an ER Diagram. For example – Person age is a derived
attribute as it changes over time and can be derived from another attribute (Date of
birth).

E-R diagram with multivalued and derived attributes:

3. Relationship

Cardinality: Defines the numerical attributes of the relationship between two entities or
entity sets.

A relationship is represented by diamond shape in ER diagram, it shows the relationship

among entities. There are four types of cardinal relationships:
1. One to One
2. One to Many
3. Many to One
4. Many to Many

1. One to One Relationship

When a single instance of an entity is associated with a single instance of another entity
then it is called one to one relationship. For example, a person has only one passport
and a passport is given to one person.

10
2. One to Many Relationship

When a single instance of an entity is associated with more than one instances of
another entity then it is called one to many relationship. For example – a customer can
place many orders but a order cannot be placed by many customers.

3. Many to One Relationship

When more than one instances of an entity is associated with a single instance of
another entity then it is called many to one relationship. For example – many students
can study in a single college but a student cannot study in many
colleges at the same time.

4. Many to Many Relationship

When more than one instances of an entity is associated with more than one instances of
another entity then it is called many to many relationship. For example, a can be
assigned to many projects and a project can be assigned to
many students.

11
Total Participation of an Entity set

A Total participation of an entity set represents that each entity in entity set must have
at least one relationship in a relationship set. For example: In the below diagram each
college must have at-least one associated Student.

12
3.0 Steps to Create an ERD (E-R Digram)
Following are the steps to create an ERD.

Let's study them with an example:

In a university, a Student enrolls in Courses. A student must be assigned to at least one
or more Courses. Each course is taught by a single Professor. To maintain instruction
quality, a Professor can deliver only one course
Step 1) Entity Identification
We have three entities
 Student
 Course
 Professor

Step 2) Relationship Identification

We have the following two relationships

 The student is assigned a course
 Professor delivers a course

13
Step 3) Cardinality Identification
For them problem statement we know that,
 A student can be assigned multiple courses
 A Professor can deliver only one course

Step 4) Identify Attributes

You need to study the files, forms, reports, data currently maintained by the
organization to identify attributes. You can also conduct interviews with various
stakeholders to identify entities. Initially, it's important to identify the attributes without
mapping them to a particular entity.
Once, you have a list of Attributes, you need to map them to the identified entities.
Ensure an attribute is to be paired with exactly one entity. If you think an attribute
should belong to more than one entity, use a modifier to make it unique.
Once the mapping is done, identify the primary Keys. If a unique key is not readily
available, create one.

Entity Primary Key Attribute

Student Student_ID StudentName

Professor Employee_ID ProfessorName

Course Course_ID CourseName

14
For Course Entity, attributes could be Duration, Credits, Assignments, etc. For the sake
of ease we have considered just one attribute.

15
Step 5) Create the ERD
A more modern representation of ERD Diagram

Best Practices for Developing Effective ER Diagrams

 Eliminate any redundant entities or relationships
 You need to make sure that all your entities and relationships are properly labeled
 There may be various valid approaches to an ER diagram. You need to make
sure that the ER diagram supports all the data you need to store
 You should assure that each entity only appears a single time in the ER diagram
 Name every relationship, entity, and attribute are represented on your diagram
 Never connect relationships to each other
 You should use colors to highlight important portions of the ER diagram

Summary
 The ER model is a high-level data model diagram
 ER diagrams are a visual tool which is helpful to represent the ER model
 Entity relationship diagram displays the relationships of entity set stored in a database
 ER diagrams help you to define terms related to entity relationship modeling
 ER model is based on three basic concepts: Entities, Attributes & Relationships
 An entity can be place, person, object, event or a concept, which stores data
in the database

16
  Relationship is nothing but an association among two or more entities
 A weak entity is a type of entity which doesn't have its key attribute
 It is a single-valued property of either an entity-type or a relationship-type
 It helps you to defines the numerical attributes of the relationship
between two entities or entity sets
 ER- Diagram is a visual representation of data that describe how
data is related to each other
 While Drawing ER diagram you need to make sure all your entities
and relationships are properly labeled.

4.0 Course Outcomes Achieved

 Implement standard ER diagram by using notation.

 Implement various notation, attributes for ER diagram
 Gain Knowledge about The ER diagram

6.0 Actual Resources Used

Sr. no. Name of resource material Specifications Quantity

1 Computer System 16 GB RAM, Windows 10 OS 1

1
2 Textbook/Manual DBMS Database Management System 22319

17
 7.0 Skill Developed

1. Teamwork

2. Communication skills

4. Problem-solving skills.

5. Creativity.

6. Critical thinking skills.

8.0 Conclusion of this Micro-Project

 ER diagram can be used in database design, data modeling, system analysis

 It can be used to implement different Communication: Enhancing communication between
stakeholders about data structures and relationships.
 It can be used to implement different Education: Teaching and learning about data modeling and
databases.

18
19