Abhi333 Dbms
Abhi333 Dbms
Abhi333 Dbms
3. 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 the E-R diagram.
3. Brief study on our topic.
4. Gather all information based on the topic of the micro project
4. Resources used:
1
3 textbook/manual DBMS Data Management System
Micro-Project Report
1. Brief Introduction/Rationale:
An Entity–relationship model (ER model) defines the structure
of a database with the aid of a diagram, which is known as an Entity
Relationship Diagram (ER Diagram). An ER model is a design or blueprint of a
database that can later be executed as a database. The major components of the
E-R model are the entity set and relationship set.
1. Entity
2. Attribute
3. Relationship
1. Entity:
An entity is an object or element of data. An entity is described as a
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, but for
now, concentrate on entities.
Weak Entity:
An entity that cannot be uniquely determined by its own attributes and
relies on the relationship with another entity is called a weak entity. The weak
entity is defined by a double rectangle. For example bank account cannot be
uniquely determined without knowing the bank to which the account belongs,
so bank account is a weak entity.
2. Attribute:
An attribute defines the property of an entity. An attribute is
expressed as an Oval in an ER diagram. There are four kinds of attributes:
1. Key attribute
2. Composite attribute
3. Multivalued attribute
4. Derived attribute
1. Key attribute:
2. Composite attribute:
An attribute that is a mixture of other attributes is known as a
composite attribute. For example, In a student entity, the student address is a
composite attribute as an address is composed of other attributes such as pin
code, state, and country.
3. Multivalued attribute:
An attribute that can carry multiple values is known as a
multivalued attribute. It is described with double ovals in an ER Diagram. For
example – A person can have more than one phone number so the phone
number attribute is multivalued.
4. Derived attribute:
A derived attribute is one whose value is dynamic and derived
from another attribute. It is defined by a dashed oval in an ER Diagram. For
example – A person's age is a derived attribute as it varies over time and can be
derived from another attribute (Date of birth).
1. One to One
2. One to Many
3. Many to One
4. Many to Many
1. One-to-One Relationship:
3. Skill Developed:
1. Teamwork
2. Communication skills
3. Able to get all information about ER Diagram
Conclusion:
An entity-relationship diagram, or ER diagram, is important for
modeling the data held in a database. It is the basic design upon which a
database is built. ER diagrams identify what data we will store: the entities and
their attributes. They also illustrate how entities relate to other entities.