Slides - Tagged

Title and Author

CIS 4365 Database Management Renjie Hu

Data Definition

Facts and symbols, e.g., series of numeric values. Examples: 31, 17, 1, -1, -9, 35.

Information Definition

Data that is understandable and meaningful, illustrated with temperature records: High °F, Low °F by month and their equivalent in °C.

Knowledge Definition

Data that is useful for decision-making, presented similarly to temperature data.

Wisdom Definition

A deeper understanding of knowledge, exemplified by average temperatures in Chicago by month, providing context for the data.

DIKW Pyramid

Hierarchy illustrating the transformation from raw data to deeper understanding: Data, Information, Knowledge, Wisdom.

Database Design Problem 1

Table Overview: Employee records with columns for employee number, name, rank, salary, manager. Problem: Identifying data issues.

Database Design Problem 2

Redundancy Issue: Data duplication among records.

Database Design Problem 3

Update Anomaly: Challenges when updating employee information across duplicated records.

Database Design Problem 4

Insertion Anomaly: Issues while adding new records resulting in incomplete data entries.

Database Design Problem 5

Deletion Anomaly: Loss of necessary data due to deletion of records.

Desirable Database Characteristics

Integrated Data: Data should be connected and not isolated. Data Independence: Application immunity to storage structure changes and access strategies.

ER Model Purpose

A grammar for conceptual modeling.

Database Design: ER Model

Emphasis on building relationships between data through ER models.

ER Model Details

History: Proposed by Peter Chen in 1976, became ANSI standard in 1988 for IRDS. Properties: expressiveness, simplicity, minimality.

ER Model Uses

Communication Tool for analysts to present ideas to end-users; Design Tool for high-level abstraction for understanding.

ER Modeling Components

Entities, Attributes, Relationships.

ER Diagram Definition

Visual representation of data relationships. Elements: Entities = tables, Attributes = columns, Relationships = lines.

Entity in ER Model

Entity Type: Conceptual representation of an object type with related attributes. Types: Base and Weak entities. Entity Set: Collection of entity instances.

Understanding Entity

Entities: Objects or events stored in a database. Instance: A record or row of an entity in a database.

Identifying Entities

Guidelines: Look for nouns representing people, places, or things; avoid proper nouns.

Entity Instance Examples

List of students with ID numbers, names, and other identifiers.

Identifying Attributes

Definition: Descriptive data associated with entities. Identification Process: Focused on descriptive nouns.

Attribute Representation

Conceptual Attributes: Properties describing an object type.

Composite Attribute Example

Related to albums, distinguishing between single-valued and multi-valued attributes.

Multi-valued Attributes Example

Example of multi-valued attribute with several related artists.

Unique Identifier and Key Attribute Definitions

Unique identifier: Distinct values for each entity. Key attribute: Part of the unique identifier. Non-key attribute: Not part of a unique identifier.

Identifiers

Primary Key: Attributes that uniquely identify entity instances.

Relationships in ER Model

Definition: Associations/actions between entities, typically using a verb. Cardinality Types: One-to-one, one-to-many, etc.

Foreign Keys in ERD

Role: Links two tables, enforcing referential integrity.

Understanding Cardinality Definition

Cardinality: Number of occurrences between entity relationships. Basic Types: 1:1, 1:M, M:N.

Foreign Keys and Relationships

Types of Relationships: One-to-One, One-to-Many, Many-to-Many, with implications for table design.

ERD Representation Details

Visually depicts relationships and types between entities.

Example Model

Basic ER model illustrations showcasing entities and relationships.

Crow’s Foot Notation Overview

Depicts entities as rectangles with singular names.

Attributes Representation Highlighting

Attributes emphasized, underscoring their role in entity description.

Relationship and Cardinality Overview

Relationships represented, including cardinality aspects.

Many-to-Many Relationships Management

Need for associative entities to handle many-to-many relationships effectively.

Business Rule Overview

Specific conditions relevant to the domain being modeled, crucial in requirements gathering.

More on Business Rules Categories

Categories: Explicit, Inferred, and Ambiguities needing clarification.

Exemplar Vignette

Emphasizes practical examples to understand concepts.

Examples of Business Rules

Explicit Rules: Operational conditions, course offerings, instructor availability.

Inferred Business Rules Example

Assumptions deduced from explicit rules regarding instructor responsibilities.

Ambiguities Needing Clarification Examples

Questions about course offerings and instructor roles requiring user input.

Bi-Directional Business Rules Importance

Business rules should reflect mutual relationships and responsibilities.

Utilizing Business Rules Purpose

Define entities, attributes, relationships, and constraints within a database context.

Creating Effective Business Rules Guidelines

Keep rules simple and broadly understood; gather from diverse sources.

Real World Example Application

Example of developing business rules through data collection and iterative refinement.

Business Rules Example 2 Key Relationships

Descriptions of relationships between sales representatives, departments, and invoices.

Continuation of Business Rules Example 2

Reinforcement of same relationships, emphasizing clarity in conditions.

Overview of University Structure Components

Students, courses, instructors, departments, and advisors as interconnected entities.

Continuation of Overview Registration System

Detailed paths linking students with courses and tracking their progress.