Database System:

Assume that you are a graduate and with few of your friends, you have founded a startup company where you are the database designer. Since ride sharing service-based apps are really doing good and the rainy season is knocking at the door, your creative team has come up with an app idea, named METAL. The business logic of METAL is quite similar to other ride sharing apps, however, your app is unique since this will deal with boat sharing. Anyhow, you have started your database design where the DB is named as 'metaldb'. You have initially identified the necessity to store the following information:

For the app user (rider), you need to store name, NID, cell number, address and one emergency contact number. For the boat, its id, start location, end location, capacity and fee. For the boat owners, their name, NIDs, and district. A boat owner may have multiple boats; however, each boat is operated by exactly one owner. And For every trip, store the riders in the trip, the boatman who sailed, fee paid by each rider. A trip may have multiple riders, and a boatman may be working with multiple boat owners. Considering this scenario, answer the all the following questions.

Question 1: Recommend an entity relationship diagram for the database 'metaldb'. Question 2: Provide appropriate SQL to construct tables for 'metaldb'. The SQL must support the ERD of the previous question. Data types for all the attributes need to be rational, however field size for any attribute must not exceed 8.