3. Consider the following scenario of a Bus Ticket Reservation System. The system is responsible for allowing customers to search for available bus routes, select seats, make reservations, and manage their bookings. The system should also keep track of the buses, routes, reservations, and customers. In this system, a bus company operates multiple Buses. Each Bus belongs to one Bus Company. A bus company has a unique identifier - company_id along with other attributes such as name, address, contact_info. A bus is identified by bus_id. It may also have a registration number, model and seat capacity. Each bus serves a Route. Each

Route can be served by multiple Buses. A route is described by a route_id, start location, end location, distance, estimated duration of the journey and fare. A customer can book a reservation for a particular bus on a particular date. A customer is described by customer_id, first name, last name, email, and phone number. A reservation can have multiple passengers. A passenger can have multiple reservations too. Each passenger must be uniquely identified by an identifier and have first name, last name, phone number and emergency contact number. Each Reservation generates one or more Tickets, depending on the number of seats reserved. Each ticket has a ticket number and seat number. A ticket must belong to exactly one reservation. Design an ER Model and show the ER diagram based on the above-mentioned scenario. Identify the weak entity set in your diagram using appropriate notations. The scenario description is not complete. You may include additional assumptions. Mention your assumptions explicitly (if any).

Transform your ER model into a set of relational schemas. Show the resulting schema diagram. Add justifications where necessary.