Conceptual Data Modeling

Create a data model (ERD) based on the following business rules. You must

• Identify all of the main entities.
• Identify all of the relations and connectivities.
• Identify PK and FK
• Identify the type of participation optionality, existence dependency and relationship strength in all the relationships.
• Resolve the many to many relationships using the associative entities.

You must use Lucidchart to draw the ERD (and then copy and paste your complete diagram).

For each employee, the following information is stored: Employee ID, First and Last name, Rank, and billing rate. Employees are organized into solution sets, each solution set has a head of the solution set, who is the resource owner for all employees in that SS. For each solution set we record the SS ID and the SS name. For scheduling purposes, we want to store information about the head of each solution set, and about assignment of employees to solution sets. An employee can belong to only one solution set.

The scheduling system also stores information about project. For each project, the following information is stored: Project ID, Status, Location and Client name.

As a part of the scheduling system, we store information about each calendar day in a year with the date and the weekday. When an assignment is requested for an employee, the employee is scheduled to work on a particular project, on a particular day for the specified amount of time (10%-100%). For each assignment we also record current status.

Hint: You may need the following 6 entities in your diagram: EMPLOYEE, SOLUTIONSET, ASSIGNMENT, CLIENT, PROJECT, CALENDAR. There would be two relationships between EMPLOYEE and SOLUTIONSET. CALENDAR entity has three attributes: C_YEAR, C_WEEKDAY, C_DATE, all of which will be used as a composite PK.