Consider an ER schema with entity types Employee and Department, and relationship type Manages (make a drawing!) Employee has one attribute empid (which is the key). Department has one attribute depid (which is the key). Manages has two edges to Employee, one with role boss, one with role sub (for "subordinate"). Manages also has an edge to Department. The edge with role boss is functional. Finally, Manages also has an attribute: date.

Converting this schema to a relational schema with keys and inclusion dependencies, indicate which keys and which inclusion dependencies would be generated. Below, 'inc.' stands for the inclusion symbol.

	1.	Employee[empid] inc. Department[depid]
	2.	key {sub, depid}
	3.	key {sub, boss, depid}
	4.	Manages[depid] inc. Department[depid]
	5.	key {date}
	6.	Employee[empid] inc. Manages[boss]
	7.	key {boss}
	8.	Manages[boss] inc. Employee[empid]