PAC Booking System

Punjab Council of The Arts
Software Requirements Specification
PUNJAB COUNCIL OF THE ARTS HALL

BOOKING SYSTEM
Version 1.0
Prepared by:
1. Muhammad Luqman IT Administrator
2. Suhail Kamran Maitla AD(Accounts & Finance)

Revision Page
a. Overview
In this Software Requirements Specification document version 1.0, it is written primarily
for the stakeholders of the Punjab Council of The Arts and describes in technical terms the
details of the functionality of the product which is Punjab Council Of The Arts Hall Booking
System. This document contains several information of the system; Overall description and
specific requirements.
In overall description, it gives an overview of the overall perspective and requirements of

the system. It describes the informal requirements and is used to establish a context for the
technical requirements specification. While in specific requirements section, it will show and
describe the details of the requirements that a stakeholder needs to know, which comprise the
domain model.
b. Target Audience
1. Stakeholder
2. Punjab Council of The Arts
3. Teachers
4. Teenagers
5. Business Activities
6. Social Society
ii
Ta ble of Contents
1 Introduction………………………………………………………………. 1
1.1 Purpose…………………………………………………………………….... 1
1.2 Scope……………………………………………………………………….... 1
1.3 Definitions, Acronyms and Abbreviations………………………………...... 2
1.4 References…………………………………………………………………… 2
1.5 Overview…………………………………………………………………….. 3
2 Overall Description………………………………………………………. 4
2.1 Product Perspective…………………………………………………………. 5-6
2.1.1 System Interfaces……………………………………………… 7
2.1.2 User Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communication Interfaces
2.1.6 Memory
2.1.7 Operations
2.1.8 Site Adaptations Requirements
2.2 Product Functions
2.3 User Characteristic
2.4 Constraints
2.5 Assumption and Dependencies
2.6 Apportioning of Requirements
iii
3 Specific Requirements
3.1 External Interface Requirements
3.2 System Features
3.2.1 Module < Admin Module>
3.2.1.1 UC001: Use Case < Admin Module >
3.3 Performance Requirements

