1) Time Cards Database:
A company wants to have a system for submitting and approving its time cards. Draw the database ER diagram according to this specification:
a) Employee and Timecard entity types connected by a 1:M relationship from Employee to Timecard. Choose an appropriate relationship name. Define minimum cardinalities so that an employee does not need to associate to any timecard, but each timecard must associate to an employee. A timecard should have a unique id, hours worked, date submitted and a status (approved, not approved, or pending). Each employee has a unique id, name, address and method of payment of his/her choice (i.e., direct deposit, check, cash).
b) Manger entity type is a subtype of the Employee entity type. Manager has one additional attribute, responsibility.
c) Manager and Employee entity types connected by 1:M relationship from Manager to Employee. Choose an appropriate relationship name. Define minimum cardinalities so that a manager does not need to manage any employee, and an employee must have a manager to report to.
d) Manager and Timecard entity types connected by 1:M relationship from Manager to Timecard. Choose an appropriate relationship name. Define minimum cardinalities so that a manager does not need to approve a time card but a time card must be approved by a manager.
e) Employee and Location entity types connected by M:N relationship between Employee and Location. This relationship should have an attribute named BeginWorkDate and EndWorkDate. Choose an appropriate relationship name. Define minimum cardinalities so that each location does not need to have any employee but an employee must work on some location. Each location should have a unique id, location name, and province.