0% found this document useful (0 votes)
21 views4 pages

Task2 Prado PC5

An ER diagram visually represents the relationships between entities in a database using symbols and notations. It is used for database design, communication, and documentation. An ER diagram shows entities, attributes, relationships, and cardinality. Entities are represented by rectangles, attributes by ovals, relationships by diamonds, and cardinality by notations like 1 or M.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views4 pages

Task2 Prado PC5

An ER diagram visually represents the relationships between entities in a database using symbols and notations. It is used for database design, communication, and documentation. An ER diagram shows entities, attributes, relationships, and cardinality. Entities are represented by rectangles, attributes by ovals, relationships by diamonds, and cardinality by notations like 1 or M.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1.

ER Diagram (Entity-Relationship Diagram):

An ER diagram is a visual representation of the relationships between entities (objects, concepts, or


things) in a database. It uses various symbols and notations to illustrate how these entities are related to
each other.

2. Uses of ER Diagram:

- Database Design: ER diagrams help in designing the structure of a database by defining entities, their
attributes, and how they relate.

- Communication: They facilitate communication between stakeholders, including developers,


designers, and business analysts.

- Documentation: ER diagrams serve as documentation for understanding and maintaining the


database over time.

3. Components and Features of an ER Diagram:

- Entities: Represent objects, concepts, or things in the database (e.g., "Customer" or "Product").

- Attributes: Characteristics or properties of entities (e.g., "Customer Name" or "Product Price").

- Relationships: Connections between entities, indicating how they are associated (e.g., "Customer
buys Product").

- Cardinality: Indicates the number of instances in one entity related to another (e.g., one-to-one, one-
to-many, or many-to-many).

4. ER Diagram Symbols and Notation:

- Entity: Shown as a rectangle with the entity name.

- Attribute: Represented by ovals connected to entities.

- Relationship: Displayed as a diamond shape connecting entities.

- Cardinality: Notations like "1" or "M" are used to specify cardinality.


5. Conceptual, Logical, and Physical Data Models:

- Conceptual Data Model: Provides a high-level view of the data without going into technical details. It
focuses on concepts and relationships. Example: An ER diagram representing "Library System" with
entities like "Book" and "Borrower."

- Logical Data Model: Represents the data at a more detailed level, including attributes, keys, and
relationships. It is independent of the specific database management system. Example: Adding attributes
like "Author" and "ISBN" to the "Book" entity in the Library System ER diagram.

- Physical Data Model: Defines how the data will be stored and structured in a specific database
system. It includes details like data types, indexing, and storage optimization. Example: Specifying table
structures and constraints for "Book" and "Borrower" in a MySQL database.
ER Diagram for Student-University Setup

You might also like