The document outlines the design requirements for various Entity-Relationship (ER) diagrams for different systems, including Online Shopping, University Research Management, Hospital Management, Library Management, Hotel Booking, Car Rental, Social Media, Banking, and Food Delivery. Each system includes specific entities, attributes, and relationships, such as customers, orders, products, professors, students, appointments, books, guests, cars, users, accounts, and restaurants. The relationships detail how entities interact, such as customers placing orders, professors supervising students, and patients having appointments.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
9 views3 pages
Sheet 1 ERD
The document outlines the design requirements for various Entity-Relationship (ER) diagrams for different systems, including Online Shopping, University Research Management, Hospital Management, Library Management, Hotel Booking, Car Rental, Social Media, Banking, and Food Delivery. Each system includes specific entities, attributes, and relationships, such as customers, orders, products, professors, students, appointments, books, guests, cars, users, accounts, and restaurants. The relationships detail how entities interact, such as customers placing orders, professors supervising students, and patients having appointments.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3
Sheet 1: ER Diagram
Design an ER diagram for the following. Your ER diagram must show entities, attributes and the relationships between entities
1- Online Shopping System
An e-commerce website needs a database to store information about customers, orders, and products with the following information. 1- A customer has a customer ID, name, email, phone number, and address. 2- A product has a product ID, name, description, price, and stock quantity. 3- An order has an order ID, order date, and total price. 4- A customer can place multiple orders, but each order belongs to only one customer 5- An order can contain multiple products, and each product can be in multiple orders. 6- The quantity of each product in an order must be recorded. 2- University Research Management System A university wants to manage professors, students, research projects, and publications. 1- A professor has a professor ID, name, department, and specialization. 2- A student has a student ID, name, degree program, and year of study. 3- A research project has a project ID, title, start date, end date, and funding amount. 4- A publication has a publication ID, title, publication date, and journal name. 5- A professor can supervise multiple students, but each student has only one supervisor. 6- A professor can work on multiple research projects, and a research project can have multiple professors. 7- A student can be assigned to multiple research projects, and a research project can have multiple students. 8- A professor or student can publish multiple research papers, and each publication can have multiple authors. 3- Hospital Management System A hospital wants to create a database to track patients, doctors, and appointments. 1. A patient has a patient ID, name, date of birth, gender, and contact details. 2. A doctor has a doctor ID, name, specialization, and years of experience. 3. An appointment has an appointment ID, date, time, and purpose. 4. A patient can have multiple appointments, and each appointment is for only one patient 5. A doctor can have multiple appointments, but each appointment is with only one doctor 4- Library Management System: A library wants to manage books, members. 1. A book has a book ID, title, author, publisher, and publication year. 2. A member has a member ID, name, email, and phone number. 3. A member can borrow multiple books, and each book can be borrowed by multiple members over time 4. The borrowing date and return date must be recorded. 5- Hotel Booking System A hotel needs a system to store guest, room, and booking information. 1. A guest has a guest ID, name, phone number, and email. 2. A room has a room ID, type (single/double), and price per night. 3. A booking has a booking ID, check-in date, check-out date, and total cost. 4. A guest can make multiple bookings, but each booking is for only one guest 5. A room can be booked multiple times, and each booking is for one room. 6- Car Rental System A car rental company wants to track customers, cars, rentals, and payments. 1- A customer has a customer ID, name, driver’s license number, phone, and email. 2- A car has a car ID, model, brand, year, and rental price per day. 3- A rental has a rental ID, start date, end date, total amount, and status (active, completed, canceled). 4- A customer can rent multiple cars, but each rental belongs to only one customer 5- A rental can include only one car, but a car can be rented multiple times over time. 6- A payment has a payment ID, rental ID, payment date, amount, and payment method. 7- A rental must have at least one payment, but multiple payments may be made for one rental 7- Social Media Platform: A social media platform needs a database to store users, posts, comments, likes, and friendships. 1- A user has a user ID, name, email, and date of birth. 2- A post has a post ID, content, timestamp, and user ID. 3- A comment has a comment ID, content, timestamp, user ID (foreign key), and post ID (foreign key). 4- A like has a like ID, user ID, and post ID 5- A user can make multiple posts, and each post belongs to only one user. 6- A user can comment on multiple posts, and each comment belongs to only one post and one user 7- A user can like multiple posts, and each post can be liked by multiple users 8- A friendship stores user ID1, user ID2, and status (pending, accepted, blocked). 8- Banking System A bank wants to track customers, accounts, transactions, and employees. 1- A customer has a customer ID, name, address, email, and phone number. 2- An account has an account ID, account type (savings, checking), balance, and customer ID. 3- A transaction has a transaction ID, transaction type (deposit, withdrawal, transfer), amount, date, and account ID. 4- An employee has an employee ID, name, role (teller, manager), and branch. 5- A customer can have multiple accounts, but each account belongs to only one customer. 6- An account can have multiple transactions, but each transaction belongs to only one account. 7- An employee can handle multiple transactions, but each transaction is processed by only one employee. 9- Food Delivery System: A food delivery app tracks restaurants, customers, orders, and delivery person. 1- A restaurant has a restaurant ID, name, address, and cuisine type. 2- A customer has a customer ID, name, phone number, and delivery address. 3- An order has an order ID, customer ID (foreign key), restaurant ID (foreign key), order date, and total price. 4- A delivery person has a delivery ID, name, phone number, and vehicle type. 5- A restaurant can receive multiple orders, but each order belongs to only one restaurant. 6- A customer can place multiple orders, but each order belongs to only one customer. 7- A delivery person can deliver multiple orders, but each order is assigned to only one delivery person.