Software Requirements

Specification

for

e-Tempahan System

Version 1.4

Prepared by

Group Name: ISE Apprentice

Ainaa Najihah bt. Rusali 2012372699 [email protected]

Wan Nur Syahira bt. Wan 2012310269 [email protected]
Othman
Wan Nur Syahirah bt. Wan Ismail 2012397085 [email protected]
Nur Husna bt. Abdul Rahman 2012132451 [email protected]
Mohd Sabry b. Mohd Safiq 2012938081 [email protected]
Nurul Fatihin bt.Mohd Sahid 2012599831 [email protected]

Date of Re-Submission: 27/06/2014

Software Requirements Specification for e-Tempahan System Page ii

Contents

1 INTRODUCTION ................................................................................................................. 1
1.1 DOCUMENT PURPOSE ....................................................................................................... 1
1.2 PRODUCT SCOPE ............................................................................................................... 1
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW .......................................................... 2
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS .............................................................. 2
1.5 DOCUMENT CONVENTIONS............................................................................................... 3
1.6 REFERENCES AND ACKNOWLEDGMENTS .......................................................................... 3
2 OVERALL DESCRIPTION ................................................................................................ 4
2.1 PRODUCT PERSPECTIVE .................................................................................................... 4
2.2 USERS AND CHARACTERISTICS ......................................................................................... 5
2.3 OPERATING ENVIRONMENT .............................................................................................. 6
2.4 DESIGN AND IMPLEMENTATION CONSTRAINTS ................................................................. 6
2.5 USER DOCUMENTATION ................................................................................................... 7
2.6 ASSUMPTIONS AND DEPENDENCIES .................................................................................. 7
3 SYSTEM FEATURES .......................................................................................................... 8
4 OTHER NON-FUNCTIONAL REQUIREMENTS......................................................... 21
4.1 PERFORMANCE REQUIREMENTS ..................................................................................... 21
4.2 SAFETY AND SECURITY REQUIREMENTS ........................................................................ 21
4.3 SOFTWARE QUALITY ATTRIBUTES ................................................................................. 22
APPENDIX A – REQUIREMENT MODELS ......................................................................... 23
Software Requirements Specification for e-Tempahan System Page 1

1 Introduction

1.1 Document Purpose

The main purpose of System Requirement Specification (SRS) documentation is to describe the
functional and non-functional requirement regarding e-Tempahan System. This document has
been developed after organizing the System Development Plan (SDP) document. The
objectives of e-Tempahan System is to eliminate booking delays and to save time. The data that
is included in the system will be more organized and secured. With the existence of the project,
it will also increase customer’s satisfaction. It also helps the flow of hall’s booking to be more
organized and systematic and also helps to increase the frequency of customer’s booking.
It will explain the purpose and features, interfaces, capabilities of the system, the constraints
under which it must operates and how the system will react to external stimuli.

1.2 Product Scope

In this part, the scope of the project is to provide information capabilities which help the
customers to find out more detailed hall information. Currently, Majlis Bandaraya Shah Alam
(MBSA) is using manual system where customer has to fill up forms to book a hall. Thus, we
have come out with a great idea by developing a system for hall booking. Customer can make
online booking where they must create an account, login to the system, view hall information,
create hall booking and manage their booking. In addition, staffs are able to login to the system,
manage hall details and view hall booking details. Four model operations of our system are:
a) Staff Subsystem
b) Customer Subsystem
c) Booking Subsystem
d) Hall Subsystem
Software Requirements Specification for e-Tempahan System Page 2

1.3 Intended Audience and Document Overview

The target audiences for this document are developer, project managers, programmer, designers
and client. The purpose of this document is to describe the system requirement specification for
e-Tempahan system. Plus, this document can be the reference to the new staff in order to
comprehend the flow of the system. Several modeling have been described in the
documentation including Use Case Diagram, Use Case Description, Activity Diagram , System
Sequence Diagram and Domain Class Diagram.

