Databases Reference
In-Depth Information
Major
Department
Course
330
CourseNum
DepartmentCode (FK)
MajorNum
DepartmentCode
Description
DepartmentCode (FK)
DepartmentName
Location
CourseTitle
NumCredits
has prereq
is prereq
Advises
Office
Prereq
CourseNum (FK)
DepartmentCode (FK)
CourseNum/1 (FK)
DepartmentCode/1 (FK)
MajorNum (FK)
StudentNum (FK)
OfficeNum
Phone
FacultyNum (FK)
Faculty
FacultyNum
LastName
FirstName
Street
City
State
Zip
CurrentRank
StartDate
OfficeNum (FK)
DepartmentCode (FK)
Section
ScheduleCode
SemesterCode (FK)
SectionLetter
Time
Room
FacultyNum (FK)
CourseNum (FK)
DepartmentCode (FK)
Student
StudentClass
Semester
StudentNumber
StudentNum (FK)
ScheduleCode (FK)
SemesterCode (FK)
SemesterCode
LastName
FirstName
LocalStreet
LocalCity
LocalState
LocalZip
PermStreet
PermCity
PermState
PermZip
StartDate
EndDate
ExamStartDate
ExamEndDate
WithdrawalDate
Grade
StudentGrade
CourseNum (FK)
DepartmentCode (FK)
StudentNum (FK)
SemesterCode (FK)
Grade
CreditsEarned
GradePoints
CreditsEarned
TotalPoints
ClassStanding
FIGURE A-15
Cumulative design after User View 6
User View 7—Registration request form:
A student uses this form to request classes for the upcoming
semester. Students indicate the sections for which they want to register by entering the sections' schedule
codes; for each section, students may also enter a code for an alternate section in case the requested pri-
mary section is full. The collection of tables to support this user view includes a Student table that con-
sists of the primary key, StudentNum, and all the attributes that depend only on StudentNum. These attributes
include LastName, FirstName, and LocalStreet. Because all attributes in this table are already in the
Student table in the cumulative design, this user view will not add anything new and there is no need for fur-
ther discussion of it here.
