Design an ER$-$diagram $($ a drawing with ovel and sqare and dimond $)$ for the following:Airport $($Airplane$\_$ID $,$ Location $($city $,$ country$))$Flight $($Flight$\_$ID $,$Destination$\_$code $,$ Time$\_$of$\_$flight $)$Aircraft $($Aircraft$\_$ID $,$ Model $)$Passenger $($ Passenger$\_$ID $,$ Name $,$ Age $,$ Contact$\_$info $,$ passport$\_$number$)$Booking $($ Booking$\_$ID $,$ Flight$\_$Number $,$ Seat$\_$Number $,$ infants $($Under $2,$free payment $)$ Child$\_$pricing $(2-11),$ Adult$\_$pricing $(12$ and above$))$Payment $($ Payment$\_$ID $,$ Price $,$ Payment$\_$Method$($credit card $,$paypal,etc$),$Payment$\_$Status$($confirmed $,$ cancelled $))$The relationships : An AIRPORT has many FLIGHTS.A FLIGHT has many BOOKINGS.A PASSENGER has many BOOKINGS.Each FLIGHT is associated with one AIRPORT.Each BOOKING is associated with one PASSENGER.Each airport is identified by its unique Airplane$\_$ID and location $($city$,$ country$).$A flight has a unique Destination$\_$code.Each flight is identified by its unique Flight$\_$ID and scheduled time.Each aircraft is identified by its unique Aircraft$\_$ID and model.Each passenger is identified by their unique Passenger$\_$ID and personal details.Each booking is identified by its unique Booking$\_$ID and includes flight number, seat number, and age$-$based pricing.Each payment is identified by its unique Payment$\_$ID and includes price, method, and status.Each booking must have a payment, following pricing rules for infants $($free$),$ children $($reduced$),$ and adults $($standard$).$