1.4 Definitions, Acronyms and Abbreviations

Acronyms Definitions

SDP Software Development Plan

SDLC Software Development Life Cycle

SRS Software Requirements Specifications

DCD Design Class Diagram

SDD Software Design Description

REQ Requirement

SCM Supplier Chain Management

CSS Customer Support System

SRS Software Requirements Specification

SSD System Sequence Diagram

Table 1 : Acronyms and its Definitions.

Software Requirements Specification for e-Tempahan System Page 3

1.5 Document Conventions

ACRONYMS DEFINITIONS

VD Vision Document

SDP Software Development Plan

SRS Software Requirements Specifications

REQ Requirement

WBS Work Breakdown Structure

Table 2 : Document Conventions

1.6 References and Acknowledgments

Book
1. John W. Satzinger, Robert B. Jackson, Stephen D. Burd, Introduction to Systems
Analysis and Design: An Agile, Iterative Approach, Sixth International Edition, Joe Sabatino,
2012.

Other
1. Use Case Diagram, Activity Diagram, Use Case Description and Sequence Diagram.
2. Software Development Plan (SDP).
3. Vision Document (VD).

2. Overall Description

2.1 Product Perspective

This is a web-based application system that is known as e-Tempahan system, that provide
company the online booking systems, which is the Web Site for this company and the
customers to booked hall. This e-Tempahan system is a main system of the modules subsystem.
Software Requirements Specification for e-Tempahan System Page 4

There are five modules in this e-Tempahan system there are staff subsystem, customer
subsystem, booking subsystem, hall subsystem and finance subsystem.
1. Customer Subsystem
a) Create customer information.
b) Login to the system.
c) Update customer information.
d) View customer information.
2. Booking Subsystem
a) Customer
- Create hall booking.
- Update hall booking.
- Cancel booking.
3. Hall Subsystem
a) Customer
- View hall information.
b) Staff
- View hall information.
- Create new hall.
- Update hall information.
Software Requirements Specification for e-Tempahan System Page 5

2.2 Users and Characteristics

Users and characteristics describe more about the two types of users which include Staff,
Authenticated user and Anonymous user. The table below will describe about the different of
characteristic, limitation, frequently use and way to access into the system.

User Staff Authenticated user Anonymous user

Characteristic Have authorities to The important Visitor that is able to
change the content of customer or member see the e-service lists
system side and can be the member
of the system by doing
registration.
Limitation This user can Specified to their This user cannot
perform or view own area. They can access to staff and
more task compared access their details authenticated user.
to other user because only but to access They only can view
there is staff account others are prohibited. the information which
included in the do not require
system. authentication.

Frequently use High frequency Medium frequency Low frequency

Accesses Can access to both Can access to Do not require
side using username member side using username and
and password username and password.
created. password created.

Table 3 : User Classes and Characteristic

Software Requirements Specification for e-Tempahan System Page 6

2.3 Operating Environment

ITEM Description

Operating system Windows 8

Tool Microsoft Office 2010, Microsoft Office 2007, starUML, Netbeans,

Microsoft Visio, Microsoft Powerpoint.

Database ORACLE.

Language Java html, CSS

Server Apache Tomcat.

Table 4 : Operating environment used in the project development.

2.4 Design and Implementation Constraints

1. Hardware constraints
a) Not enough workstation
b) Slow workstation
c) Lack of workers

2. Software constraints
a) Lack of knowledge and skills on tools.
b) Good proprietary software is too expensive.
c) Development tools are not stable and reliable.
Software Requirements Specification for e-Tempahan System Page 7

2.5 User Documentation

a) User manual

b) Research

c) Online Tutorial

d) Book (Introduction to System Analysis and Design)

2.5 Assumptions and Dependencies

