1. Produce an ERD that portrays the relationships listed below. Provide appropriate FK attribute
names.
A CONSULTANT (ConsultID,Name,Status, FK1,FK2)
Works in exactly 1 department
Is a member of only 1 team and must be on a team
Is either an employee or a contractor
Employee or contractor-specific supplemental attributes are tracked outside of CONSULTANT
A DEPARTMENT(DeptID,DeptName)
May have many consultants
You can have a department without any consultants
A TEAM(TeamName,Description)
Is in zero or more office locations
You cant have a team without multiple consultants
An OFFICE(OfficeID,Description,FK1)
Can have zero or more teams
Is in exactly 1 building but you cant have an office without a building
A BUILDING(BldgID,Address,Owner)
Has at least 1 but may have many offices
Eliminate any N:M relationships in this exercise
Do the following:
Draw a Crows Foot ERD, using proper notation, for the above scenario.
Identify all possible relationships
Identify the connectivity for each relationship. The relationship line should connect PK to FK
and show the proper min/max cardinalities. The keys attribute name may be derived from the
problem narrative, or you may need to use a surrogate PK (e.g. EmployeeNum)
Use these LucidChart entity shapes and formats:
To help simplify, work under the assumption that only ID-dependent associative entities are
weak in your ERD.

2. Derive non-key attribute names from the narrative wherever possible (e.g. DateLastContacted).
Each entity should have all attributes identified in your SME interviews.
Identify and properly label all entity relationships (example: you should have a narrative label of
is assigned to at the qualification end of the EMPLOYEE>CUSTOMER relationship
termination).
Entities should represent a single theme and be normalized to at least 3rd Normal Form. This
means, among other 3NF requirements, all attributes should further describe the theme of only
that entity. Hint: Does a manufacturers phone # further describe the theme of EQUIPMENT?
Do the following:
Draw a Crows Foot ERD, using proper notation, for the above scenario.
Identify all possible relationships
Identify the connectivity for each relationship. The relationship line should connect PK to FK
and show the proper min/max cardinalities. The keys attribute name may be derived from the
problem narrative, or you may need to use a surrogate PK (e.g. EmployeeNum)