Conceptual Data Modeling using the ER Model Flashcards

Flashcards generated from the Conceptual Data Modeling using the ER Model lecture transcript covering database design phases, ER concepts, attributes, entity types, relationships, and ER features.

Database Design

The process of creating a database that correctly represents the real-world and supports all the functions and data required by users.

Miniworld

The specific part of the real world that is to be represented in the database.

Requirements Collection and Analysis

The phase in which database designers collect information from prospective users through interviews, forms, and discussions to understand what data should be stored and how it will be used.

Data Requirements

Requirements that specify the type of data to be stored in the database, such as student marks, name, roll number, and course.

Functional Requirements

Requirements that specify what operations will be performed on the data, such as inserting a new student or updating exam marks.

Conceptual Design

The phase where a high-level conceptual schema is created to represent entities, attributes, relationships, and constraints.

Functional Analysis and High-Level Transaction Specification

The stage where required database transactions are specified in detail at a conceptual level without concerning SQL or DBMS commands.

Logical Design (Data Model Mapping)

The phase where the conceptual schema is converted or mapped into the data model of a specific DBMS, such as mapping an ER diagram into relational tables.

Physical Design

The phase that deals with internal storage structures and access methods, such as indexing fields for quick searches.

Application Program Design and Implementation

The process, developed in parallel with database design steps, of creating programs containing the actual database transactions that users will run.

Entity-Relationship (ER) Model

A popular data model introduced by Peter Chen in 1976, used during conceptual design to describe real-world objects as entities and connections between them as relationships using diagrams.

Entity

Any real-world object or concept that has an independent identity and about which data can be stored in a database.

Physical Entities

Objects with physical existence that can be seen and touched, such as a lecturer, student, or car.

Abstract Entities

Objects with conceptual existence that cannot be physically touched but are important for the system, such as a course, job, or bank account.

Attribute

A property or characteristic that describes an entity.

Simple Attribute

An attribute that holds only one single value and cannot be divided further, such as age or gender.

Composite Attribute

An attribute that can be broken down into smaller parts, such as an address divided into street, city, state, and zipcode.

Single-valued Attribute

An attribute that can have only a single value for an entity, such as date of birth.

Multi-valued Attribute

An attribute that can have multiple values for a single entity, such as multiple phone numbers or degrees.

Stored Attribute

An attribute that supplies a value to a related attribute, such as date of birth used to determine age.

Derived Attribute

An attribute whose value is derived from a stored attribute, such as age calculated by subtracting date of birth from the current date.

Complex Attribute

An attribute that is both composite and multi-valued.

Null Value Attribute

An attribute that may not have a value for a particular entity, such as an apartment number.

Entity Type

A group of entities that share the same set of attributes, defining the structure for storing similar kinds of information.

Entity Sets

A collection of entities that belong to the same entity type and hold actual data entries at a particular point in time, also called the extension of an entity type.

Strong Entity

An entity type that has its own primary key which can uniquely identify every entity in that set.

Weak Entity

An entity type that does not have a primary key of its own and depends on another strong entity to be uniquely identified.

Key Attribute

An attribute that uniquely identifies each entity in an entity set.

Domain of an Attribute

The set of valid values that an attribute can take, also known as a Value Set.

Relationship

An association between two or more entities that shows how they interact or are related, usually represented by a verb.

Relationship Type

The logical association between two or more entity types.

Relationship Instance

A real-time example or actual data of a relationship connecting specific entities at a given moment.

Relationship Set

A collection of all relationship instances of the same relationship type.

One-to-One Relationship (1:1)

A relationship where one entity from Entity A is associated with only one entity from Entity B, and vice versa.

One-to-Many Relationship (1:N)

A relationship where one entity from Entity A is related to many entities from Entity B.

Many-to-One Relationship (M:1)

A relationship where many entities from Entity A are associated with one entity from Entity B.

Many-to-Many Relationship (M:N)

A relationship where multiple entities from Entity A are related to multiple entities from Entity B.

Degree of Relationship

Refers to the number of entity types involved in a relationship type.

Binary Relationship

A relationship type that connects two entity types (degree 2).

Ternary Relationship

A relationship type involving three entity types (degree 3).

n-ary Relationship

A relationship type involving four or more entity types.

Role Name

A name used to clarify the participation of entities in a relationship, written in lowercase letters.

Recursive Relationship

A type of relationship where the same entity type participates more than once in different roles.

ER Diagram

The graphical representation of organizational system elements and the associations among those elements.

Associative Entity

An entity created to join two entities in an ER model.

Identifying Relationship

A relationship that relates a weak entity type to specific entities from a strong entity type to uniquely identify it.

Optionality

Expresses whether a relationship is optional or mandatory.

Cardinality

Expresses the maximum number of relationships in an association.

Abstraction

A method used to simplify real-world objects by keeping only important information and ignoring unnecessary details.

Specialization

The process of dividing a general entity set into smaller sub-entities based on distinguishing features.

Generalization

The process of combining two or more entities into one higher-level entity by identifying their common attributes.

Aggregation

An abstraction concept where a relationship itself is treated as an entity so that it can be connected with another entity.