For this project, we will discuss among six of us and refer to Majlis Bandaraya Shah Alam and
we also often consult with our lecturers which are PM. Aishah bt. Ahmad and Dr. Suriyati bt.
Razali to avoid misinterpretation for finishing this project. This project must be completed
within three months. The information that we have will help to smooth the progress and save
time. We went to Majlis Bandaraya Shah Alam for conducting an interview and after that, we
decided to develop a web based system for corporate department in MBSA. Before starting the
interview, we have provided a sample of questionnaire for MBSA in order to ensure that we get
the right data. There are several constraints while finishing this project. For example, we do not
have much time to make a progression, lack of requirements, staff and quality of software. The
assumptions and dependencies we need most are the greater internet connection for our project
development because without connection of internet our project cannot be implemented.
Besides, we need more information about MBSA to develop the system. To run this system, the
web browser that we have suggested is Mozilla Firefox or Google Chrome. The most vital issue
is the administrator has to verify the authenticated user to use the system.
Software Requirements Specification for e-Tempahan System Page 8

3. System Features

Figure 1 : Use Case Diagram for e-Tempahan System

Software Requirements Specification for e-Tempahan System Page 9

1.1 Use Case Description

Use Case ID: UC100

Use Case Register Account
Name:
Created By: Nur Husna Abdul Last Updated By: ISE Apprentice
Rahman
Date Created: 15 June 2013 Date Last 6 April 2014
Updated:

Actor: Customer

Description: Customer registers their account by entering personal details.

Preconditions: Customer account subsystem must be available.

Post conditions: Customer account successfully registered.

Priority: High

Frequency of Use: Frequent

Normal Course of Actor System

Events: 1. Customer selects to 1.1 System displays
register account. registration form for
customers to fill up their
personal details.
2. Customer inserts personal 2.1 System checks the validity
details. of the data.
<E1> <E2> <E3><E4>
- IC Number
- Name 2.2 System records the
- Phone Number 1 customer’s personal
details.
- Phone Number 2
- Email
- Street
- City
- Postcode
-State
- Password
Alternative Courses: -
Software Requirements Specification for e-Tempahan System Page 10

Exceptions: Actor System

<E1> Customer’s personal <E1.1> System displays
details are incomplete. message for
customer :
- “No Kad Pengenalan tidak
lengkap!”
- “Nama tidak lengkap!”
- “No Telefon 1 tidak
lengkap!”
- “Emel tidak lengkap!”
- “Alamat tidak lengkap!”
- “Bandar tidak lengkap!”
- “Poskod tidak lengkap!”
- “Negeri tidak lengkap!”
- “Kata Laluan tidak lengkap
atau lebih dari 6!”
- “Pengesahan Kata Laluan
tidak lengkap!”
<E1.2> System displays the
registration form.

<E2> Customer’s account <E2.1> System displays

already exists. message for
customer :
- “No. Kad Pengenalan
sudah wujud! Sila cuba
lagi!”
<E2.2> System displays the
registration form.

<E3> Customer enters invalid <E3.1> System displays

data into the form. message for
customer :
- “Ralat, ruangan kad
pengenalan ini diisi dengan
12 angka sahaja.”
- “Ralat, ruangan nama ini
diisi dengan abjad sahaja.”
- “Ralat, ruangan nombor
telefon ini diisi dengan angka
sahaja.”
-“Ralat, emel tidah sah.”
Software Requirements Specification for e-Tempahan System Page 11

<E3.2> System displays the

registration form.

<E4> Customer did not enter <E4.1> System displays

the same password at message for customer :
the Sah Kata Laluan - “Kata Laluan tidak sah!”
field.

Includes: N/A
Special Requirements: Security
Assumptions: N/A
Notes and Issues: N/A
Software Requirements Specification for e-Tempahan System Page 12

Use Case ID: UC200

Use Case Authenticate Password
Name:
Created By: Wan Nur Syahirah Last Updated By: ISE Apprentice
Wan Ismail
Date Created: 29 November 2013 Date Last 6 April 2014
Updated:

Actor: Customer, Staff

