COMPREHENSIVE DESIGN EXAMPLE: MARVEL COLLEGE - Concepts of Database Management - page 324

324

Department
CourseNum
CourseTitle
Grade
CreditsTaken (Course)

CreditsEarned (Course)

GradePoints (Course)

CreditsTaken (Semester)

CreditsEarned (Semester)

GPA (Semester)

TotalPoints (Semester)

CreditsTaken (Cumulative)

CreditsEarned (Cumulative)

GPA (Cumulative)

TotalPoints (Cumulative)

SemesterCode
StudentNum
LastName
FirstName
Address
City
State
Zip
LocalAddress
LocalCity
LocalState
LocalZip

FIGURE A-11 Attributes on a report card from Marvel College

Assume the system's users have verified the attributes listed in Figure A-11 and your work is correct.
Figure A-12 shows the functional dependencies among the attributes you identified on the report card. The stu-
dent number alone determines many of the other attributes.

StudentNum →

CreditsTaken

(Cumulative)

CreditsEarned (Cumulative)

GPA (Cumulative)

TotalPoints (Cumulative)

LastName
FirstName
Address
City
State
Zip
LocalAddress
LocalCity
LocalState
LocalZip

StudentNum, SemesterCode →

CreditsTaken (Semester)

CreditsEarned (Semester)

GPA (Semester)

TotalPoints (Semester)

DepartmentName, CourseNum →

CourseTitle

CreditsTaken (Course) (Same as NumCredits)

StudentNum, SemesterCode, DepartmentName, CourseNum →

Grade

CreditsEarned (Course)

GradePoints (Course)

FIGURE A-12 Functional dependencies among the attributes on a report card

In addition to the student number, the semester must be identified to determine credits taken and earned,
grade point average (GPA), and total points each semester. The combination of a department name (such as
Computer Science) and a course number (such as 153) determines a course title and the number of credits.