The ER Model shown below is based on the following business rules. A manager manages one department. Each department is managed by one manager. An employee is assigned to one project. Each project is assigned many employees. Employee's salary cannot be less than 0. A project's end date cannot be earlier than its start date. UID (Unique identifier) uniquely identifies an instance of the entities. DEPARTMENT PROJECT DeptNo: UID DName ProjectNo: UID StartDate EndDate Location Is assigned is managed by is hired by ΕMPLOYEE EmpNo: UID EmpFName EmpLName EmpPhone Salary BirthDate manages iş supervised by Zipcode Supclvises Requirements 1 Based on the ER Model, write SQL statements to create EMPLOYEE, DEPARTMENT and PROJECT tables. • First, you'll need to do the relational modeling. In other words, map the ER model to the relational model (i.e., table structure with PK and FKs) • For each column, use the data type and length that you think appropriate. • Implement all necessary data integrity rules (e.g., entity integrity constraint, key constraint, referential integrity constraint, and semantic integrity constraints). • If necessary, make explicit assumptions.
The ER Model shown below is based on the following business rules. A manager manages one department. Each department is managed by one manager. An employee is assigned to one project. Each project is assigned many employees. Employee's salary cannot be less than 0. A project's end date cannot be earlier than its start date. UID (Unique identifier) uniquely identifies an instance of the entities. DEPARTMENT PROJECT DeptNo: UID DName ProjectNo: UID StartDate EndDate Location Is assigned is managed by is hired by ΕMPLOYEE EmpNo: UID EmpFName EmpLName EmpPhone Salary BirthDate manages iş supervised by Zipcode Supclvises Requirements 1 Based on the ER Model, write SQL statements to create EMPLOYEE, DEPARTMENT and PROJECT tables. • First, you'll need to do the relational modeling. In other words, map the ER model to the relational model (i.e., table structure with PK and FKs) • For each column, use the data type and length that you think appropriate. • Implement all necessary data integrity rules (e.g., entity integrity constraint, key constraint, referential integrity constraint, and semantic integrity constraints). • If necessary, make explicit assumptions.
Database System Concepts
7th Edition
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Chapter1: Introduction
Section: Chapter Questions
Problem 1PE
Related questions
Question

Transcribed Image Text:Assignment #3: Data Definition
The ER Model shown below is based on the following business rules.
A manager manages one department. Each department is managed by one
manager.
An employee is assigned to one project. Each project is assigned many
employees.
Employee's salary cannot be less than 0.
A project's end date cannot be earlier than its start date.
UID (Unique identifier) uniquely identifies an instance of the entities.
DEPARTMENT
PROJECT
DeptNo: UID
ProjectNo: UID
StartDate
DName
EndDate
Location
Is assigned
managed by
is hired by
ΕMPLOYEΕ
EmpNo: UID
EmpFName
EmpLName
EmpPhone
Salary
BirthDate
Zipcode
manages
is supervised by
Supclvises
Requirements
1
Based on the ER Model, write SQL statements to create EMPLOYEE,
DEPARTMENT and PROJECT tables.
• First, you'll need to do the relational modeling. In other words, map the ER
model to the relational model (i.e., table structure with PK and FKs)
• For each column, use the data type and length that you think appropriate.
• Implement all necessary data integrity rules (e.g., entity integrity constraint,
key constraint, referential integrity constraint, and semantic integrity
constraints).
• If necessary, make explicit assumptions.
Expert Solution

This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps

Knowledge Booster
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.Recommended textbooks for you

Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education

Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON

Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON

Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education

Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON

Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON

C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON

Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning

Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education