Description: Customer enters their IC number and password to login.

Staff enters their staff ID and password to login.
Preconditions: Customer’s account must be available.
Staff’s account must be available.
Post conditions: The customer and the staff are successfully logged in.

Priority: High

Frequency of Use: Frequent

Normal Course of Actor System

Events: 1. Actors have to login to the 1.1 System displays login
system. form.

2. Customer enters IC 2.1 System checks the

number and password. Staff entered IC number or
enters staff ID and password. staff ID and password.
<E1>
2.2 System allows actor to
enter account.

Alternative Courses: -
Exceptions: Actor System
<E1> Customer enters the <E1.1> System displays
wrong IC number or message for the actor :
password. Staff enters wrong - “Ralat, sila cuba lagi.”
staff ID or password. <E1.2> System displays login
form.

Includes: -
Assumptions: -
Notes and Issues: -
Software Requirements Specification for e-Tempahan System Page 13

Use Case ID: UC300

Use Case Maintain Personal Details
Name:
Created By: Wan Nur Syahira Wan Last Updated By: ISE Apprentice
Othman
Date Created: 15 June 2013 Date Last 6 April 2014
Updated:

Actor: Customer

Description: The customer can maintain their own personal details.

The customer can view and update their personal details.
Preconditions: 1. Customer must log in into the system.
2. The customer subsystem and customer account must be
available.
3. The customer must view their personal details.
Post conditions: Customer account successfully viewed and updates their
personal details.
Priority: Low.

Frequency of Use: Not frequent.

Normal Course of Actor System

Events: 1. Customer views their 1.1 System displays the
personal details. customer’s personal
details.
UC301 – Update Personal
Details

Alternative Courses: Actor System

UC301 – Update Personal
Details
A1 Customer selects to A1.1 System displays
update form for customer
update their personal to update their personal
details. details.

A2 Customer enters new A2.1 System checks validity

personal details : of the data <E1>
- Name A2.2 System records the
updated customer’s
- Phone Number 1 personal details.
- Phone Number 2
- Email
- Street
- City
- Postcode
- State
- Password
Software Requirements Specification for e-Tempahan System Page 14

Exceptions: Actor System

<E1> Customer’s updated <E1.1> System displays
personal details are message for customer :
incomplete or invalid - “Ralat, ruangan nama tidak
lengkap atau diisi dengan
abjad sahaja.”
- “Ralat, ruangan no telefon 1
tidak lengkap atau diisi
dengan angka sahaja.”
- “Ralat, ruangan no telefon 2
ini diisi dengan angka
sahaja.”
- Ralat, emel tidak sah.”
- “Ralat, ruangan alamat tidak
. lengkap atau diisi dengan
abjad sahaja.”
- “Ralat, ruangan bandar
tidak lengkap atau diisi
dengan abjad sahaja.”-
“Ralat, ruangan poskod tidak
lengkap atau diisi dengan 5
angka sahaja.”
- “Ralat. Ruangan Negeri
tidak lengkap, sila pilih
negeri”

<E1.2> System displays the

update form.
Includes: N/A
Special Requirements: Security
Assumptions: N/A
Notes and Issues: N/A
Software Requirements Specification for e-Tempahan System Page 15

Use Case ID: UC400

Use Case Name: Manage Hall Details

Created By: Ainaa Najihah Rusali Last Updated By: ISE Apprentice
Date Created: 15 June 2013 Date Last 6 April 2014
Updated:

Actor: Staff

Description: Staff is able to add new hall and update the hall details.

Preconditions: 1. Staff must log in into the system.

2. The hall subsystem must be available.
3. The hall must exist.
Post conditions: 1. New hall is successfully added.
2. Hall information is successfully updated.
Priority: Medium.

Frequency of Use: Not frequent.

Normal Course of Actor System

