Major (such as mathematics or MATH and computer science or CS); each COURSE record includes data to represent the Course_name, Course_number, Credit_hours, and Department (the department that offers the course); and so on. We must also specify a data type for each data element within a record. For example, we can specify that Name of STUDENT is a string of alphabetic characters, Student_number of STUDENT is an integer, and Grade of GRADE_REPORT is a single

character from the set {A,B,C,D,F,I}. We may also use a coding scheme to rep- resent the values of a data item. For example, in Figure 1.2 we represent the Class of

a STUDENT as 1 for freshman, 2 for sophomore, 3 for junior, 4 for senior, and 5 for graduate student. To construct the UNIVERSITY database, we store data to represent each student, course, section, grade report, and prerequisite as a record in the appropriate file. Notice that records in the various files may be related. For example, the record for Smith in the STUDENT file is related to two records in the GRADE_REPORT file that specify Smiths grades in two sections. Similarly, each record in the PREREQUISITE

file relates two course records: one representing the course and the other represent- ing the prerequisite. Most medium-size and large databases include many types of

records and have many relationships among the records. 1:A

Give 5 informal queries and 5 updates that you would expect to apply to the database shown in Figure 1.2. 1:B Give 2 additional views that may be needed by other user groups for the database shown in Figure 1.2. 1:C Give 5 examples of integrity constraints that you think should hold on the database shown in Figure 1.2.

COURSE SECTION GRADE_REPORT PREREQUISITE Figure 1.2 A database that stores student and course information