A small bus company keeps details of the starting place, destination, and fare for all routes which it operates.
 Each route has a unique route number and is divided into a number of stages. A stage
is identified by the names of the bus stops that mark its beginning and end.
 For example, route number 154 goes from Hartlepool-Greatham, GreathamWolviston, Wolviston-Billingham, and Billingham-Norton.
 Each stage may appear in a number of routes, and is given a different sequence
number for each route.
 For example, Greatham-Wolviston is stage 2 on route 154, stage 3 on route 178
Billingham-Sunderland, and stage 6 on route 105 Stockton-Hartlepool.
 The distance in miles is kept for each stage.
 Each route is associated with a number of scheduled departures, each of which is
identified by a day of the week and a time.
 The estimated arrival time at the destination is recorded for each departure. There may
be a number of departures, for different routes, leaving at the same time? on the same
day.
 For example, route 154 departs at 9.15 on Monday, 10.00 on Wednesday, and at 9.30
and 15.00 on Saturday. Route 105 also departs at 9.30 on Saturday.
 Once a week a particular bus is allocated to each departure scheduled for the
following week. The data on which bus is allocated to which departure is only kept
for one week, being removed when buses are allocated for the following week.
 Details of the registration number and seating capacity of each bus are recorded.
 Every route must consist of at least one stage, but details of a stage may be kept even
if it is not currently part of route.
 Details of the scheduled departures are recorded before buses are allocated.
 Details of all buses are recorded even if they are not currently allocated to any
departures. Details of routes are to be recorded before departures have been arranged.
Design database for the given case scenario and also normalize the database. List your
assumptions and clearly indicate the cardinality mappings.