Events: 1. Staff selects to manage hall 1.1 System displays the
information :- options to add or update
hall details.
UC401 - Add new hall
UC402 - Update hall details
Software Requirements Specification for e-Tempahan System Page 16

Alternative Courses: Actor System

UC401 - Add new hall

A1 Staff selects to add new A1.1 System displays form

hall into the system. for staff to enter new hall
details.

A2 Staff enters new A2.1 System checks for the

hall details. validity of the data.
-Hall ID <E1><E2><E3>
-Hall Name
-Hall Charge A2.2 System records the
-Hall Type added hall details.
-Hall Capacity
-Hall Address
-Facility provided in the hall

UC402 - Update hall details

A1 Staff selects to update A1.1 System displays list of

hall details. halls.

A2 Staff selects the hall that A2.2 System displays the hall
need to be updated. details and update
form for staff to enter
the updated hall details.

A3 Staff enters updated hall A3.1 System checks the

details. validity of the data.
<E2><E3>
A3.2 System records the
updated hall details.
Software Requirements Specification for e-Tempahan System Page 17

Exceptions: Actor System

<E1 >The hall id already <E1.1> System displays
existed. message for the staff :
-“ ID dewan sudah wujud!
Sila cuba lagi!”
<E1.2> System displays the
hall form.

<E2> Hall details are <E2.1> System displays

incomplete. message for staff :
- “ID dewan tidak lengkap!”
- “Nama dewan tidak
lengkap!”
- “Harga dewan tidak
lengkap!”
- “Jenis dewan tidak
lengkap!”
- “Kapasiti dewan tidak
lengkap!”
- “Alamat tidak lengkap!”
- “Bandar tidak lengkap!”
- “Poskod tidak lengkap!”
- “Fasiliti tidak lengkap!”
<E2.2> System displays the
hall form.

<E3> Staff enters invalid data <E3.1> System displays

into the form. message for customer :
- “Ralat, ruangan harga
dewan ini diisi dengan angka
sahaja!”
-“Ralat, rungan jenis dewan
ini disi dengan abjad sahaja!”
-Ralat, ruangan kapasiti ini
diisi tidak melebihi 5 angka!”
<E3.2> System displays the
hall form.
Includes: N/A
Special Requirements: Security
Assumptions: N/A
Software Requirements Specification for e-Tempahan System Page 18

Notes and Issues: N/A

Use Case ID: UC500

Use Case Manage Booking
Name:
Created By: Mohd Sabry Mohd Last Updated By: ISE Apprentice
Safiq
Nurul Fatihin Mohd
Sahid
Date Created: 15 June 2013 Date Last 6 April 2014
Updated:

Actor: Customer, Staff

Description: 1. Customer books hall by viewing hall details first.

2. Customer updates their booking details.
3. Customer cancel booking by deleting the booking details.
4. Staff can view the list of booking details.
Preconditions: 1. Customer account must exist and log in to the system.
2. Customer must view the hall details to book the hall.
3. Customer must check hall availability first before book the
hall.
4. Customer must fill up the booking form.
5. Staff must login to the system.
Post conditions: 1. Hall booking is successfully created by the customer.
2. Booking information is successfully updated by the
customer.
3. Hall booking is successfully viewed by staff.
Priority: High.

Frequency of Use: Frequent.

Normal Course of Actor System

Events: 1. Customer selects to 1.1 System displays the
manage booking :- options to book or
update booking details.
UC501 - Book hall.
UC502 - Update booking
details.
UC503 – Cancel booking.

2.Staff selects to view

booking details :-
UC504 – View booking
details.

Alternative Courses: Actor System

Software Requirements Specification for e-Tempahan System Page 19

UC501 - Book hall.

A1 Customer selects to book A1.1 System displays the list
of hall.
a hall.

A2 Customer chooses a hall.

A2.1 System validates the
chosen hall.

A2.2 System displays the hall

details.

A2.3 System displays form

for customer to enter desired
session and date.

A3.1 System checks the hall

