Develop an online web-based university

administration system

Patrick Ward
D11124386
Instructor: Mr. Patrick Mathews
Module: Advanced Database Systems
1st March 2012

1. Assignment Overview!

1.1.User Types!

1.2.User Functionality!

1. Students will be able to:!

2. Lecturers will be able to:!

3. Administrators will be able to:!

2. Database Tables!

2.1.User Tables!

2.2.Main Tables!

1. Scheduling Tables:!

2. Linking Tables to avoid Many to Many relationships:!

3. Entity Relationship Diagram!

4. Use Case Diagrams!

4.1.Basic Use Case Diagram!

4.2.Student Use Case Diagram!

10

4.3.Lecturer Use Case Diagram!

11

4.4.Administrator Use Case Diagram!

12

University administration system database design

1. Assignment Overview
Design a database system that will allow the efficient management of the university.

1.1. User Types

The system will have three user types:
1. Students
2. Lecturers
3. Administrators

Page 3

University administration system database design

1.2. User Functionality

1.2.1. Students will be able to:
1. register for a semester
2. view all available modules
3. enrol to up to 4 modules
4. view the modules they are enrolled to
5. view their class timetables
6. view their grades
7. un-enrol from modules (provided the module has not been closed by an administrator)

1.2.2. Lecturers will be able to:

1. view the modules they are assigned to
2. view their timetable
3. view a list of all enrolled students to each module
4. assign grades to each student enrolled on the module (if the module is closed)

1.2.3. Administrators will be able to:

1. assign modules to semesters
2. assign lecturers to modules (1 lecturer will be assigned to a maximum of 3 modules per
semester.
3. assign and edit room, days and timeslots to modules (this combination must be unique to
avoid timetable clashes)
4. view timetables for lecturers and students
5. close a module for enrolment
6. produce lists of enrolled students for each module
7. view grades for all students on a module
8. view all grades of a particular student

Page 4

University administration system database design

2. Database Tables
The tables below have been designed to meet the requirements of 3rd Normal Form that states
that all non-key columns are independent of each other in addition to meeting 1st and 2nd
Normal Forms.

2.1. User Tables

Note: Colour coding =

Staff_ID
SystemLogin_id
fist_name
last_name
addressLine1
addressLine2
addressLine2
addressLine2
email
mobilePhone
officePhone
job_typeId

id
title

Staff
int (11)
int (10)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
int (14)
int (14)
int (1)

Primary Key
Foreign Key
Combined Key

Primary Key

id
SystemLogin_id
fist_name
last_name
addressLine1
addressLine2
addressLine2
addressLine2
email
mobilePhone
officePhone

Student
int (11)
int (10)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
varchar (55)
int (14)
int (14)

Primary Key
Foreign Key

Foreign Key

Job_Type
int (1)
Primary Key
varchar (55)

id
username
password

Page 5

SystemLogin
int (10)
Primary Key
varchar (25)
varchar (25)

University administration system database design

2.2. Main Tables

code
title
openOrClosed
SemesterID

Module
varchar (5)
varchar (55)
binary (1)
int (10)

Primary Key

id
startDate
endDate

Foreign Key

2.2.1. Scheduling Tables:

Day
id
int (1)
Primary Key
name
varchar (3)
mon, tues, etc.
This will be read-only table representing 7 day week.
TimeSlot
id
int (2)
Primary Key
startTime
time
endTime
time
This will be read-only table representing 24 hour clock.

roomName
capacity

Room
varchar (6)
int (4)

Primary Key

Class (event)
RoomName
int(10)
Primary Key
TimeSlot
int(2)
Primary Key
DayID
int(1)
Primary Key
ModuleCode
varchar (5)
Primary Key
Combined key will prevent scheduling conflicts

Page 6

Semester
int (6)
date
date

Primary Key

University administration system database design

2.2.2. Linking Tables to avoid Many to Many relationships:

SemesterID
Student_ID
Date

Registration
int(6)
int(11)
timestamp

LecturerToModule
staff_id
int(10)
ModuleCode varchar(5)
staffJob_Type int (1)
Restricted to 3 per lecturer using a trigger

StudentToModule
int(10)
int(6)

StudentID
SemesterID
ModuleCode
grade
varchar (5)
Restricted to 4 per student using a trigger

Page 7

University administration system database design

3. Entity Relationship Diagram

Page 8

University administration system database design

4. Use Case Diagrams

4.1. Basic Use Case Diagram

Page 9

University administration system database design

4.2. Student Use Case Diagram

Page 10

University administration system database design

4.3. Lecturer Use Case Diagram

Page 11

University administration system database design

4.4. Administrator Use Case Diagram

Page 12