The document describes a web application called UAHMS (UNISZA Auditorium & Hall Management System) that allows for online booking and management of auditoriums and halls at UNISZA. The system aims to computerize booking details, allow admins to view reports, and send email confirmations. It uses an iterative development approach and priority scheduling to approve bookings. The system has three user types - students, staff, and admins - who can register, login, make bookings, and have their requests approved or denied by admins. MySQL is used as the backend database.

1. UNISZA AUDITORIUM & HALL
MANAGEMENT SYSTEM (UAHMS)
NAME : SITI NOR SHUHADA BINTI MOHAMAD
MATRIC NO : BTAL16044385
SUPERVISOR : EN MOHD ISA BIN AWANG

2. INTRODUCTION

3. BACKGROUND
 UAHMS is a web application where the management of multiple
auditorium and hall in UNISZA is computerized.
 In this project, details like student/staff details reserves and booking
details are maintained.
 The report can be viewed completely by the admin by daily, weekly or
monthly and can review it.
 The following activities can be performed reserving specific slot,
booking a time slot, offense-specific auditorium and hall, total
reservation and email notification will be sent on booking
confirmation.

4. OBJECTIVES
 To design a web-based system for booking auditorium and hall in
UNISZA.
 To implement Priority Scheduling methods in booking system.
 To test performance of the system in receiving and cancelling the
bookings of users without any problems.

5. SCOPES
 An online booking system that enables student/staff to book or cancel
the booking of the auditorium or hall in UNISZA.
 Consists of three users including system :
Admin
Student
System
Staff

6. Student
 User registration form available where new users can create their
account.
 User can log in and raise a request for auditorium/hall booking.
 User can request for the booking for a particular date and time
slot.

7. Staff
 User registration form available where new users can create their
account.
 User can log in and raise a request for auditorium/hall booking.
 User can request for the booking for a particular date and time
slot.

8. ADMIN
 It has admin login who is has the authority of the system.
 Responsible for approving and disapproving the users request for
auditorium booking.
 Admin can add and delete notifications and updates in the system.
 Able to manage auditorium and hall booking.
 Able to view all the report.

9. SYSTEM
 Inform the respective customers through an email about their
status of booking request whether approved or disapproved.
 Allows notifies when new event timing draws near.
 Keeps track of auditorium status and advance bookings.
 Keeps records of auditorium bookings along with associated event
details and user contacts in a well maintained database.

10. PROCESS MODEL

11. METHODOLOGY
Iterative and Incremental Model

12. FRAMEWORK DESIGN

13. CONTEXT DIAGRAM

14. DATA FLOW DIAGRAM LEVEL 0

15. DATA FLOW DIAGRAM LEVEL 1
MANAGE PROFILE

16. DATA FLOW DIAGRAM LEVEL 1
MANAGE AUDITORIUM/HALL

17. DATA FLOW DIAGRAM LEVEL 1
BOOKING

18. DATA MODEL

19. ENTITY RELATIONSHIP DIAGRAM

20. PROOF OF CONCEPT

21. ADMIN

22. ADMIN LOGIN

23. HOMEPAGE

24. ADD AUDITORIUM AND HALL

25. BOOKING REPORT

26. AUDITORIUM AND HALL REPORT

27. USER REPORT

28. USER

29. HOMEPAGE

30. REGISTER PAGE

31. LOGIN PAGE

32. USER LOGIN

33. PROFILE PAGE

34. BOOKING FORM

35. BOOKING CONFIRMATION PAGE

36. SESSION TIMETABLE BEFORE BOOKED

37. SESSION TIMETABLE AFTER BOOKED

38. SESSION TIMETABLE EXPIRED

39. CANCEL BOOKING

40. CANCEL BOOKING CONFIRMATION

41. SOLUTION OF
COMPLEXITY

42. HOW TO IMPLEMENT PRIORITY
SCHEDULING TECHNIQUE
 ALGORITHM
1. Start
2. Declare U1, U2
3. If (U1.date = = U2.date) //clash date
3.1 If (U1.capacity > U2.capacity)
3.1.1 Insert U1 data into database
3.1.2 Search (U2.capacity)
3.2 Else if (U1.capacity < U2.capacity)
3.2.1 Insert U2 data into database
3.2.2 Search (U1.capacity)
3.3 Else if(U1.capacity = = U2.capacity)
3.3.1 If (U1.serverTime > U2.serverTime)
3.3.1.1 U1 get insert
3.3.2 Else
3.3.2.1 U2 get insert
4. Else //FCFS
4.1 If (U1.date > U2.date)
4.1.1 U2 get insert
4.2 Else
4.2.1 U1 get insert
5. End

43. MYSQL AS DATABASE
Table 1: Admin
Table 2: User

44. Table 3: Equipment
Table 4: Hall

45. Table 5: Hall Equipment
Table 6: Faculty
Table 7: Booking