Scribd
Upload
25 views3 pages

Design Your Own Database Activity

Uploaded by

Rose Marie Gepolani
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views3 pages

Design Your Own Database Activity

Uploaded by

Rose Marie Gepolani
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Advanced Database System - Lesson 1

Activity Instructions:
Activity: “Design Your Own Database World” 1. Choose a scenario from the list below (or
propose your own):
Objective:
Apply your knowledge of database models,  Online Food Delivery System
identifiers, and relationships by creating a  School Library Management System
mini-database design for a real-world  Hospital Patient Record System
scenario.  Real Estate Property Listing System
 Social Media Platform
Instructions:
1. Choose a scenario from the list below (or 2. Tasks:
propose your own): Step 1 – Identify Entities
List at least 3 entities relevant to your
 Online Food Delivery System chosen system.
 School Library Management System Step 2 – Define Attributes
 Hospital Patient Record System For each entity, list at least 3 attributes and
 Real Estate Property Listing System identify the Primary Key and possible Foreign
 Social Media Platform Key.
Step 3 – Determine Relationships
2. Tasks:
Step 1 – Identify Entities Describe how the entities are related and
List at least 3 entities relevant to your explain why.
chosen system. Step 4 – Choose a Database Model
Step 2 – Define Attributes Select the most suitable database model and
For each entity, list at least 3 attributes and justify your choice.
identify the Primary Key and possible Foreign Step 5 – Draw a Simple Diagram
Key. Create a basic ERD or schema diagram
Step 3 – Determine Relationships showing entities, attributes, and
Describe how the entities are related and relationships.
explain why.
Step 4 – Choose a Database Model
Select the most suitable database model and Advanced Database System - Lesson 1
justify your choice. Activity
Step 5 – Draw a Simple Diagram Activity: “Design Your Own Database World”
Create a basic ERD or schema diagram
showing entities, attributes, and Objective:
relationships. Apply your knowledge of database models,
identifiers, and relationships by creating a
mini-database design for a real-world
scenario.
Advanced Database System - Lesson 1
Activity
Instructions:
Activity: “Design Your Own Database World”
1. Choose a scenario from the list below (or
propose your own):
Objective:
Apply your knowledge of database models,  Online Food Delivery System
identifiers, and relationships by creating a  School Library Management System
mini-database design for a real-world  Hospital Patient Record System
scenario.
 Real Estate Property Listing System For each entity, list at least 3 attributes and
 Social Media Platform identify the Primary Key and possible Foreign
Key.
2. Tasks: Step 3 – Determine Relationships
Step 1 – Identify Entities
List at least 3 entities relevant to your Describe how the entities are related and
chosen system. explain why.
Step 2 – Define Attributes Step 4 – Choose a Database Model
For each entity, list at least 3 attributes and Select the most suitable database model and
identify the Primary Key and possible Foreign justify your choice.
Key. Step 5 – Draw a Simple Diagram
Step 3 – Determine Relationships Create a basic ERD or schema diagram
showing entities, attributes, and
Describe how the entities are related and relationships.
explain why.
Step 4 – Choose a Database Model
Select the most suitable database model and Advanced Database System - Lesson 1
justify your choice. Activity
Step 5 – Draw a Simple Diagram Activity: “Design Your Own Database World”
Create a basic ERD or schema diagram
showing entities, attributes, and Objective:
relationships. Apply your knowledge of database models,
identifiers, and relationships by creating a
mini-database design for a real-world
Advanced Database System - Lesson 1 scenario.
Activity
Activity: “Design Your Own Database World” Instructions:
1. Choose a scenario from the list below (or
Objective: propose your own):
Apply your knowledge of database models,
identifiers, and relationships by creating a  Online Food Delivery System
mini-database design for a real-world  School Library Management System
scenario.  Hospital Patient Record System
 Real Estate Property Listing System
Instructions:  Social Media Platform
1. Choose a scenario from the list below (or
propose your own): 2. Tasks:
Step 1 – Identify Entities
 Online Food Delivery System List at least 3 entities relevant to your
 School Library Management System chosen system.
 Hospital Patient Record System Step 2 – Define Attributes
 Real Estate Property Listing System For each entity, list at least 3 attributes and
 Social Media Platform identify the Primary Key and possible Foreign
Key.
2. Tasks: Step 3 – Determine Relationships
Step 1 – Identify Entities
List at least 3 entities relevant to your Describe how the entities are related and
chosen system. explain why.
Step 2 – Define Attributes Step 4 – Choose a Database Model
Select the most suitable database model and Advanced Database System - Lesson 1
justify your choice. Activity
Step 5 – Draw a Simple Diagram Activity: “Design Your Own Database World”
Create a basic ERD or schema diagram
showing entities, attributes, and Objective:
relationships. Apply your knowledge of database models,
identifiers, and relationships by creating a
mini-database design for a real-world
scenario.
Advanced Database System - Lesson 1
Activity
Activity: “Design Your Own Database World” Instructions:
1. Choose a scenario from the list below (or
Objective: propose your own):
Apply your knowledge of database models,  Online Food Delivery System
identifiers, and relationships by creating a  School Library Management System
mini-database design for a real-world  Hospital Patient Record System
scenario.  Real Estate Property Listing System
 Social Media Platform
