Database Design Flashcards
These include tables, columns (fields), data types, keys (primary and foreign), and relationships.
Structures
The core unit where data is stored in rows and columns. Each table
represents an entity (e.g., customers, products).
Tables
CustomerName, CustomerAge, CustomerHeight are characteristics of entities also referred to as _______.
Attributes/Columns/Fields
Establishes a relationship between two tables.
Foreign Key
These are the constraints that enforce data integrity and business
logic.
define how data can be created, stored, and manipulated, ensuring that
operations align with organizational policies.
Business Rules
Enforced directly within the database through constraints, triggers, and stored
procedures.
Example: A university database enforces that a student cannot register for
more than 21 credits per semester. This can be implemented using a trigger
that checks the total credits during registration.
Database-oriented Business Rules
Implemented within the application logic rather than directly in the database.
Example: An e-commerce platform may restrict product returns to within 30
days of purchase. This rule is enforced by the application’s order management
module rather than the database itself.
Application-oriented Business Rules
the specifications that the database must fulfill to align with business needs and user expectations. This phase involves gathering and analyzing data requirements from stakeholders to define
Database Requirements
These describe what the database should do for users to accomplish their tasks (e.g., storing customer orders, managing employee records).
Functional Requirements
These are set of specifications that describe the system’s operation capabilities and constraints
Non-functional Requirements
3 Non-Functional Requirements
Hint: PSS
Performance
Scalability
Security
Using indexing to optimize query performance. Which of the 3 Non- Funtional Requirements does this consider?
Performance
Design the database to accommodate increasing data volume.
Scalability
Implement user access control and data encryption.
Security
Criteria of a Good Database Design
Ensures data integrity, efficiency, and scalability.
Ensures that data remains accurate and consistent across tables and transactions.
Data Integrity and Consistency
Eliminates redundancy and improves data integrity by organizing
tables so that each table contains data related to a single entity or concept.
Normalization
The database should be designed to handle growth in data volume and
user load.
Scalability
refers to the correctness, consistency, and accuracy of data in a database. It
ensures that data remains reliable and valid over its lifecycle.
Data Integrity
Ensures that each row in a table is uniquely identifiable.
Entity Integrity
Ensures that relationships between tables remain consistent.
Referential Integrity
Ensures that the values in a column fall within a specified range, type, or set.
Domain Integrity