#Detail of the scenarioDeveloping ERDoDefining at least $7$ EntityoDefining attributesoDefining all necessary relationships $($Identify with matrix diagram$)$oIf possible superype$-$subtype, arc and hierarchical structures, non$-$ transferable relationship.Preparing "table instance chart" to map ERD to DB structureWriting SQL DDL statements for implementing ERD $($create table, constraints, defining keys: pks and fks$)$Making Physical Database using APEXEntering data to the DatabaseWriting SQL DML Statements to reach informationoOne statement including subqueryoOne statement including joinoOne statement including group byoOne statement including date functionoOne statement including character functionoOne statement including updateoOne statement including alter tableRailway System Database ProjectA railway system, which needs to model the following:$1.$Stations$\mathrm{.}2.$Tracks, connecting stations. You can assume for simplicity that only one track exists between any two stations. All the tracks put together to form a graph$\mathrm{.}3.$Trains, with an ID and a name$\mathrm{.}4.$Train schedules recording what time a train passes through each station on its route.You can assume for simplicity that each train reaches its destination on the same day and that every train runs every day. Also, for simplicity, assume that for each train, for each station on its route, you store. Time in$.$ Timeout $($same as time in if it does not stop$).$ A sequence number so the stations in the route of a train can be ordered by sequence number$\mathrm{.}1.$Passenger booking consisting of train, date, from$-$station, to station, coach, seat and passenger name.Tables: Stations, Tracks, Trains, TrainSchedules, Coaches, Bookings, Passengers.