A3 Customer choose the availability.<E1>
session and date to check the
hall availability.
A4.1 System displays the
A4 If the hall is available, booking form
customer clicks the
“Tempah” button.
A5.1 System checks the
A5 Customer fills up the validity of the
data.<E2><E3>
booking form and clicks the A5.2 System creates hall
submit button. booking.
A.5.3 System calculate all
charges.
A5.4 System displays the
booking details.

UC502 - Update booking

details.
A1 Customer selects to view A1.1 System displays the
the booking details. customer’s booking details.
A2 Customer selects to A2.1 System displays the
update booking details. update booking form.

A3 Customer enters updated A3.1 System checks the

booking details. validity of the data.
<E1><E2><E3>
A3.2 System records the
updated booking details.
Software Requirements Specification for e-Tempahan System Page 20

UC503 – Cancel booking.

A1 Customer selects to view A1.1 System displays
the booking details. customer’s booking details.
A2 Customer selects to A2.1 System displays popup
cancel booking. message for customer to
confirm deletion.
A3 Customer click “OK”
button. A3.1 System deletes the
chosen booking details.

UC504 – View booking.

A1 Staff selects to view the A1.1 System displays the
booking details booking details.

Exceptions: Actor System

<E1> The session and date is <E1.1> System will disable
fully booked. the fully booked session and
date to be clicked.
<E1.2> Displays message for
customer to choose another
date or session or hall.

<E2> The booking details are

incomplete. <E2.1> System displays
message for customer :
- “Nama acara tidak
lengkap!”
<E2.2> System displays the
booking form.

<E3> Customer enters <E3.1> System displays

invalid data into the form. message for customer :
- “Tambahan jam tidak sah!”
<E3.2> System displays the
booking form.
Includes: N/A
Special Requirements: Security
Assumptions: N/A
Notes and Issues: N/A
Software Requirements Specification for e-Tempahan System Page 21

4. Other Non-functional Requirements

4.1 Performance Requirements

The Web Page of e-Tempahan system will be developed based on Software Development Life
Cycle. Start with system planning, analysis, design, implementation and testing. The
development process will take about 1 year 6 month to be completed. The system capability of
updating the displayed record count within an acceptably short interval of the number of
records changing need to be ensured. It also needs a compatible size of database as the numbers
and information of the customer will be increase from time to time. The system’s response time
must be effective and efficient due to the number of access can be made by more than one
person in a time.

4.2 Safety and Security Requirements

For the safety of the e-Tempahan system requirements, the system must not contain any harm,
or something that can damage the hardware or software to the computer.
For the security requirement, e-Tempahan system is using customer’s IC number or staff ID
and password in order for them to access the system. Customer can book a hall online which is
starting with creating customer account, login to the system, view hall details, create hall
booking, and manage their hall booking. For staff they can login to the system, view hall
booking information, and manage hall details.
Software Requirements Specification for e-Tempahan System Page 22

4.3 Software Quality Attributes

Additional characteristics of the system that important to either customers or staff listed as
below:
1. Adaptability
The system was adapted with the e-Tempahan which requires only a network connection and
anyone can access.
2. Availability
The system provides an enough database that facilitate to keep many customer information and
transaction of booking hall.
3. Correctness
The system displays the right data for customer booking regarding the unique ID key in during
login. An ID refers to identification card (IC).
4. Flexibility
The system can be accessed in anywhere and anytime. Both customer and staff require a
network connection only to access the website.
5. Maintainability
A customer can update their information and also information of hall booking into the system.
Meanwhile a staff can add, update the information of new hall.
6. Reliability
The system is reliable due to security and safety provided together in order to prevent from an
unauthorized access. This will be helping much to smooth the system running due to booking
hall.
Software Requirements Specification for e-Tempahan System Page 23

Appendix A – REQUIREMENT MODELS

SYSTEM SEQUENCE DIAGRAM

UC 100 – Register Account

Customer