3.4 Design Constraints
3.5 Software System Attributes
3.6 Other Requirements
Appendices (if any)
iv
1. Introduction
1.1Purpose
The purpose of this document is to present a detailed description of the Punjab Council of
The Arts Hall Booking System. It will explain the purpose and features of the system, the
interfaces of the system, what the system will do, the constraints under which it must operate
and how the system will react to external stimuli. This document is intended for both the
stakeholders and the developers of the system.
1.2Scope
In our website user can view home, about us, information, location of Hall, contact,
promotion, booking, price, login and signup page. User also can check the hall rent price of
the nonmember and member as well. As a guest, user can only view the systems and
feedback us.
For the user who sign up as a member, after login, they able to view home, about us,
information, location of Hall, contact, promotion, booking, price, payment, profile update and
prices in detail. Only members can book our Hall and make payment in online/Cheque. For
booking, the details required are the date (check in & check out), no. of Participant, Function
Type, payment.
For users who are not a member and would like to book a Hall must register and become a
member. It is easy to register and requirements are Full Name, Username, Address, Phone
Number, Email Address, Gender, State, Date of Birth, Username, Password, IC/Passport
number. Billing information is required of making payment via transfer from their account to
our account and we just need the references number, name, and bank name or Cheque.
1
1.3Definitions, Acronyms and Abbreviation
Acronym Definition
SRS Software Requirement System
Administrator Admin/ Owner
Project Refers to state that belong to the company
Grade The booking may be rejected or accepted at
low price by Punjab Arts Council.
Stakeholder Any person who is directly or indirectly
involve and have interest in this project.
1.4Overview
Overall Description section, of this document gives an overview of the functionality of the
system. It describes the informal requirements and is used to establish a context for the
technical requirements specification.
Requirements Specification section, this document is written primarily for both the
stakeholders involved and developers. It describes in technical terms the details of the
functionality of the system.
2
2. Overall Description
This section will show the interactions of the system with another context and it’s a basic
functionality. Besides, this section will show a simple Hall management system and
promotion on it. Punjab Council of The Arts Hall Booking System is a booking system that
is specially designed for Punjab Council of The Arts, Penang to improve efficiency of their
Hall selling process as well as optimize the operating costs. The system will allow the
customer to do booking and payment. The owner could deal with customer all the time. For
example; updating price and promotion, editing profile, adding and editing Hall type
Besides, the system will allow the owner to keep track on the viewing number of members
that book the Hall and its process of booking. Punjab Council of The Arts could be able to,
viewing monthly booking and payment report by owner. The owner can attach some
promotion update for customers view. The new user of the system also can do sign up and
view the website, then drop a feedback.
3
Figure 1: Use Case Diagram of Punjab Council of The Arts Hall Booking System
4
2.1 Product Perspective
This Punjab Council of The Arts Booking System requires external system GPS which feeds
the input into the system for contact us functions. Besides, this system relies on the input of
the users. Whereas for database management, this system needs to interact with database
management software.
Figure 2: Use Case Diagram of Punjab Council of The Arts Hall Booking System
5
2.1.1 System Interfaces
This booking system contains seven modules that serves specific functions to full fill the
system’s goals. The modules are User Module, Admin Desk and Member Module. The owner
known as administrator, who can access to Admin Desk Modules for some main function
which doesn’t excess in other module. For customer the provided module is Member Module.
The function is login, Hall booking and logout. However, new quest for our booking system
is able to use User Module to do signup and then, go to login.
Since the system is used by different users, the category of user interfaces (UI) is depending
on the functions the user is authorized to perform. User access such as login and then to
homepage is provide for all Punjab Council Of The Arts members. Through this homepage
interface, all basic user’s functions are shown but can be accessed after login and based on
user access authorization. This system is very user friendly which the new users of the system
only can sign up and then to drop feedbacks from the experience users before operating it.
Just like any other system, this system requires basic computer that consists of CPU, monitor,
keyboard and mouse or laptop and smartphones for input and output. Printer is needed for
print functions if required. Besides, for direction the system is connected with GPS device in
every organization transportation vehicle to get the transportation details.
The system will require software IIS to program and create Punjab Council of The Arts Hall
Online Booking System. Booking process of the system that organizes the distribution of
users in the local network and able to do this online booking.
6
The system communication interface is completely depending on server software to ensure

correct send and retrieves data from the database. Other than that, is an online protocol to
connect between GPS and the system.
2.1.6 Memory
The program will need at least 80 GB hard disk / disk space and minimum 2 GB RAM space
in order to run at optimum performance.
2.1.7 Operations
a. The users of the system must first login into the system before operate the system
for security purpose.
b. The system is available and active during 24hrs by online execution.
c. The system will be able to create backup for data daily.
d. The system will be able to recover files from backup.
2.1.8 Site Adaptation Requirements
The software does not require any modifications for site adaptation. The system works on
basic computer that is connected to the organization’s local area network.
2.2 Product Functions
This Punjab Council of The Arts Online Booking System aims to make the booking,
checking Hall availability, view, update and cancellation on the booking in the system easier.
Below are the major functions of this system.
7
a. User Module: New quest or user are allowed to go homepage, then can view the
facilities and activities of Hall, Hall promotion and prices, terms and conditions of
Hall and also can use contact us to find the location of Punjab Council Of The Arts
Hall easily. As well, the function of this user module is only able to sign up to the
system and give feedback about the webpage.
b. Member Module: Customer of Punjab Council of The Arts Online Booking System
may login into member login of system to booking and after the confirmation member
can do the payment method to do payment. For customer reference purpose the print
out, function is provided to print their booking information. The member also can
update their profile any time. If incase member forget password, then they could reset
the password using our forget password function.
c. Admin Desk Module: The administrator function is handled by owner/ admin to do

