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
1.
2.
3.
Users for database
International Advising
Admissions Office
Student center
Interface
Parametric Interface
Parametric Interface
Applications
-List of international students
-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
-New admissions each semester
-List of students who got accepted/denied
-Applications for branch change
-Applications for insurance waiver
-Visa enquiries
-To provide transcripts of the current and alumni students after/before they graduate.
Form-based/ Parametric
Interface
4.
5
Professors/Faculty members
Students
-Manage records of all students
-Advising students on their courses
-Add/Modify grades if needed
-Track performances based on their 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 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
Form-based/ Parametric
Interface
Form-based
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
1.
Table
STUDENT
Column/Columns
Student_number
2. COURSE Course_number
Constrains
-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.
-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
3.
4.
PREREQUISITE
SECTION
5. GRADE_REPORT
Prerequisite_number
Section_Identifier
Student_number
&
Section_Identifier unique number to differentiate from the existing ones.
- 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.
-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.
-Student number should be unique as mentioned above even though they have same names.
-Section Identified is a unique number as stated above as it depends on the semester, year the course is offered.