Chapter 2: DATABASE SYSTEM CONCEPTS AND ARCHITECTURE

1. Think of different users for the database shown in Figure 1.2.What types of applications would each
user need? To which user category would each belong, and what type of interface would each need?

Sl.no Users for database Applications Interface

1. International Advising -List of international students Parametric Interface
-Minimum credits/semester
-Eligibility for graduation would
depend credits completed
-List of students under
probation/out of status depends on
grades
- OPT applications would depend
on section

2. Admissions Office -New admissions each semester Form-based/ Parametric

-List of students who got Interface
accepted/denied
-Applications for branch change
-Applications for insurance waiver
-Visa enquiries
3. Student center -To provide transcripts of the Parametric Interface
current and alumni students
after/before they graduate.
4. Professors/Faculty members -Manage records of all students Form-based/ Parametric
 -Advising students on their courses
-Track performances based on their
5 Students
Interface
-Add/Modify grades if needed
overall performances
-To conduct an exam depend on
the course type and number of
students
-To schedule a meeting with the
student
-Monitor whether a student has
enrolled in the appropriate
prerequisite courses
-While enrolling classes in a new Form-based
semester
-To track their performances
-To apply for change of major
-Early/Late registration for the
classes
-To decide on courses
-Drop/Add a course
-To request a transcripts

2. Consider Figure 2.1. In addition to constraints relating the values of columns in one table to columns in
another table, there are also constraints that impose restrictions on values in a column or a
combination of columns within a table. One such constraint dictates that a column or a group of
columns must be unique across all rows in the table. For example, in the STUDENT table, the
Student_number column must be unique (to prevent two different students from having the same
Student_number). Identify the column or the group of columns in the other tables that must be unique
across all rows in the table.

Sl.no Table Column/Columns Constrains

1. STUDENT Student_number -Student number should be unique
across all rows in the table to avoid
overlapping of the tables if any two
students have same names in a section.
2. COURSE Course_number -No two course number can be same,
course number determines the
department and course name itself.
-If any new course is added to the
catalog then it must be assigned a
unique number to differentiate from
the existing ones.
3. PREREQUISITE Prerequisite_number - Prerequisites are unique because they
 depend on the course in the section
table.
-Few courses have prerequisites, few
don’t so it is really important to make
sure that Prerequisite_number is
unique.
4. SECTION Section_Identifier -Sections offered in a particular
semester must be different to avoid the
overlapping of the classes.
-This would affect the registration
process as also.
-It also depends on the year if the
course is newly added.
-It depends on the professor if he wants
to add an extra sction or not based on
the number students enrolled.
5. GRADE_REPORT Student_number -Student number should be unique as
mentioned above even though they
& have same names.

Section_Identifier -Section Identified is a unique number

as stated above as it depends on the
semester, year the course is offered.