the viewing number of members that book the Hall, add and edit Hall type, view
booking, editing profile, view feedback and reply it. To promo Punjab Council of The
Arts admin can attach the promotion template or image into promotion update for
customer’s views. Admin desk will allow the admin to check the availability of Halls
and also can edit the types of Halls. Then, the admin could able to view all the details
of Hall booking under dashboard and payments details of members
.
2.3 User Characteristics
This Punjab Council of The Arts Hall Online Booking System is designed to be very user
friendly. Users of this system will not require special training before operate this system but
just a short briefing by the experienced users regarding the detailed functionalities. However,
all the users must acquire basic computer knowledge and knowing English as the system is
in these two languages. The users also can experience the time save by do booking in this
system.
2.4 Assumption and Dependencies

8
a. The user of the system is assumed to have their own unique ID and password for
login purposes.
b. The backup ability shall be available for Punjab Council of The Arts to avoid
data lost. If the company does not have backup storage, assumption is made that the
local server will not have downtime and data lost.
c. Assuming all the users for this system have basic computer knowledge and knows
how to operate the system smoothly.
2.5 Apportioning of Requirements
For Punjab Council of The Arts Hall Online Booking System, several functions are omitted.
These functions might be implemented in the future such as upgrade the system by
connecting to mobile application. A brief of the plan is we will launch our system in mobile
application that user can just download our system as apps in mobile and make updating
using mobile. Furthermore, if they make update, security code will be sent to the mobile
number that registered.
9
3. Specific Requirements
Figure 3: Domain Model of Punjab Council of The Arts Hall Online Booking System
10
Figure 4: State Machine Diagram of Punjab Council of The Arts Hall Booking System
3.1 External Interface Requirements
The system is a standalone system that does not use external system. But the system will
require database management software like MS SQL Server to manage the process of storing
the system data, and web server software that organizes the distribution of users in the local
network.

11
This system will require software MS SQL Server, ASP.net, IIS to program and create
Punjab Council of The Arts Hall Online Booking System. Microsoft Office 2017 (Word,
Excel, Access) and Adobe Master Collection CS5 (Photoshop, Illustrator) are used to support
for the system. Internet browser support such as Google Chrome and Mozilla can use by user.
Booking process of the system that organizes the distribution of users in the local network.
Window XP, Vista, 7 , 8, 9 and 10 also can supported by this system.
The system communication interface is completely depending on server software to ensure

correct send and retrieves data from the database. Other than that, is an online protocol to
connect between GPS and the system.
3.2 System Features
3.2.1 Admin Module
12
Figure 41: Admin Module
3.2.1.1 UC-001: Sign up diagram

Include system sequence diagram and activity diagram for each respective use case. See
example below for Punjab Council of The Arts Hall Online Booking System case for
system registration diagrams.
Use case Name Sign Up
13
Goal New Registrations
Primary Actors Customer
Secondary Actors None
Precondition Customer shouldn’t already be exist
Post condition Creating customer’s details/information
Triggers
Main flow Step Action
1 Enter Username
2 Enter New Password
3 Enter Full Name
4 Enter IC Number
5 Enter DOB
6 Enter Gender
7 Enter Full Address
8 Enter Email
9 Enter Contact
10 Tick Agree
11 Enter Captcha
12 Click Register
13 System validates details
14 Update database
15 Display “Successful message”
Extensions Customer details are incorrect,

Display the message "Unsuccessful.
1.1
14
Figure 42: System sequence diagram for sign up
15
Figure 43: Activity diagram for sign up
3.2.1.2 UC-002: Check Availability

16
Use case Name Check Availability
Goal To check whether a room available or not
Precondition Login to the system.
Post condition
Triggers
1 Login into system
2 Select Availability Tab
3 Enter room type, duration, number of

adults and children
4 System check room availability

relevant to each requirement
5 Display available room details
6 View reservation details
7 Print the reservation details
8 Make Payment
9 Manage the booking
11 Update database
Extensions 2.1 No room available for entered details

