190k views
4 votes
Check My Work Use the following business rules to create a Crow's Foot ERD. Write all appropriate connectivities and cardinalities in the ERD. A department employs many employees, but each employee is employed by only one department. Some employees, known as "rovers," are not assigned to any department. A division operates many departments, but each department is operated by only one division. An employee may be assigned many projects, and a project may have many employees assigned to it. A project must have at least one employee assigned to it. One of the employees manages each department, and each department is managed by only one employee. One of the employees runs each division, and each division is run by only one employee. To upload and submit your assignment, click the Choose File button below to find and select your saved document. Make sure that the file is saved with your last name in the file name. (Example: ch4_problem1_Jones.doc)

User Tiandra
by
6.7k points

1 Answer

2 votes

Final answer:

To represent the given business rules in a Crow's Foot ERD, we can identify the entities and their relationships. A Department employs many Employees, a Division operates many Departments, and an Employee may be assigned to multiple Projects. One Employee manages each Department and runs each Division.

Step-by-step explanation:

To represent the given business rules in a Crow's Foot ERD, we can start by identifying the entities involved. The main entities in this scenario would be Department, Employee, Division, and Project. Here are the connectivities and cardinalities:

  • A department employs many employees, but each employee is employed by only one department. This represents a one-to-many relationship between Department and Employee, with the cardinality of Department as one and the cardinality of Employee as many.
  • Some employees, known as 'rovers,' are not assigned to any department. This can be represented by a null relationship between Department and Rover Employee, indicating that a Rover Employee may or may not be associated with a Department.
  • A division operates many departments, but each department is operated by only one division. This represents a one-to-many relationship between Division and Department, with the cardinality of Division as one and the cardinality of Department as many.
  • An employee may be assigned many projects, and a project may have many employees assigned to it. This represents a many-to-many relationship between Employee and Project. To represent this relationship, we need to introduce a junction entity called Assignment, with connectivities of one-to-many between Employee and Assignment, and one-to-many between Project and Assignment.
  • A project must have at least one employee assigned to it. This can be represented by a mandatory participation constraint between Project and Assignment, indicating that each Project must be associated with at least one Assignment.
  • One of the employees manages each department, and each department is managed by only one employee. This represents a one-to-one relationship between Employee and Department, with the cardinality of Employee as one and the cardinality of Department as one.
  • One of the employees runs each division, and each division is run by only one employee. This represents a one-to-one relationship between Employee and Division, with the cardinality of Employee as one and the cardinality of Division as one.

This representation of the business rules in a Crow's Foot ERD captures the relationships and connectivities between the entities involved, providing a visual understanding of the organization's structure.

User Sentinel
by
6.6k points