1.

0 COURSEWORK TITLE
Hall Booking Management System

2.0 THE COURSEWORK OVERVIEW

The CEO of Hall Symphony Inc. has tasked your team with creating a system for
booking their halls, making it easy for customers to reserve them for events such as
conferences, weddings, and meetings at their preferred times. The business operates
daily from 8:00 AM to 6:00 PM. Hall Symphony offers three types of halls: an
auditorium (seating 1000 people), a banquet hall (seating 300 people), and meeting
rooms (seating 30 people). Customers can reserve these halls for their events. Table 1
shows the booking rate for each hall type.

Table 1
Hall Type Booking Rate per hour (in RM)
Auditorium RM 300.00
Banquet Hall RM 100.00
Meeting Room RM 50.00

Primarily there are 4 types of users involve with this system as listed below:
1. Scheduler (Staff)
• Handles booking and scheduling events in the halls.
2. Customer
• The one who reserves halls for their events.
3. Administrator (Staff)
• Manages the staff and customer accounts.
4. Managers (Staff)
• The one who oversees the performance of the sales and maintenance
operations.

In addition, a supporting document is needed to reflect the design of the implementation

codes and the implementation details that utilize the Object-oriented programming
concepts.

3.0 OBJECTIVES OF THIS COURSEWORK

Develop the practical ability to describe, justify, and implement an Object-oriented
system.

4.0 TYPE
Group Assignment (minimum 3 and maximum 4 students)
5.0 COURSEWORK DESCRIPTION
As an object-oriented programming student, you are required to identify the
relationship among the entities and develop a user-friendly GUI application for 4 role
types of users by fulfilling the minimal features that are listed in Table 2.
Table 2
No Roles Features
1 Scheduler ❖ Login.
❖ Hall Management:
o Add new hall information.
o View and filter hall Information.
o Edit existing hall Information.
o Delete hall information.
o Hall availability schedule:
▪ Set start date and time availability.
▪ Set end date and time availability.
▪ Write remarks (optional). Example:
“Hall reserved for a July, 2024
Conference on Sustainable
Energy.”
o Hall maintenance schedule:
▪ Set start date and time for
maintenance operation.
▪ Set end date and time for
maintenance operation.
▪ Write remarks (optional). Example:
“Air conditioning check and
lighting repairs.”
❖ Logout.
The above features are guidance but not limited to. You
can have your own creative features which are relevant to
the given use case
2 Customer ❖ Registration.
❖ Login.
❖ Update profile information.
❖ Perform Booking by:
o View list of available halls that has been set
by the scheduler.
o Select the preferred hall.
o Proceed to payment.
o View receipt of the payment along with the
booking information (minimally in
JFrame).
❖ View and filter upcoming and past booking
information made by the customer.
❖ Perform cancelling of the booking (must be at least
3 days before the booking date)
❖ Raising any issues with the manager regarding a
booked hall.
 ❖ Logout
The above features are guidance but not limited to. You
can have your own creative features which are relevant to
the given use case
3 Administrator ❖ Login.
❖ Scheduler Staff Management:
o Add new scheduler staff information.
o View and filter scheduler staff Information.
o Edit existing scheduler staff Information.
o Delete scheduler staff information.
❖ User Management:
o View and filter existing user information.
o Block/Delete user information.
❖ Booking management:
o View and filter upcoming and past booking
information for all customers.
❖ Logout
The above features are guidance but not limited to. You
can have your own creative features which are relevant to
the given use case
4 Manager ❖ Login
❖ Sales dashboard:
o View and filter the sales made weekly,
monthly, and yearly from the bookings.
❖ Maintenance operation:
o View and respond to customer issues
regarding the hall.
o Assigning the scheduler(staff) to fix the
issue.
o Change the status of customer issues:
▪ In progress - Work on the task has
started.
▪ Done - The task has been
completed.
▪ Closed - The task is closed and no
further action is required.
▪ Cancelled - The task has been
cancelled and will not be completed.
❖ Logout
The above features are guidance but not limited to. You
can have your own creative features which are relevant to
the given use case

6.0 General Requirements

• The submitted GUI application should compile and execute without errors.
• User input validation should be implemented to avoid logical errors.
• The implementation code must highlight the use of Object-oriented
programming concepts.
 • Database tools like access, oracle, sql servers, etc. are not allowed. Must use
text file(.txt) for storing and retrieving data required for the system.

7.0 Deliverables
• Report and source code
• Submission deadline: 27th September 2024, Friday, 11:59PM, Week 12

7.1 Report:
The report needs to be submitted in softcopy to Moodle with:
A. Cover Page
➢ Module
➢ Coursework Title
➢ Intake code
➢ Student name and id
➢ Date Assigned (The date the report was handed out)
➢ Date Completed (The date the report is due to be handed in)
B. Table of Contents
C. Contents
➢ Design solution (Use Case Diagram and Class Diagram)
➢ Screenshots of output of the program with appropriate
explanations
➢ Description and justification of Object-oriented concepts
incorporated into the solution
➢ Additional feature
D. Limitation and Conclusion
E. References
F. Appendix
• Screenshots of all text files that are used to store the data

7.2 Source Code:

Application source code need to be compiled into zip folder and submitted to
Moodle.

8.0 Assignment Assessment Criteria

The assignment assessment consists of two main components: System Implementation
(40%) and System Documentation (15%).

Assessment Description Weightage (%)

System Performance result of all operations and 16
Implementation design per requirements
Appropriate design and the implementation 16
of codes illustrating the object-oriented
programming concept incorporated
Presentation 8
System Description and justification of the object- 6
Documentation oriented concepts incorporate
 UML Diagrams 4
Program output screenshots 3
Report format and references 2

9.0 Development Tools

The program must be written in Java language, and you can use any Java
development IDE as a tool, but back-end data must be stored in .txt files.

10.0 Academic Integrity

You are expected to maintain the utmost level of academic integrity during the duration
of the course. Plagiarism is a serious offence and will be dealt with according to
regulations of Asia Pacific University on plagiarism.