SCSJ2203: Software Engineering
Software Requirements Specification
THE SEA BLUE CHALET BOOKING SYSTEM
Version 1.0
Printing Date
Faculty Computer Science
Prepared by:
1. VISALATCHMI A/P RAJASVARAN
SX140068CSRS01
2. CHITRAN A/L TAMIL CHELVAN
SX141068CSRS01
3. GHANAVATHI A/L KUMARAN
SX140062CSRS01
4. SUTHAN A/L KARUNAMUTHY
SX161526CSRF01
Revision Page
a. Overview
In this Software Requirements Specification document version 1.0, it is written primarily
for the stakeholders of the Mr. Puguneswaran and describes in technical terms the details of
the functionality of the product which is The Sea Blue Chalet 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. The Sea Blue Chalet Company
3. Family
4. Foreigner Tourist
5. Teachers
6. Teenagers
c. Project Team Members
No.
Name
Module
1
VISALATCHMI A/P RAJASVARAN
User
2
CHITRAN A/L TAMIL CHELVAN
Admin Desk
3
GHANAVATHI A/L KUMARAN
Member Login
4
SUTHAN A/L KARUNAMUTHY
Member Login
ii
d. Version Control History
Version
Primary Author(s)
Description of
Version
1.0
VISALATCHMI A/P RAJASVARAN
CHITRAN A/L TAMIL CHELVAN
GHANAVATHI A/L KUMARAN
SUTHAN A/L KARUNAMUTHY
iii
Software
Requirements
Specification
Date
Completed
22/4/2017
Table of Contents
1 Introduction………………………………………………………………. 1
1.1
Purpose……………………………………………………………………....
1
1.2
Scope……………………………………………………………………….... 1
1.3
Definitions, Acronyms and Abbreviations………………………………......
1.4
References…………………………………………………………………… 2
1.5
Overview…………………………………………………………………….. 3
2
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
iv
3 Specific Requirements
3.1
3.2
External Interface Requirements
3.1.1
User Interfaces
3.1.2
Hardware Interfaces
3.1.3
Software Interfaces
3.1.4
Communication Interfaces
System Features
3.2.1
Module < Admin Module>
3.2.1.1
3.3
Performance Requirements
3.4
Design Constraints
3.5
Software System Attributes
3.6
Other Requirements
UC001: Use Case < Admin Module >
Appendices (if any)
v
1. Introduction
1.1 Purpose
The purpose of this document is to present a detailed description of the The Sea Blue Chalet
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.2 Scope
In our website user can view home, about us, information, location of chalet, contact,
promotion, booking, price, login and signup page. User also can check the chalet 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 chalet, contact, promotion, booking, price, payment, profile update
and prices in detail. Only members can book our chalet and make payment in online. For
booking, the details required are the date (check in & check out), no. chalets, chalet type,
payment.
For users who are not a member and would like to book a chalet 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.
1
1.3 Definitions, 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 PTS.
Any person who is directly or indirectly
Stakeholder
involve and have interest in this project.
1.4 Reference
Bud E. Smith, Arthur Bebak (2007). “Creating Web Pages For Dummies”, 8th Edition,
United States. 386 pages.
Richard Mansfield (2005). “CSS Web Design For Dummies”, United States, March 2005.
384 pages.
Noraini (2017). SRS template File and Sample of SRS. Retrieved date, 1st April 2017 from
http://elearning.utmspace.edu.my/16172
Devterch(2013). Plantation Management System. Retrieved date, 10th April 2016 from
http://devterch.com/products/plantation-management-system/
Shahliza & Shahida (2016). SRS-Template-v1.1-ForSCSJ2203-SEUTM-BySS20March2016. Retrieved date, 5th May 2016 from http://elearning.utm.my/15162
1.5 Overview
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 other context and it’s a basic
functionality. Besides, this section will show a simple chalet management system and
promotion on it. The Sea Blue Chalet Booking System is a booking system that is specially
designed for Sea Blue Chalet, Penang to improve efficiency of their crop 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 chalet type
Besides, the system will allow the owner to keep track on the viewing number of members
that book the chalet and its process of booking. The Sea Blue Chalet 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 the Sea Blue Chalet Online Booking System
4
2.1 Product Perspective
This Sea Blue Chalet 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 (Xampp).
Figure 2: Use Case Diagram of the Sea Blue Chalet Online 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 mian function
which doesn’t excess in other module. For customer the provided module is Member Module.
The function is login, chalet booking and logout. However, new quest for our booking system
are able to use User Module to do signup and then, go to login.
2.1.2 User Interfaces
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 Sea Blue Chalet members. Through this homepage interface, all
basic user’s functions is 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.
2.1.3 Hardware Interfaces
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 vehicles to get the transportation details.
2.1.4 Software Interfaces
The system will require software Xampp to program and create The Sea Blue Chalet 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
2.1.5 Communication Interfaces
The system communication interface is completely depend 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 Sea Blue Chalet Online Booking System aims to make the booking, checking chalet
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 allow to go homepage, then can view the
facilities and activities of chalet, chalet promotion and prices, terms and conditions of
chalet and also can use contact us to find the location of The Sea Blue Chalet 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 The Sea Blue Chalet Online Booking System may
login into member login of system to booking and after the comfirmation 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 are handle by owner/ admin to do
the viewing number of members that book the chalet, add and edit chalet type, view
booking, editing profile, view feedback and reply it. To promo the Sea Blue Chalet
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 rooms
and also can edit the types of room. Then, the admin could able to view all the details
of chalet booking under dashboard and payments details of members
.
2.3 User Characteristics
This The Sea Blue Chalet 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 experiencing the time save by do booking in this system.
8
2.4 Constraints
These are the few constraints of The Sea Blue Chalet Online Boking System holds for proper
functionalities.
a. The Promotion Update can only be created as template and then need to attach to the
template. This can view by customer, but only can edit or delete by admin.
b. The System is designed in one screen where user can only execute one task at a time.
c. The system must connect to local area network of the organization before operating.
d. The GPS installed for customers via the system for location purposes.
2.5 Assumption and Dependencies
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 Sea Blue Chalet 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.6 Apportioning of Requirements
For The Sea Blue Chalet 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 the Sea Blue Chalet Online Booking System
10
Figure 4: State Machine Diagram of the Sea Blue Chalet Online Booking System
3.1 External Interface Requirements
3.1.1 User Interfaces
The system is a standalone system that does not use external system. But the system will
require database management software like MySQL to manage the process of storing the
system data, and web server software that organizes the distribution of users in the local
network.
11
1. User Module
Figure 4 Home Page
This is main “home page” for user. In this user can view our chalet look in front page. User
can view promotion and discount on side of page.
12
Figure 5: About Us
This is “about us” page for user view, in this user can read about chalet’s history that talks
about the location and views that located.
13
Figure 6: Rates / Pricing
This is “rate / pricing” page, in this user can view room type and room price for member and
non-member. User also can view look of room for each type of room.
14
Figure 7: Promotion
This is “promotion” page, in this user can view promotion which admin update time to time
especially on festival season.
15
Figure 8: Our Facilities & Activities
This is “Our Facilities & Activities” page, in this user can view our facilities and activities
which have in our chalet.
16
Figure 9: Contact Us
This is “Contact Us” page, in this user can view address and contact number of our chalet,
user also can email us for inquiry. User can view direction of our chalet and view in larger
map.
17
Figure 10: Terms and Conditions
This is “Terms and Conditions” page, in this user can our term and condition. User also can
view our chalet definition which contain about check in, check out, booking, cancellation and
booking confirmation member details.
18
Figure 11: Privacy Statement
This is “Privacy Statement” page, in this user can our privacy statement.
19
Figure 12: Feedback
This is “Feedback” page, in this user can feedback to us. User just need first name, last
name, email id, contact number and comment which inquiry or complain about website.
20
Figure 13: Check Availability
This is “Check Availability” page, in this user click check in and checks out date picture then
click check availability button for check the availability room in our chalet.
21
Figure 14: Availability Room
This is “Availability Room” page, in this user can view that there is room available for
booking, if non-member click booking button, it goes to member login page, only member can
do booking.
22
Figure 15: Sign Up
This is “Sign Up” page, in this user or non- member can do signup for become member and
enjoy more discounts. This form must fill up all by correctly to avoid error. User must check
tick for agree to do register.
23
Figure 16: Member Login
This is “Member Login” page, after sign up by user or non-member, they need input
username and password to login.
24
2. Member Module
Figure 17: Forgot Password
This is “Forgot Password” page, if in case member forgot they username or password, they
need click forgot password link at member login page and enter first name and ic number
and click send. In few minutes the username and password will send to member email
address.
25
Figure 18: New Booking
This is “New Booking” page, in this member can do booking by click check in and check out
date, select chalet type, no of chalet that u want and no of people to stay in chalet. Then click
booking to go further process.
26
Figure 19: Confirm Booking
This is “Confirm booking” page, in member can view the picture of type chalet that member
choose in booking page, then view booking number, check in & check out date, type of chalet,
no of chalet, no of night and total amount that want to pay. Member should remember the
booking number or print this page by click print button to avoid forgot member booking
number when member check in on that time. After click ok button it go to payment page.
27
Figure 20: Print
This is “Print” page, this is print page for member to print for the booking number.
28
Figure 21: Payment Confirm
This is “Payment Confirm” page, in this member can click payment option, we giving two
options which is pay by cash or bank transfer. After click check out button it goes to manage
booking.
29
Figure 22: Bank Transfer
This is “bank transfer” page, if member click detailed info on payment confirm page,
member can see this page for account number and which bank we provide to easy transfer
money.
30
Figure 23: Manage Booking
This is “Manage Booking” page, in this member can view how many member do booking and
view the payment status after admin update it. If member not do payment yet, member can
click payment to do payment.
31
Figure 24: Payment
This is “Payment” page, in this member can click here button to do payment. And view in
this payment details which key in by member for payment. After admin update the status,
member can see that status will change to the paid.
32
Figure 25: Payment Form
This is “Payment Form” page, in this member do payment by type booking number,
reference number, date transfer, method, and amount.
33
Figure 26: Member Update Profile
This is “Update Profile” page, in this member can view and update their details.
34
Figure 27:Change Username & password
This is “Change Username & password” page, in this member can view and update their
username and password.
35
3. Admin Desk Modules
Figure 28: Admin Registration
This is “Admin Registration” page, admin only know this address to register to other admin.
36
Figure 29: Admin Login
This is “Admin Login” page, after register for admin can login using username and
password.
37
Figure 30: Dashboard
This is “Dashboard” page, after login by admin, they can see this dashboard which contain
about member’s booking.
38
Figure 31: Admin Payment
This is “Admin Payment” page, admin can view who is do payment and change the status to
receive by click received button. After change the status, it automatic change at member
payment page.
39
Figure 32: Booking Manager
This is “Booking Manager” page, admin can view which member do booking, and as admin
can change payment status to paid or cancel the booking after check the member truly paid
or not.
40
Figure 33: Monthly Booking Report
This is “Monthly Booking Report” page, admin can select any of month and click go button,
it will show all member which booking on that month.
41
Figure 34: Monthly Payment Report
This is “Monthly Payment Report” page, admin can select any of month and click go button,
it will show all member which make payment on that month with total of money collection on
that month.
42
Figure 35: Today Booking
This is “Today Booking” page admin can view on the day booking.
43
Figure 36: Search Page
This is “Search” page, admin can search by using booking number and click search now
button. And it will show booking number, full name, ic, check in & check out date, and status
which for paid or not.
44
Figure 37: Room
This is “Room” page, admin can view and edit room type, price description image, quantity
by click edit button.
45
Figure 38: Edit Room
This is “Edit Room” page, admin can edit room after click edit button on room page.
46
Figure 39: Feedback
This is “Feedback” page, admin can view and reply to the feedback sender by click reply
link.
47
Figure 40: Admin Update Profile
This is “Admin Update Profile” page, in this admin can view and update their details.
48
3.1.2 Hardware Interfaces
This system requires basic computer that consists of CPU, monitor, keyboard and mouse or
laptop and smartphones for input and output. Printer is needed if required. Smartphones or
Laptop could use to do booking use this system. 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.1.3 Software Interfaces
This system will require software MySQL, PHP, Apache to program and create The Sea Blue
Chalet 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 and
8 also can supported by this system.
3.1.4 Communication Interfaces
The system communication interface is completely depend 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.
49
3.2 System Features
3.2.1 Admin Module
Figure 41: Admin Module
50
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 The Sea Blue Chalet Online Booking System case for system
registration diagrams.
Use case Name
Sign Up
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
51
Figure 42: System sequence diagram for sign up
52
Figure 43: Activity diagram for sign up
53
3.2.1.2 UC-002: Check Availability
Use case Name
Check Availability
Goal
To check whether a room available or not
Primary Actors
Customer
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Extensions
Action
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
10
System validates details
11
Update database
12
Display “Successful message”
2.1
No room available for entered details
and display “No Room Available”
Table 2: Use case description for UC-002
54
Figure 44: System sequence diagram for check availability
55
Figure 45: Activity diagram for Check Availability
56
3.2.1.3 UC-003: Payment
Use case Name
Payment
Goal
Make payment for booked rooms
Primary Actors
Customer
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Extensions
Action
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
8
System validates details
9
Update database
10
Display “Successful message”
3.1
Bank/Payment details are incorrect,
Display the message "Unsuccessful.
Table 3: Use case description for UC-003
57
Figure 46: System sequence diagram for payment
58
Figure 47: Activity diagram for payment
59
3.2.1.4 UC-004: Update profile
Use case Name
Update Profile
Goal
Manage user profile/information
Primary Actors
Customer
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Extensions
Action
1
Login into system
2
Enter new username
3
Enter new password
4
Click submit
5
System validates details
6
Update database
7
Display “Successful message”
4.1
Password doesn’t match, Username is
already existed.
Display the message "Unsuccessful”.
Table 4: Use case description for UC-004
60
Figure 48: System sequence diagram for Update profile
61
Figure 49: Activity diagram for Update profile
62
3.2.1.5: UC-005: Admin login
Use case Name
Admin Login
Goal
View admin profile
Primary Actors
Admin
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Extensions
Action
1
Login into system
2
Enter username
3
Enter password
4
Click submit
5
System validates details
6
Update database
7
Display “Successful message”
4.1
Incorrect username or password.
Display the message "Unsuccessful.
Table 5: Use case description for UC-005
63
Figure 50: System sequence diagram for admin login
64
Figure 51: Activity diagram for admin login
65
3.2.1.6: UC-006: booking manage
Use case Name
Booking Manage
Goal
View customer booking payment status
Primary Actors
Admin
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Action
1
Login into system
2
Click paid button if customer done
payment
3
System validates details
4
Update database
5
Display “Successful message”
Extensions
Table 6: Use case description for UC-006
66
Figure 52: System sequence diagram for booking manage
67
Figure 53: Activity diagram for booking manage
68
3.2.1.7: UC-007: payment
Use case Name
Payment
Goal
View customer booking payment via bank
Primary Actors
Admin
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Action
1
Login into system
2
Click received button if customer
done payment.
3
System validates details
4
Update database
5
Display “Successful message”
Table 7: Use case description for UC-007
69
Figure 54: System sequence diagram for payment
70
Figure 55: Activity diagram for payment
71
3.2.1.8: UC-007: Report
Use case Name
Report
Goal
View booking and payment report
Primary Actors
Admin
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
Action
1
Login into system
2
Choose month for view the details.
3
System validates details
4
Show the details.
Extensions
Table 8: Use case description for UC-008
72
Figure 56: System sequence diagram for Report
73
Figure 57: Activity diagram for Report
74
3.2.1.9: UC-007: Search
Use case Name
Search
Goal
Search booking info
Primary Actors
Admin
Secondary Actors
None
Precondition
Login to the system.
Post condition
Triggers
Main flow
Step
1
Action
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
Table 9: Use case description for UC-009
75
Figure 58: System sequence diagram for Search
Figure 59: Activity diagram for Search
76
3.2.1.10: UC-007: Add room
Use case Name
Add Room
Goal
Add a new room to the system
Primary Actors
Admin
Secondary Actors
None
Precondition
Log in to the system
Post condition
Triggers
Main flow
Step
Action
Login into system
1
2
Admin clicks “room”
Choose Room
2
System prompts the admin to fill out
room details
3
System validates new/update room
information
4
System creates a new/update room
5
Update database
6
Display “successful” message
Extensions
Room details are incorrect, Display
the message "Unsuccessful" and
3.1
display room management option.
Table 10: Use case description for UC-010
77
Figure 60: System sequence diagram for Add room
78
Figure 61: Activity diagram for Add room
79
3.2.1.11: UC-007: Add Promotion
Use case Name
Add Promotion
Goal
Add promotion to the system.
Primary Actors
Admin
Secondary Actors
None
Precondition
Log in to the system
Post condition
Triggers
Main flow
Step
Action
1
Login into system
2
Admin clicks “Promotion”
3
Click choose button
4
Select picture
5
Click Upload Button
6
Update database
If type invalid display “Invalid type”.
Extensions
4.1
Table 11: Use case description for UC-011
80
Figure 62: System sequence diagram for Add Promotion
Figure 63: Activity diagram for Add Promotion
81
3.2.1.12: UC-007: Feedback
Use case Name
Feedback
Goal
View/ reply Feedback
Primary Actors
Admin
Secondary Actors
None
Precondition
Log in to the system
Post condition
Triggers
Main flow
Step
Action
1
Login into system
2
Admin clicks “Feedback”
3
Click reply button
4
Open outlook for reply feedback
5
Send the reply
Extensions
Table 12: Use case description for UC-012
82
Figure 64: System sequence diagram for Add Promotion
83
Figure 65: Activity diagram for Add Promotion
84
3.3 Performance Requirements
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.
85
3.5.3 Security
The system should provide secured communication with the server. 100% of the exchange
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 asked 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.
86