name address Stars name title year Stars-in Studios Owns address Movies length genre
name address Stars name title year Stars-in Studios Owns address Movies length genre
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
Draw an E-R diagram based on the following relational design.
SeniorTeachers(teacherId, name, dept, division)
TeachingAssistants(teacherId, name, dept, division).
# These can be currently registered students who are employed part-time as teaching assistants,
# or they can be PhD students who are employed full-time.
Programmes(programmeCode, programmeName, dept, director)
director → SeniorTeachers.teacherId
Courses(courseCode, courseName, credits, level, dept, division, ownedBy)
ownedBy → Programmes.programmeCode
# level is one of “first cycle” or “second cycle”.
programmeCourses(programme, academicYear, studyYear, course, courseType)
programme→ Programmes.programmeCode
course → Courses.courseCode
# studyYear is “1” or “2” for Master’s programmes and “1”, “2” or “3” for Bachelor’s programmes.
# courseType is one of: “compulsory”, “compulsory-elective” or “elective”.
# Programmes can include different courses in different academic years.
# The same course could have a different courseType in different academic years.
CourseInstances(courseCode, studyPeriod, academicYear, instanceId, examiner)
courseCode→ courses.courseCode
examiner → SeniorTeachers.teacherId
CoursePlanning(course, planningNumStudents, seniorHours, assistantHours)
course → CourseInstances.instanceId
# planningNumStudents is the number of students used for planning course resources
# seniorHours is the estimated number of senior teachers’ hours that the course will need.
# assistantHours is the estimated number of teaching assistant hours that the course will need.
SeniorTeachers(teacherId, name, dept, division)
TeachingAssistants(teacherId, name, dept, division).
# These can be currently registered students who are employed part-time as teaching assistants,
# or they can be PhD students who are employed full-time.
Programmes(programmeCode, programmeName, dept, director)
director → SeniorTeachers.teacherId
Courses(courseCode, courseName, credits, level, dept, division, ownedBy)
ownedBy → Programmes.programmeCode
# level is one of “first cycle” or “second cycle”.
programmeCourses(programme, academicYear, studyYear, course, courseType)
programme→ Programmes.programmeCode
course → Courses.courseCode
# studyYear is “1” or “2” for Master’s programmes and “1”, “2” or “3” for Bachelor’s programmes.
# courseType is one of: “compulsory”, “compulsory-elective” or “elective”.
# Programmes can include different courses in different academic years.
# The same course could have a different courseType in different academic years.
CourseInstances(courseCode, studyPeriod, academicYear, instanceId, examiner)
courseCode→ courses.courseCode
examiner → SeniorTeachers.teacherId
CoursePlanning(course, planningNumStudents, seniorHours, assistantHours)
course → CourseInstances.instanceId
# planningNumStudents is the number of students used for planning course resources
# seniorHours is the estimated number of senior teachers’ hours that the course will need.
# assistantHours is the estimated number of teaching assistant hours that the course will need.
the image is how should the ER look a like .
AssignedHours(courseCode, studyPeriod, academicYear, teacherId, hours)
(courseCode, studyPeriod, academicYear) →
CourseInstances.(courseCode, studyPeriod, academicYear)
ReportedHours(course, teacherId, hours)
course → CourseInstances.instanceId
Students(studentId, name, programme, year, graduated)
(programme, year)→ ProgrammeCourses.(programme, academicYear)
# year is the academic year in which the student joined the programme.
# graduated is a Boolean attribute.
Registrations(courseInstance, student, status, grade)
course → CourseInstances.instanceId
student→ Students. studentId
# status is one of: “not started”, “registered”, “completed”, “withdrawn”.
# For students who have completed the course, the grade is one of “5”, “4” or “3”.
In addition to the E-R diagram, your answer should include comments:
• Stating any additional assumptions that you have made. For example, keys for the
relations are not stated in the task description, and some references (foreign keys)
are missing.
• Explaining design decisions that you have made. For example, if you considered more
than one way to model a particular part of the domain, explain your choice and why
you preferred it to the alternative that you considered
(courseCode, studyPeriod, academicYear) →
CourseInstances.(courseCode, studyPeriod, academicYear)
ReportedHours(course, teacherId, hours)
course → CourseInstances.instanceId
Students(studentId, name, programme, year, graduated)
(programme, year)→ ProgrammeCourses.(programme, academicYear)
# year is the academic year in which the student joined the programme.
# graduated is a Boolean attribute.
Registrations(courseInstance, student, status, grade)
course → CourseInstances.instanceId
student→ Students. studentId
# status is one of: “not started”, “registered”, “completed”, “withdrawn”.
# For students who have completed the course, the grade is one of “5”, “4” or “3”.
In addition to the E-R diagram, your answer should include comments:
• Stating any additional assumptions that you have made. For example, keys for the
relations are not stated in the task description, and some references (foreign keys)
are missing.
• Explaining design decisions that you have made. For example, if you considered more
than one way to model a particular part of the domain, explain your choice and why
you preferred it to the alternative that you considered
Expert Solution
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
Step by step
Solved in 2 steps
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