Part 3.1 Modelling (Total: 35 Points) Question 3.1.1 (35 Points) Build a conceptional model for an Online Bus Booking Syste The solution should be presented as an ER-diagram. Base your design on the following requirements . The database should record information about Customers, Emails, Addresses, Tickets, Buses, Bus Sched ules, Bus Stops, Purchase Feedback, and Payments. . A Customer has a name which consists of firstName, middleName and lastName. Customers are dentified by a unique custID. A Customer can have one or more phoneNumbers - Customers can book any number o Tickets (including n. Customers may provide Feedback for each booking (optional). For every booking, a Customer has to make a Payment. .An Address consists of a unique addrID, street, streetNumber, city, state and zipcode. The attributes city and state can be derived from the attribute zipode. - A Customer can be associated with any mber of Addresses and there may be multiple Cus- tomers living at the same Address. There may be some Addresses which are not be associated with any Customer . An Email consists of unique emalD and a Passuord. - A Customer may or may not have an Email and every Email belongs to a single owner (customer) We assume that a Customer can have only one Email. . A Bus is identified using a busNumber. A Bus has a capacity, model and a ticketPrice. Bus may follow several Schedules. . A Bus Stop is uniquely identified by the Address it is located at. A Bus Stop has a type (either sheltered or simple). . A Schedule includes an ArrivalTime, DepartureTime, and a unique scheduleID. - A Schedule is associated with one or more Bus Stops. For each association, we record the scheauled time of the bus stopping at this Bus Stop .A Ticket has its unique ticketid. Tickets also have a bookingDate and lDate. A Ticket may have one or more sealNumbers. - Each Ticket may be associated with a single Feedback. - Every Ticket has a Bus associated with it, while a Bus may have many different Tickets associated with itself. A Payment is identified by the Ticket for which the payment was nade. It consists of the mountPid and payment.Method (Credit Card, E-Check, etc.) Every Purchase Feedback is uniquely identified by the Ticket for which the feedback is given. For each Purchase Feedback we store a raling and commerat. Part 3.1 Modelling (Total: 35 Points) Question 3.1.1 (35 Points) Build a conceptional model for an Online Bus Booking Syste The solution should be presented as an ER-diagram. Base your design on the following requirements . The database should record information about Customers, Emails, Addresses, Tickets, Buses, Bus Sched ules, Bus Stops, Purchase Feedback, and Payments. . A Customer has a name which consists of firstName, middleName and lastName. Customers are dentified by a unique custID. A Customer can have one or more phoneNumbers - Customers can book any number o Tickets (including n. Customers may provide Feedback for each booking (optional). For every booking, a Customer has to make a Payment. .An Address consists of a unique addrID, street, streetNumber, city, state and zipcode. The attributes city and state can be derived from the attribute zipode. - A Customer can be associated with any mber of Addresses and there may be multiple Cus- tomers living at the same Address. There may be some Addresses which are not be associated with any Customer . An Email consists of unique emalD and a Passuord. - A Customer may or may not have an Email and every Email belongs to a single owner (customer) We assume that a Customer can have only one Email. . A Bus is identified using a busNumber. A Bus has a capacity, model and a ticketPrice. Bus may follow several Schedules. . A Bus Stop is uniquely identified by the Address it is located at. A Bus Stop has a type (either sheltered or simple). . A Schedule includes an ArrivalTime, DepartureTime, and a unique scheduleID. - A Schedule is associated with one or more Bus Stops. For each association, we record the scheauled time of the bus stopping at this Bus Stop .A Ticket has its unique ticketid. Tickets also have a bookingDate and lDate. A Ticket may have one or more sealNumbers. - Each Ticket may be associated with a single Feedback. - Every Ticket has a Bus associated with it, while a Bus may have many different Tickets associated with itself. A Payment is identified by the Ticket for which the payment was nade. It consists of the mountPid and payment.Method (Credit Card, E-Check, etc.) Every Purchase Feedback is uniquely identified by the Ticket for which the feedback is given. For each Purchase Feedback we store a raling and commerat