The world’s Largest Sharp Brain Virtual Experts Marketplace Just a click Away
Levels Tought:
Elementary,Middle School,High School,College,University,PHD
| Teaching Since: | Apr 2017 |
| Last Sign in: | 103 Weeks Ago, 3 Days Ago |
| Questions Answered: | 4870 |
| Tutorials Posted: | 4863 |
MBA IT, Mater in Science and Technology
Devry
Jul-1996 - Jul-2000
Professor
Devry University
Mar-2010 - Oct-2016
Hello, If you could help me with this I'd greatly appreciate it. Thank you.
Â
Â
Part 1
Use the following business rules to create a Crow's Foot Entity Relationship Diagram
(ERD). You need not use software to create the diagram. Label the symbols in the
Crow's foot diagram with the letter of the rule that relates to that symbol on the
diagram.
a. A department must have an employee, and can have many employees, but each
employee is assigned to at most one department
b. Some employees are not assigned to any department.
c. A division must have 1 or more departments, but each department is in exactly one
division.
d. An employee may be assigned to many projects, and a project need not have any
employees assigned to it, but can have many employees assigned to it.
e. An employee need not be assigned to a project.
f. Some employees are assigned their own parking space that only the designated
employee can use; some parking spaces are not assigned to any individual.
Part 1 will be graded so you can use those comments in order to complete Part 2. You
may submit a picture of your diagram or in hard copy.
Part 2
Create an Access database based on Part 1. You may do all the following using the
Access GUI rather than using SQL
1. Create a table for each entity shown in Part 1
2. Create additional tables to convert N:M relationships into 1:N relationships
3. Place foreign keys in tables as appropriate
4. Each table should have at least three columns (which can include foreign keys)
that are appropriate for that table - choose any appropriate columns
5. Specify properties for each column - data type, null status, default value (if
any), data constraints (if any) 6. The design should be normalized to Boyce-Codd Normal Form unless you
provide a justification for denormalization..
7. Create relationships that enforce referential integrity; you can do what you like
regarding cascade
For this part, you need only submit an Access database. As an alternative to creating
an Access database, you may submit the SQL in a text file to accomplish the above
steps.
-----------