and days/times (QaysTime; for example, 'MWF 9am-9.50am' or TR 3.30pm-5.20pm'- restricted to only allowed days/time values). (Note: The database will keep track of all the sections offered for the past several years, in addition to the current offerings. The Secld is unique for all sections, not just the sections for a particular semester.) The database keeps track of the students in each section, and the grade is recorded when available (this is a many-to-many relationship between students and sections). A section must have at least five students. Draw an ER diagram for this application. Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete.

Database Systems: Design, Implementation, & Management
12th Edition
ISBN:9781305627482
Author:Carlos Coronel, Steven Morris
Publisher:Carlos Coronel, Steven Morris
Chapter9: Database Design
Section: Chapter Questions
Problem 5P
icon
Related questions
icon
Concept explainers
Question
Consider the following set of requirements for a university database that is used to keep track of
students' of student enrollments in classes and students' final grades:
a. The university is organized into colleges (COLLEGE), and each college has a unique
name (CName), a main office (COffice) and phone (CPhone), and
particular faculty
member who is dean of the college. Each college administers a number of academic
departments (DEPT). Each department has a unique name (RName), a unique code
number (RCode), a main office (ROffice) and phone (RPhone), and a particular faculty
member who chairs the department. We keep track of the start date (CStartDate) when
that faculty member began chairing the department.
b. A department offers a number of courses (COURSE), each of which has a unique course
name (COName), a unique code number (CCode), a course level (Level: this can be coded
as 1 for freshman level, 2 for sophomore, 3 for junior, 4 for senior, 5 for MS level, and 6
for PhD level), a course credit hours (Credits), and a course description (CDesc). The
database also keeps track of instructors (INSTRUCTOR); and each instructor has a
unique identifier (Id), name (IName), office (IQffice), phone (IPhone), and rank (Rank);
in addition, each instructor works for one primary academic department
c. The database will keep student data (STUDENT) and stores each student's name
(SName, composed of first name (FName), middle name (MName), last name (LName)),
student id (Sid, unique for every student), address (Addr), phone (Phone), major code
(Major), and date of birth (ReB). A student is assigned to one primary academic
department. It is required to keep track of the student's grades in each section the student
has completed.
d. Courses are offered as sections (SECTION). Each section is related to a single course and
a single instructor and has a unique section identifier (Secld). A section also has a section
number (ŞecNo; this is coded as 1, 2, 3, ... for multiple sections offered during the same
semester/year), semester (Sem), year (Year), classroom (CReom: this is coded as a
combination of building code (Bldg) and room number (RoomNe) within the building),
Transcribed Image Text:Consider the following set of requirements for a university database that is used to keep track of students' of student enrollments in classes and students' final grades: a. The university is organized into colleges (COLLEGE), and each college has a unique name (CName), a main office (COffice) and phone (CPhone), and particular faculty member who is dean of the college. Each college administers a number of academic departments (DEPT). Each department has a unique name (RName), a unique code number (RCode), a main office (ROffice) and phone (RPhone), and a particular faculty member who chairs the department. We keep track of the start date (CStartDate) when that faculty member began chairing the department. b. A department offers a number of courses (COURSE), each of which has a unique course name (COName), a unique code number (CCode), a course level (Level: this can be coded as 1 for freshman level, 2 for sophomore, 3 for junior, 4 for senior, 5 for MS level, and 6 for PhD level), a course credit hours (Credits), and a course description (CDesc). The database also keeps track of instructors (INSTRUCTOR); and each instructor has a unique identifier (Id), name (IName), office (IQffice), phone (IPhone), and rank (Rank); in addition, each instructor works for one primary academic department c. The database will keep student data (STUDENT) and stores each student's name (SName, composed of first name (FName), middle name (MName), last name (LName)), student id (Sid, unique for every student), address (Addr), phone (Phone), major code (Major), and date of birth (ReB). A student is assigned to one primary academic department. It is required to keep track of the student's grades in each section the student has completed. d. Courses are offered as sections (SECTION). Each section is related to a single course and a single instructor and has a unique section identifier (Secld). A section also has a section number (ŞecNo; this is coded as 1, 2, 3, ... for multiple sections offered during the same semester/year), semester (Sem), year (Year), classroom (CReom: this is coded as a combination of building code (Bldg) and room number (RoomNe) within the building),
and days/times (DaysTime: for example, 'MWF 9am-9.50am' or TR 3.30pm-5.20pm'-
restricted to only allowed days/time values). (Note: The database will keep track of all
the sections offered for the past several years, in addition to the current offerings. The
Secld is unique for all sections, not just the sections for a particular semester.) The
database keeps track of the students in each section, and the grade is recorded when
available (this is a many-to-many relationship between students and sections). A section
must have at least five students.
Draw an ER diagram for this application. Specify key attributes of each entity type and structural
constraints on each relationship type. Note any unspecified requirements, and make appropriate
assumptions to make the specification complete.
Transcribed Image Text:and days/times (DaysTime: for example, 'MWF 9am-9.50am' or TR 3.30pm-5.20pm'- restricted to only allowed days/time values). (Note: The database will keep track of all the sections offered for the past several years, in addition to the current offerings. The Secld is unique for all sections, not just the sections for a particular semester.) The database keeps track of the students in each section, and the grade is recorded when available (this is a many-to-many relationship between students and sections). A section must have at least five students. Draw an ER diagram for this application. Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete.
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 3 steps with 1 images

Blurred answer
Knowledge Booster
Query Syntax
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.
Similar questions
  • SEE MORE QUESTIONS
Recommended textbooks for you
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781305627482
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781285196145
Author:
Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel
Publisher:
Cengage Learning