and display “No Room Available”
Table 2: Use case description for UC-002
17
Figure 44: System sequence diagram for check availability
18
Figure 45: Activity diagram for Check Availability
19
3.2.1.3 UC-003: Payment
Use case Name Payment
Goal Make payment for booked rooms
Post condition
Triggers
1 Login into system
2 Enter booking number
3 Enter reference number
4 Select date
5 Select method to choose bank
6 Enter amount
7 Click submit
9 Update database
Extensions 3.1 Bank/Payment details are incorrect,

20
Figure 46: System sequence diagram for payment
21
Figure 47: Activity diagram for payment
3.2.1.4 UC-004: Update profile

22
Use case Name Update Profile
Goal Manage user profile/information
Post condition
Triggers
1 Login into system
2 Enter new username
3 Enter new password
4 Click submit
6 Update database
Extensions 4.1 Password doesn’t match, Username is

already existed.
Display the message "Unsuccessful”.
23
Figure 48: System sequence diagram for Update profile
24
Figure 49: Activity diagram for Update profile
3.2.1.5: UC-005: Admin login
Use case Name Admin Login
25
Goal View admin profile
Primary Actors Admin
Post condition
Triggers
1 Login into system
2 Enter username
3 Enter password
4 Click submit
6 Update database
Extensions 4.1 Incorrect username or password.
26
Figure 50: System sequence diagram for admin login
27
Figure 51: Activity diagram for admin login
3.2.1.6: UC-006: booking manage

28
Use case Name Booking Manage
Goal View customer booking payment status
Post condition
Triggers
1 Login into system
2 Click paid button if customer done

payment
4 Update database
Extensions
29
Figure 52: System sequence diagram for booking manage
30
Figure 53: Activity diagram for booking manage
31
3.2.1.7: UC-007: payment
Use case Name Payment
Goal View customer booking payment via bank
Post condition
Triggers
1 Login into system
2 Click received button if customer done

payment.
4 Update database
32
Figure 54: System sequence diagram for payment
33
Figure 55: Activity diagram for payment
3.2.1.8: UC-007: Report

Use case Name Report
34
Goal View booking and payment report
Post condition
Triggers
1 Login into system
2 Choose month for view the details.
4 Show the details.
Extensions
35
Figure 56: System sequence diagram for Report
36
Figure 57: Activity diagram for Report
37
3.2.1.9: UC-007: Search
Use case Name Search
Goal Search booking info
Post condition
Triggers
1 Login into system
1 Admin select search option
2 System displays search interface
3 Admin enters booking number
4 System validates admin inputs
5 Display search results
Extensions Admin inputs are invalid and prompt
4.1 Display unsuccessful message
38
Figure 58: System sequence diagram for Search
Figure 59: Activity diagram for Search
3.2.1.10: UC-007: Add room
39
Use case Name Add Hall
Goal Add a new Hall to the system
Precondition Log in to the system
Post condition
Triggers
Login into system
1 Admin clicks “Hall”
2 Choose Hall
2 System prompts the admin to fill out

Hall details
3 System validates new/update hall

information
4 System creates a new/update room
5 Update database
6 Display “successful” message
Extensions
Hall details are incorrect, Display the

message "Unsuccessful" and display
3.1
room management option.
40
Figure 60: System sequence diagram for Add Hall
41
Figure 61: Activity diagram for Add Hall
3.2.1.11: UC-007: Add Promotion

Use case Name Add Promotion
42
Goal Add promotion to the system.
Post condition
Triggers
1 Login into system
2 Admin clicks “Promotion”
3 Click choose button
4 Select picture
5 Click Upload Button
6 Update database
Extensions
If type invalid display “Invalid type”.
4.1
43
Figure 62: System sequence diagram for Add Promotion
Figure 63: Activity diagram for Add Promotion
44
3.2.1.12: UC-007: Feedback
Use case Name Feedback
Goal View/ reply Feedback
Post condition
Triggers
1 Login into system
2 Admin clicks “Feedback”
3 Click reply button
4 Open outlook for reply feedback
5 Send the reply
Extensions
45
Figure 64: System sequence diagram for Add Promotion
46
Figure 65: Activity diagram for Add Promotion
3.3 Performance Requirements
47
3.3.1 System dependability
If the software loses the connection to the Internet, the user should be informed by the system
with a “Data could not be retrieved as there is an error occur in data connection.” message.
Else if the system gets some strange input, the system shall be able to display an incorrect
password message to the user.
3.3.2 Reduce data redundancy