createCustomer ( custIC, custName, custPhone1, custPhone2, custEmail,

custAddressStreet, custAddressCity, custAddressPostcode, custAddressState
custPassword )

custIC, custName, custPhone1, custPhone2, custEmail, custAddressStreet,

custAddressCity, custAddressPostcode, custAddressState custPassword

Figure 2 : System Sequence Diagram for actor Customer in Use Case Register Account.
Software Requirements Specification for e-Tempahan System Page 24

UC 200 – Authenticate Password

Customer

validate(custIC, custPassword)

custIC, custPassword

Figure 3 : System Sequence Diagram for actor Customer in Use Case Authenticate Password.

Staff

validate(staffID, staffPassword

staffID, staffPassword

Figure 4 : System Sequence Diagram for actor Staff in Use Case Register Account.
Software Requirements Specification for e-Tempahan System Page 25

UC300 – Maintain Personal Details

Customer

updateCustomer ( custIC, custName, custPhone1, custPhone2, custEmail,

custAddressStreet, custAddressCity, custAddressPostcode, custAddressState
custPassword )

custIC, custName, custPhone1, custPhone2, custEmail, custAddressStreet,

custAddressCity, custAddressPostcode, custAddressState custPassword

Figure 5 : System Sequence Diagram for actor Customer in Use Case Maintain Personal Details
Software Requirements Specification for e-Tempahan System Page 26

UC400 – Manage Hall Details

Staff

createHall( hallID. hallName, hallCharge, hallType, hallCapacity,

hallAddressStreet, , hallAddressCity, , hallAddressPostcode, hallFacility )

hallID. hallName, hallCharge, hallType, hallCapacity, hallAddressStreet,

, hallAddressCity, , hallAddressPostcode, hallFacility

updateHall( hallID. hallName, hallCharge, hallType, hallCapacity,

hallAddressStreet, , hallAddressCity, , hallAddressPostcode, hallFacility )

hallID. hallName, hallCharge, hallType, hallCapacity, hallAddressStreet,

, hallAddressCity, , hallAddressPostcode, hallFacility

Figure 6 : System Sequence Diagram for actor Staff in Use Case Manage Hall Details.
Software Requirements Specification for e-Tempahan System Page 27

UC500 – Manage Booking

Customer

createHallBooking( eventSession, eventName, eventDate, extraHour)

eventSession, eventName, eventDate, extraHour

updateHallBooking( eventSession, eventName, eventDate, extraHour)

eventSession, eventName, eventDate, extraHour

del ( bookID)

Displays message

Figure 7 : System Sequence Diagram for actor Customer in Use Case Manage booking
Software Requirements Specification for e-Tempahan System Page 28

Domain Class Diagram

Figure 8 : Domain Class Diagram for e-Tempahan system.

Software Requirements Specification for e-Tempahan System Page 29

Activity Diagram

UC_100 – Register Account

Customer System

Displays registrations form for

Selects to register account customers to fill up their personal
details

Inserts personal details. Checks the validity of the data

Records the customer personal

details

Figure 9 : Activity Diagram for UC100 - Register Account.

Software Requirements Specification for e-Tempahan System Page 30

UC_200 – Authenticate Password

Actors System

Have to login to the

Display login form
system

Customer enters IC number and

password. Staff enters staff ID
and password

System checks the

entered IC number
or staff ID and
password

Allows actor to enter

account

Figure 10 : Activity Diagram for UC200 - Authenticate Password.

Software Requirements Specification for e-Tempahan System Page 31

UC_300 – Maintain Personal Details

Customer System

Views their personal details

UC301 – Update Personal Displays the customer personal
Details details

Figure 11 : Activity Diagram for UC300 – Maintain Personal Details.

Software Requirements Specification for e-Tempahan System Page 32

UC_301 – Update Personal Details

Customer System

Displays update form for

Selects to update their personal customer to update their
details personal details

Enters new personal details. Checks validity of the data

Records the updated

customer personal details

Figure 12 : Activity Diagram for UC301 – Update Personal Details.

Software Requirements Specification for e-Tempahan System Page 33

UC_400 - Manage Hall Details

Staff System

Selects to manage hall

information:- Display the option to add
UC_401 – Add new hall or update hall details
UC_402 – Update hall details

Figure 13 : Activity Diagram for UC400 – Manage Hall Details.

Software Requirements Specification for e-Tempahan System Page 34

UC_401 – Add New Hall (UC_400 – Manage Hall Details)

Staff System

Selects to add new Display form for staff to

hall into the system enter new hall details

Enters new hall details.

Checks for the
validity of the data

Records the
added hall details

Figure 14 : Activity Diagram for UC401 – Add New Hall.

Software Requirements Specification for e-Tempahan System Page 35

UC_402 – Update Hall Details (UC_400 – Manage Hall Details)

Staff System

Selects to update hall Display list of halls

details

Displays the hall details and

Selects the hall that needs update form for staff to enter
to be updated the updated hall details

Checks the validity of

Enters updated hall
the data
details

Record the updated

hall details

Figure 15 : Activity Diagram for UC402 – Update Hall Details.

Software Requirements Specification for e-Tempahan System Page 36

UC_500 - Manage Booking

Actor System

Select to manage booking:-

UC_501 – Book hall Displays the options to
book or update
UC_502 – Update booking details
booking details
UC_503 – Cancel booking
UC_504 – View booking

Figure 16 : Activity Diagram for UC500 – Manage Booking.

Software Requirements Specification for e-Tempahan System Page 37

UC_501 – Book Hall (UC_500 – Manage Booking)

Actor System

Selects to book a hall Display the list of hall

Choose a hall

Validates the chosen hall

Display the hall details

Choose the session and date to Displays form for customer to enter desired
check the hall availability session and date

Checks the hall availability

If the hall is available, customer

click the “Tempah” button

Display the booking form

Fills up the booking form and clicks

the submit button

Checks the validity of the data

Creates hall booking

Displays the booking details

Figure 17 : Activity Diagram for UC501 – Book Hall.

Software Requirements Specification for e-Tempahan System Page 38

UC_502 – Update Booking Details (UC_500 – Manage Booking)

Customer System

Displays the customer’s

Selects to view the
booking details
booking details

Select to update
booking details

Displays the update

booking form

Enter update
booking details

Checks the validity

data.

Records the updated

booking details.

Figure 18 : Activity Diagram for UC502 – Update Booking Details.

Software Requirements Specification for e-Tempahan System Page 39

UC_503 – Cancel Booking (UC_500 – Manage Booking)

Actor System

Selects to view the booking Display the customer

details booking details

Displays popup message for

Selects to cancel
customer to confirm deletion.
booking

Deletes the chosen booking

Click “OK” button
details.

Figure 19 : Activity Diagram for UC503 – Cancel Booking.

Software Requirements Specification for e-Tempahan System Page 40

UC_504 – View Booking Details (UC_500 – Manage Booking)

Staff System

Selects to view the Displays the booking

booking details details.

Figure 20 : Activity Diagram for UC504 – View Booking Details.

Software Requirements Specification for e-Tempahan System Page 41

PROTOTYPE
1) CUSTOMER INTERFACE
Software Requirements Specification for e-Tempahan System Page 42
Software Requirements Specification for e-Tempahan System Page 43
Software Requirements Specification for e-Tempahan System Page 44
Software Requirements Specification for e-Tempahan System Page 45
Software Requirements Specification for e-Tempahan System Page 46
Software Requirements Specification for e-Tempahan System Page 47
Software Requirements Specification for e-Tempahan System Page 48

2) STAFF INTERFACE
Software Requirements Specification for e-Tempahan System Page 49
Software Requirements Specification for e-Tempahan System Page 50
Software Requirements Specification for e-Tempahan System Page 51