You are asked to work as database designer to consider the following problem description (Note that X and Y are specific to every student): A transportation company hires drivers to drive buses between stations. A driver drives buses from a source station to a destination station. It is necessary to keep track of all the stations visited while moving from the source to the destination. Each station has a director (who may be a driver), a location and registered passengers who may be classified into various categories like X, Y and Z (here, replace X, Y, Z with three types of passengers of your choice (like students) and specify two or three attributes for each type of passengers you choose). A station also runs different projects to improve its services. A driver has equipment in each bus he/she drives. Each equipment has serial number, name, color and may be shared by several drivers to serve passengers. A driver has an ID, name, phone, and at least one hoppy. A driver has multiple insurance coverages (we need only names of the insurance company and its phone number) and gives preferential treatment to passengers in category Y; we need to keep the time of the special treatment and the satisfaction level of the passenger. A bus gets regular checkup and maintenance at the mechanic shop. Each visit to the mechanic may lead to replacing some parts with an associated cost per part. We need to keep the part number, price (other than the replacement cost), manufacturer and life-time. a) Draw Extended Entity Relationship diagram by identifying entities, relationships, and their attributes. Only when it is obvious from the above description, decide on relationship cardinality. State any constraints you may find necessary; but make sure your constraints do not contradict with the problem specifications as described above. . b) Transform your EERD from part (a) into the relational model