Draw an Entity-Relationship diagram for the scenario described below. Each relationship must have cardinalities. If you think that the cardinality of a relationship hasn't been clearly specified, please make your own REASONABAL assumptions and NOTE them. If you want to use weak entities in your diagram, please use a rectangle with dotted line to present a weak entity. If you want to use interaction entities, please a rectangle with double edges to represent an interaction entity. You can use the drawing tool https://erdplus.com/ , Microsoft word, or any other software (such as visio) to draw the diagram. Please make sure your diagram is readable and understandable.

Scenario: A website flightpedia.com helps people book flights. Each customer has a customer ID, and the system also stores their first name, last name, date of birth, gender, address, email, and phone number. Flightpedia.com also tracks flight information. For each flight, the website tracks the flight number, the airline, the departure and arrival dates and times, the departure and arrival airports, the ticket price (to simply things a little, we don't consider different flight classes. Each flight has just one price). When booking a flight, the customer must book for him/herself and can add at most two other passengers. For each of the accompanying passengers, the customer needs to provide their first name, last name, date of birth and gender, and the customer must select seats for him/herself and their accompanying passengers. When a flight is booked (here we just consider one-way flight), the website creates a reservation id and records the reservation date and time (different from the fight date and time). For each reservation, the system should be able to retrieve the flight information including the fight number of the booked flight and the fight date and time, the customer information such as customer ID, first name, last name, etc., the passenger information provided by the customer, and their selected seats. Meanwhile, the customer is invoiced. The database needs to track the invoice number, and invoices must be paid before the departure date. If the invoice is not successfully paid in time, the reservation will be cancelled, but the company will keep the reservation record in the database for one year. A person, who does not have to be the customer, must pay the invoice in full, either by credit card, debit card or PayPal account. For each payment, the system needs to record the invoice number and the name and address of the payer. If the payer pays using credit card or debit card, the system needs to record the card type, card number and expiration date and if the payer pays using PayPal, the system needs to record the PayPal account number. The system also needs to have a flag field that indicates if a payment is successful or not.