1. Draw the ERD of the database that could be used to support the operations of the business described in the case (down below).

The ERD should identify:

• Primary keys and Foreign keys;
• Entities and at least threeAttributes for each entity;
• Relationships and Cardinalities (e.g., one-to-one, one-to-many).

Next to the ERD in your submission, list the assumptions made when designing the ERD. If an element of the business case does not provide the information necessary to know for certain whether one design choice should be made over another, the choice you make will be accepted if it correctly reflects your assumptions.

Business Case: Go Bike

• Go bike is a sharing bike platform with several bike parking stations identified by their longitude, latitude, and a unique 6-digit ID (format: A1A1A).
• There are different departments that are responsible for (e.g., maintenance, finance, and operation), and one or more employees are working in each department. An employee must be assigned to only one department.
• Bicycles are to be described by data such as make, year of production, uses (purpose), size, registry number, purchase price, purchase date, and insurance details.
• There are two types of users (unregistered, and registered users) and only registered users can request a bike. Registered users should provide personal and payment information.
• There are also two types of requests: members' requests and one-time-purchase (OTP). Members can take a bike for free, limited to 30 minutes, and for more than 30 minutes, they should pay an extra fee of 1$ per hour. For OTPs, initially, they should pay 100$ as a deposit and their hourly rate begins from the moment of usage which is 1$ per hour. After returning the bike, the usage amount will be calculated and deducted from the 100$ deposit, and the rest of the deposit will be returned to them.
• No customer can use a bike for more than 100 hours.
• For each usage, the office keeps track of the date of request, the date the bike is returned, bike, customer and the rental total charged amount.
• Personal details (such as name, address, telephone number) about each customer are kept in the database.

HINT: Many-to-many relationships must be split into two one-to-many relationships.

A many-to-many relationship is not allowed.For example, the PROJECT table and the EMPLOYEE table have a many-to-many relationship. One PROJECT can have many EMPLOYEE, and each EMPLOYEE can participate in many PROJECTS.

Eg: