Demonstrate understanding of database models

The hierarchical database model organizes data in a tree-like structure with parent-child relationships, where each parent can have multiple children but each child has only one parent. This model resembles an organizational chart or a file directory system.

Key characteristics:

• Data is organized in levels or segments
• Each child segment has only one parent
• Navigation is from parent to child along specific paths
• Efficient for representing one-to-many relationships

Practical example: In a school administration system, the hierarchy might be: School → Form → Class → Student. A form (like Form Five) contains multiple classes, and each class contains multiple students.

Limitations: This model cannot represent many-to-many relationships effectively and requires careful planning of the tree structure.

The network database model extends the hierarchical structure by allowing each child segment to have multiple parent segments, creating a network or graph-like structure. This enables representation of many-to-many relationships.

Key characteristics:

• Data is organized like a network with multiple connections
• Allows many-to-many relationships between data items
• Accessing data is faster because multiple paths exist
• More flexible than the hierarchical model
• Redundancy is managed more efficiently than in hierarchical approach

Practical example: In a university system, a student can enroll in multiple courses, and each course can have multiple students—this many-to-many relationship is handled efficiently in the network model. Additionally, a student may have multiple instructors, and an instructor may teach multiple students.

Historical context: This was the most extensively used database model before the introduction of the relational model.

The relational database model represents data in two-dimensional tables called relations, with data organized in rows and columns. This is currently the most widely used database model globally.

Key characteristics:

• Data is organized in tables (relations) with rows and columns
• Each row represents a record (tuple), and each column represents an attribute
• Tables can be connected based on common attributes
• Simple structure that is easily scalable
• Uses SQL (Structured Query Language) for data manipulation

Practical example: A student table might include columns for StudentID, Name, DateOfBirth, and Address, with each row representing an individual student.

Advantages:

• Simple model that is easy to understand and query
• Data accuracy through primary and foreign keys
• Easy data access without fixed patterns
• Data integrity and flexibility
• High security through access controls

The object-oriented database model represents both data and relationships in a single structure called an object. This model better represents real-world problems by combining data and behavior.

Key characteristics:

• Data and methods are stored together in objects
• Supports complex data types (music, video, photographs)
• Objects with properties and methods are linked together
• Compatible with object-oriented programming languages
• Suitable for applications requiring multimedia data

Practical example: An employee object might have properties like Name, Position, and Salary, along with methods like "CalculateBonus" or "UpdateRecord." This is similar to objects in programming languages such as Java or Python.

Comparison with relational: Unlike relational databases that are table-oriented, object-oriented databases can store complex data types that were not efficiently handled in traditional relational systems.

The Entity-Relationship (ER) model is a conceptual framework used for database design, illustrating the database structure through entities, attributes, and relationships. It serves as a blueprint for database implementation.

Key components:

Entities: Real-world objects or concepts stored in the database, such as students, courses, or products. They are represented as tables within the database.

Attributes: Properties or characteristics of entities, such as names, ages, or prices. They are represented as columns within entity tables.

Relationships: How entities interact or associate with each other, including:

• One-to-one: One entity associates with exactly one other entity
• One-to-many: One entity associates with multiple entities
• Many-to-many: Multiple entities associate with multiple entities

ER Diagram: A visual representation using symbols like rectangles (entities), diamonds (relationships), and ovals (attributes) to depict database structure.

Practical example: In a university database:

• Entities: Student, Course, Professor
• Relationships: A student enrolls in courses; a professor delivers courses
• Attributes: Student (StudentID, Name), Course (CourseID, Title), Professor (EmployeeID, Name)

The flat file database model stores all data in a single table, similar to a basic spreadsheet or list. This is the simplest form of database organization.

Key characteristics:

• All data is stored in one table
• Easy to create and understand
• Suitable for simple data storage needs
• Becomes cumbersome with complex relationships

Practical example: A simple list of student names stored in a single column. However, this model cannot effectively show which students belong to which class or combination.

Limitations: When data relationships become complex (like tracking which student takes which subjects), flat files become inefficient and lead to data redundancy.

In Tanzania, database models are used extensively in systems like the National Identification Authority (NIDA) database, which uses a relational model to store citizen information, and mobile banking systems like M-Pesa use database models to manage millions of transactions daily. A student might encounter this when their school's exam results system uses a relational database to link students to their subjects and scores, allowing efficient retrieval of report cards.