It will have a perfect collection of data information where no duplicates of a data. By the
way, it also helps us to make a search easier rather than flipping thousands of files.
3.4 Design Constraints
3.4.1 Hard drive space

The program will need at least 80 GB hard disk / disk space and minimum 2 GB RAM space
in order to run the booking process.
3.5 Software System Attributes
3.5.1 Reliability
The reliability that the system gives the right result on a search must be more than 98%.
3.5.2 Availability
The system should available more than 98% of the time (not considering network failing).
3.5.2.1 Internet connection

The system should be connected to the Internet to do booking process in online 24hrs.
3.5.3 Security
The system should provide secured communication with the server. 100% of the exchange
48
of information between client and server in the communication of a login session should be
encrypted. Indicate any specific attributes that the customers/users request such as system
must be attractive and easy to use for any specific customers.
3.5.3.1 Security of the accounts

The system should be notified about login failure and prevent admin from logging in to the
system if that admin tries to login with a non-existing account.
3.5.3.2 Security of creating new account for user of the system

The system should ask the user to choose a different username if the user wants to create an
account and the desired username is already occupied.
3.5.4 Extensibility
The system should be easy to extend. The code of the system should be written in a way that
it favors implementation of new functions easily in the future.
3.5.5 Portability
The system should be portable with operating system such as Linux, Windows ‘95 up to the
latest version and Mac OS.
3.5.6 Usability
The system should be easy to handle and navigates in the most expected way with no delays.
49

PAC Booking System

Uploaded by

Copyright:

Available Formats

You might also like

PAC Booking System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PAC Booking System

Uploaded by

Copyright:

Available Formats

Punjab Council of The Arts

Software Requirements Specification

PUNJAB COUNCIL OF THE ARTS HALL

2. Suhail Kamran Maitla AD(Accounts & Finance)

In overall description, it gives an overview of the overall perspective and requirements of

3.3 Performance Requirements

Appendices (if any)

2.1.2 User Interfaces

2.1.3 Hardware Interfaces

2.1.4 Software Interfaces

The system communication interface is completely depending on server software to ensure

2.1.8 Site Adaptation Requirements

2.2 Product Functions

c. Admin Desk Module: The administrator function is handled by owner/ admin to do

2.3 User Characteristics

2.4 Assumption and Dependencies

2.5 Apportioning of Requirements

3.1 External Interface Requirements

3.1.1 User Interfaces

3.1.3 Software Interfaces

3.1.4 Communication Interfaces

The system communication interface is completely depending on server software to ensure

3.2 System Features

3.2.1 Admin Module

3.2.1.1 UC-001: Sign up diagram

Use case Name Sign Up

Primary Actors Customer

Secondary Actors None

Precondition Customer shouldn’t already be exist

Post condition Creating customer’s details/information

Main flow Step Action

2 Enter New Password

3 Enter Full Name

7 Enter Full Address

13 System validates details

15 Display “Successful message”

Extensions Customer details are incorrect,

3.2.1.2 UC-002: Check Availability

Goal To check whether a room available or not

Primary Actors Customer

Secondary Actors None

Precondition Login to the system.

Main flow Step Action

1 Login into system

2 Select Availability Tab

3 Enter room type, duration, number of

4 System check room availability

5 Display available room details

6 View reservation details

7 Print the reservation details

9 Manage the booking

10 System validates details

12 Display “Successful message”

Extensions 2.1 No room available for entered details

Table 2: Use case description for UC-002

Goal Make payment for booked rooms

Primary Actors Customer