Data and databases

Data refers to raw, unprocessed facts and figures without context or meaning. Information is processed data that has been organized and given context, making it meaningful and useful for decision-making.

Databases are organized collections of structured data stored electronically, designed for efficient retrieval, management, and updating. A Database Management System (DBMS) is software that facilitates creating, maintaining, and querying databases.

Key Database Terminology:

Entity - A distinct object or concept about which data is stored (e.g., Student, Product)

Attribute - A characteristic or property of an entity (e.g., StudentName, ProductPrice)

Primary Key - A unique identifier for each record in a table, ensuring no duplicates exist

Foreign Key - An attribute in one table that references the primary key of another table, establishing relationships

Relational Database - Data organized into tables (relations) with rows (records/tuples) and columns (attributes/fields), linked through keys

Flat File Database - A single-table database storing all data in one structure, suitable only for simple applications

Normalization - The process of organizing data to minimize redundancy and dependency, typically through First Normal Form (1NF), Second Normal Form (2NF), and Third Normal Form (3NF)

Data Integrity - Ensuring accuracy, consistency, and reliability of data throughout its lifecycle

Validation - Checking data meets specified rules before entry (e.g., range check, type check)

Verification - Confirming data has been accurately transferred or entered (e.g., double-entry, visual check)

Cambridge Command Words: Define requires precise, concise explanations. Explain demands reasoning with cause-and-effect. Describe needs characteristics without justification.

Think of data versus information like ingredients versus a recipe. Raw numbers "25, 12, 2023" are data—meaningless alone. Processed as "25th December 2023" becomes information with context.

Real-World Database Applications:

E-commerce platforms like Amazon use relational databases with entities: Customer, Order, Product, Payment. A customer's order connects through foreign keys—CustomerID in the Order table references the Customer table's primary key. This prevents storing duplicate customer addresses for each order (redundancy reduction).

School Management Systems demonstrate normalization beautifully. Instead of one massive table repeating teacher details for every class they teach, separate tables exist: Teacher (TeacherID, Name, Department), Class (ClassID, Subject, TeacherID). The TeacherID foreign key links them, eliminating data duplication.

Healthcare databases prioritize data integrity. A patient's blood type must validate against permitted values (A, B, AB, O) with + or - modifiers. Verification through double-entry by different medical staff catches critical errors.

Flat files versus relational databases: Imagine a spreadsheet listing students with their courses—each student-course combination repeats student details (name, email, address). This flat file causes update anomalies: changing a student's email requires finding every row they appear in. A relational approach splits this into Student and Course tables linked through an Enrollment table, updating email once.

Primary keys in practice: Your passport number uniquely identifies you globally—it's your primary key in immigration databases. No two people share it, ensuring accurate tracking. Similarly, ISBNs uniquely identify books, preventing confusion between editions.

Memory Aid - ACID properties: Atomicity, Consistency, Isolation, Durability ensure reliable database transactions—like a complete bank transfer (not half-processed).

Example 1: Normalization to 3NF

Question: Normalize this table to Third Normal Form:

Solution:

Step 1 - 1NF: Already achieved (atomic values, no repeating groups, primary key exists)

Step 2 - 2NF: Remove partial dependencies. Composite key (StudentID, CourseID) exists. CourseName depends only on CourseID (partial dependency). Split:

Student_Course Table: StudentID, CourseID

Course Table: CourseID (PK), CourseName, InstructorName

Step 3 - 3NF: Remove transitive dependencies. InstructorName depends on CourseID through CourseName (not directly on key). Final structure:

Enrollment: StudentID (FK), CourseID (FK)

Student: StudentID (PK), StudentName

Course: CourseID (PK), CourseName, InstructorID (FK)

Instructor: InstructorID (PK), InstructorName

Examiner Note: Award marks for identifying dependency types and systematic progression through normal forms.

Example 2: Validation vs. Verification

Question (4 marks): Explain the difference between validation and verification, giving one example of each.

Model Answer:

Validation checks data meets predefined rules before entry [1], such as a range check ensuring age values between 0-120 [1]. Verification confirms data has been accurately entered or transferred [1], such as double-entry password systems requiring identical inputs twice [1].

Examiner Tip: Clear distinction + specific, relevant examples = full marks.