Instructions:
1. Choose a scenario from the list below (or 2. Tasks:
propose your own): Step 1 – Identify Entities
 Online Food Delivery System List at least 3 entities relevant to your
 School Library Management System chosen system.
 Hospital Patient Record System Step 2 – Define Attributes
 Real Estate Property Listing System For each entity, list at least 3 attributes and
 Social Media Platform identify the Primary Key and possible Foreign
Key.
2. Tasks: Step 3 – Determine Relationships
Step 1 – Identify Entities Describe how the entities are related and
List at least 3 entities relevant to your explain why.
chosen system. Step 4 – Choose a Database Model
Step 2 – Define Attributes Select the most suitable database model and
For each entity, list at least 3 attributes and justify your choice.
identify the Primary Key and possible Foreign Step 5 – Draw a Simple Diagram
Key. Create a basic ERD or schema diagram
Step 3 – Determine Relationships showing entities, attributes, and
Describe how the entities are related and relationships.
explain why.
Step 4 – Choose a Database Model
Select the most suitable database model and
justify your choice.
Step 5 – Draw a Simple Diagram
Create a basic ERD or schema diagram
showing entities, attributes, and
relationships.

Common questions

Powered by AI

Primary and foreign keys are crucial in a database schema because they establish unique identifiers for entities, ensuring each record within a table can be uniquely identified. Primary keys enforce entity integrity by preventing duplicate records, while foreign keys maintain referential integrity by linking tables and establishing relationships. This linkage allows for efficient joins and relationship mappings, crucial for complex queries and data consistency .

In a Social Media Platform, the 'User' entity might include attributes like UserID (Primary Key), Username, Email, and Password. In contrast, the 'Post' entity might include PostID (Primary Key), UserID (Foreign Key), Content, and Timestamp. Storage implications include needing flexible and scalable storage solutions for potentially large and variable 'Content' fields in Posts, alongside ensuring efficient access controls and data retrieval across extensive User databases .

Determining a primary key for a complex entity involves ensuring the key is unique, stable, and minimal. Considerations include avoiding sensitive data (e.g., using a CustomerID instead of Social Security Number), evaluating natural versus surrogate keys for clarity and simplicity, and ensuring scalability and efficiency, especially in large datasets. The stability of a primary key is pivotal, as changing it can lead to data integrity issues across related tables .

An Entity-Relationship Diagram (ERD) is a visual representation of a database's components and their relationships. It is crucial for project design because it provides a clear and concise picture of the entire database structure, aiding stakeholders in understanding data flow, relationships, and system limits. ERDs facilitate communication among team members, highlight design issues early, and serve as a blueprint for database implementation .

In a Hospital Patient Record System, entity relationships are highly structured, focusing on one-to-one or one-to-many relationships, such as a Doctor having many Patients or a Patient having multiple Medical Records. These relationships emphasize data accuracy and integrity. Conversely, a Social Media Platform involves more complex, many-to-many relationships with entities like User and Post, where a User can have multiple Posts and interact with other Users’ activities, reflecting dynamic and less structured interactions .

Challenges in defining attributes for a Real Estate Property Listing System include ensuring comprehensive property descriptions, handling varied data types (e.g., numerical for prices, text for descriptions), and capturing changing attributes like pricing and availability. These can be mitigated by conducting thorough domain analysis to cover all possible attributes, employing data validation techniques, and using flexible yet structured schemas that accommodate regular updates without compromising data integrity .

Using a relational database model for a School Library Management System offers advantages such as strong ACID transaction support, which ensures data consistency and integrity. It facilitates complex querying capabilities and precise data integrity through well-defined relationships and constraints, which might be less straightforward in a NoSQL model. This is particularly beneficial for systems needing structured, interrelated datasets, such as tracking book loans, returns, and penalties .

The choice of database model significantly impacts the handling of relationships between entities. In a Real Estate Property Listing System, a relational database model facilitates structured many-to-many relationships between properties, agents, and clients through join tables and foreign keys. An object-oriented or NoSQL database might offer more flexibility and scalability, allowing for hierarchical data embedding, beneficial when dealing with nested or unstructured data. The choice affects transaction integrity, data retrieval speed, and ease of relationship management .

For an Online Food Delivery System, key entities could include 'Customer', 'Order', and 'Restaurant'. The 'Customer' entity might have attributes such as CustomerID (Primary Key), Name, and Address. The 'Order' entity could have OrderID (Primary Key), CustomerID (Foreign Key), and RestaurantID (Foreign Key). The 'Restaurant' entity might include attributes like RestaurantID (Primary Key), Name, and Location. Relationships between these entities could include Customers placing Orders, and an Order being fulfilled by a Restaurant. This setup illustrates a one-to-many relationship from Customer to Order, and potentially a many-to-many relationship via Orders to Restaurants .

To select a suitable database model for a School Library Management System, criteria would include the complexity of data relationships, need for ACID transactions, scalability requirements, and the efficiency of query operations. A relational database model might be preferred due to its structured schema and support for complex queries, which are ideal for managing entities like Books, Students, and Loans with many-to-many relationships between them .

You might also like