Final Project PDF

Project Report for Tour and travel reservation system
KULLIYYAH OF INFORMATION & COMMUNICATION TECHNOLOGY
SEMESTER 1, 2019/2020
CSC 1501 INTRODUCTION TO SOFTWARE ENGINEERING

SECTION 3
TOUR AND TRAVEL RESERVATION SYSTEM
GROUP NO 5
PREPARED BY:
NAME MATRIC NO. PARTICIPATION
Saif Al Faied 1828615 100%
Md Borhan Uddin 1822665 100%
Md Ferdous Ahmed Khan 1825869 100%
Muhammad Hisyam bin Malang 1822907 100%
LECTURER
DR. AZLIN BINTI NORDIN
DUE
27 DECEMBER 2019
Table of Contents
1 INTRODUCTION....................................................................................................................................... 3
1.1 DOCUMENT PURPOSE ............................................................................................................................ 3
1.2 PROJECT SCOPE .................................................................................................................................... 3
2 OVERALL DESCRIPTION ....................................................................................................................... 3
2.1 PROJECT PERSPECTIVE .......................................................................................................................... 3
2.2 PROJECT OVERVIEW ............................................................................................................................. 4
2.3 DESIGN AND IMPLEMENTATION CONSTRAINTS ....................................................................................... 5
2.4 ASSUMPTIONS AND DEPENDENCIES ....................................................................................................... 5
3 SOFTWARE PROCESS ............................................................................................................................. 6
3.1 SOFTWARE PROCESS MODEL................................................................................................................. 6
4 REQUIREMENTS ENGINEERING ......................................................................................................... 7
4.1 REQUIREMENTS ENGINEERING ACTIVITIES ............................................................................................. 7
4.2 SCOPE DEFINITION AND PROBLEM ANALYSIS ........................................................................................ 9
4.3 REQUIREMENTS ANALYSIS .................................................................................................................... 9
5 DESIGN PHASE ....................................................................................................................................... 26
5.1 DESIGN ACTIVITIES ............................................................................................................................. 26
6 IMPLEMENTATION PHASE ................................................................................................................. 33
6.1 IMPLEMENTATION ACTIVITIES ............................................................................................................. 33
7 TESTING PHASE .................................................................................................................................... 41
7.1 TESTING ACTIVITIES ........................................................................................................................... 41
8 REFERENCES AND ACKNOWLEDGMENTS ..................................................................................... 49
1 Introduction
Our project name is tour and travel reservation system. Tour and travel reservation system- is an
online reservation system that allows travelers to easily book and search for great tourism spots.
1.1 Document Purpose

The purpose of this document is to give the reader a ‘free from doubt’ description about the system
we have created.
Furthermore, this document contains the information regarding the software process model and the
reason behind choosing that model. Additionally, the requirement phases- where the requirement
engineering activates has been vastly described, design phase- containing the facts of designing
activates and the finally the implementation and testing phases where how the system has been
implemented and what testing cases are and how those test cases have been tested is being described
progressively.
1.2 Project Scope

The software is developed under the of Tour and Travel Reservation System. The system is developed
by the team of four people. The spiral process model is used to build this system and the main aim is
to build a reservation system that will ease the process of booking and satisfy the customer.
The benefit of the system is not only to ease the process but also reduce different kind of errors. At
the same time maintaining a strong security and integrity with a strong database system.
The goals that need to be met are creating a product that satisfies all the requirements generated in
the requirements engineering phase, achieving the deadline to create the software on time while using
the minimal amount of time, effort and resources to create a product that represents what every
stakeholder has envisioned.
2 Overall Description
2.1 Project Perspective

This project will focus on a new self-contained product as this software hasn’t been developed
before/any content of this software hasn’t been inherited. It was purely based on the requirements
we gathered, and we made sure that the software was engineered to meet our customers’ demands.
However, the idea of this project is generated through public interest.
This program can be accessed by pc and mobile phones, however we focused more on the pc part.
Hence, pc and good internet service is a one of the major requirements for the software to work.
Furthermore, to control the system another major component of this system would be the system
administrator. The system will constantly be updated through users review which will maintained
by the admin.
2.2 Project Overview
This website has five use cases & four actors. The use cases are the log in, the user must log in to
make booking, then use case is view package both the travellers and visitors will be able the view
the available packages. Next use case is update package; admin will be able to update or add
packages as well as login and view available packages. Next is use case book package, the travellers
will be able to book package and make payment using our system. Provided the payment is made
the admin panel can update the booking status.
2.3 Design and Implementation Constraints

The constraint can be this website should be improving so the user will be able to enter their
payment details.
• Time – not enough time is given to us by the client to develop the software
• Flexibility – Although it has been made flexible, all users may not have the right privilege to
use the application.
• Money – the budget provided may not be enough to meet the project requirements thus it
was hard to work with the limited amount of budget we were allocated for it
2.4 Assumptions and Dependencies
This project takes the following factors into assumption for the software to work
• All staffs have enough knowledge on how the system works.

• All the customer in this system must have device with internet capable of running the
software.
• All staffs don’t have the privilege to change the system without the permission of System
admin.
• Hotels/ restaurant / transportation companies provide packages for admin to update.
3 Software Process
3.1 Software Process Model

<Refer A1. Describe the selected process model here and describe. You should describe how you use the
model to guide you in this project.>
Here it has been described how we use the model to guide us in this project:
Customer communication: In this phase, the customer communication will occur.
Planning: In planning phase, firstly will gather necessary requirements from the stakeholders.
Risk analysis: In risk analysis, we will take necessary steps to identify the risks, and to come up
with a definite solution.
Engineering: In this phase, we will do the necessary things such as the class design, and the user
interface design.
Construction & release: In this phase, we will create a prototype of our system, and release it for
the customer evaluation.
Customer evaluation: In this phase, the customer will evaluate the prototype, and check whether it
meets all the necessary requirements.
3.1.1 Activities involved
Planning Phase:
In this phase, we have worked along side with the stakeholders to find the requirements and user
needs for the project. The requirements like business and system requirement specification. The
requirements were specified through use case and its specifications also taking ideas from other web
sites.
Risk-Analysis Phase:
This phase is to identify the risk involved with the tour and travel reservation system. This phase
was not applied during this circle.
Engineering Phase:
During this phase, we have created use case diagram, activity diagram, use case specification, class
design and user interface design for the prototype. After developing, we checked the system if it
meets all the conditions and requirements with the draft (Planning phase).
Evaluation Phase:
This phase is to check with customer weather if it meets the requirements, by getting their feedback.
Depending on their opinion, a new update or correction will be given. Since it was not possible, we
checked it with the planning phase requirements.
4 Requirements Engineering
4.1 Requirements Engineering activities

In this section, we have worked on the requirements engineering activities which are nothing other
than making the use case diagram, activity diagram, and use case specifications
4.1.1 Inception
In this phase we have identified the stakeholders and created project goals that helped us to create
the project. The key points of this phase,
i. The travelers who are interested to visit Malaysia, are the main stakeholders of the system.
The other stakeholders are the visitors (Main customer), admin panel (who will maintain
the system), transportation companies, Hotel companies, restaurant companies, Bank,
Project team members. The main stakeholders will pass the all the booking info to the
system administrator.
ii. The system administration will manage the package details, additional facilities details,
booking status.
iii. The visitors will visit the system without login and able to see all the packages and other
information about tours packages.
iv. Bank will receive all types of payments.
v. Project team members will develop the tour and travel reservation system
4.1.2 Elicitation
We have used different elicitation techniques to get the better information. The different system and
techniques are described later in the report.
4.1.3 Elaboration
1. CONTEXT DIAGRAM
Figure-2
Figure 2 is a context diagram of Book package use case. In Figure 2, User, admin, company
representative and bank represent Entity. Invoice, user, packages, booking represents database.
4.2 Scope Definition and Problem Analysis
Booking a tour package manually is very difficult as,
1. Time is one of the main scopes of our project, as it saves time of the user. When customers book any
packages manually, they need to find out everything by themselves. But with the system they get all
the packages in just one click.
2. One of the other things of manual booking is the customer needs to be physically present. As in most
cases there remains a chance of fraud. So, physical presence is a must in the present systems. But in
our system the customers physical presence is not required, at the same time our service is guaranteed.
3. The current systems are poor in providing information and advices to the agencies and customers about
tour plan. In our case, customer doesn’t need any agencies as each & every information is given in the
website. It is also creating a secure platform for the users.
4.3 Requirements Analysis
4.3.1 Requirements Elicitation Strategy
1. We have gathered requirements from the stakeholders by using different technique e.g. survey and
interviews. On the first iteration of prototyping we have taken requirements from the stakeholders for
the first use case of our system and after working on the use case we went for the next one on the next
iteration. This process continued until we finished working on all the use cases.
2. Interview:
The interview was targeted towards the existing system admins (Date:27/10/19).
i. Should system send invoice?

a. Yes
ii. Should system record customer details?
a. Yes
iii. Should system record payment and payment type?
a. Yes
iv. Should system have tour plan customization option?
a. Yes
v. what would be the type of your payment?
a. both cash & credit
vi. What sort of trip plan should be included?
a. business trip, family trip, honeymoon and others
vii. How to become trustworthy online system?
a. Truthfulness in every situation, Keeping a transparent transaction and Customer

care and satisfaction.
Survey(offline):
This part of survey was done manually, the main stake holders were project team members and
admin panels.
i. Can visitor book packages without logging in??
a. Yes (10%)
b. No (90%)
ii. Should system keep ‘Booking status’ function?
a. yes (70%)
b. no (30%)
iii. Shall system record customer feedback?
a. Yes (95%)
b. No (5%)
iv. Should system have a confirmation ‘email/call’ function of user reservation?
a. Yes (95%)
b. No (5%)
v. The load time of user interface screen should be?
a. 1 sec (80%)
b. 2 sec (25%)
c. 3 sec (5%)
vi. The system should be available during?
a. 24 hours (80%)
b. Normal operating hours (20%)
Survey(online):
This is the online survey; the main stake holders were customers, different companies and visitors.
1.
2.
1.
2.
3.
4.
5.
4.3.2 Functional Requirements

The traveler, who will visit our website then we call to them the ‘user’, will be presented with 2
choices by our tour and travel reservation system, as the first step in the interaction between them. A
user can see and check all the availability of packages on our website without any registration or login
to our website. Also, a user can directly register themselves by giving their personal information such
email, password, address and so on, after registration, a user can able to access all the features given
on our website.
A user who has booked a package by our system earlier or registered would have been given a user
id and a password. He would have his personal information stored in the database referred to earlier
in choice 2 above. This ‘personal information’ would be henceforth referred to as ‘profile’. Such a
user with a profile in database. And this user will be called a ‘registered user’. A registered user will
be able to book available packages either one or more by completing payment section.
A new user, on the other hand, either would register himself with the system by providing personal
information (case1) or visit the website as a guest or general user (case2). In first case, the new user
becomes a registered user. In the second case, the new user would remain a guest or general user. A
general user can only check the availability of packages and cannot book a package. But a registered
user can also act as a user if he only wants to check the availability of packages.
‘Availability of packages’ always refers to viewing the package destination of travel, prices and some
other information and any discount offers. The system shall present the user with an option to register
once user navigate to booking option on the package below.
4.3.3 Use Case Specification for Login.
login
Use Case ID: LogIn.1.0
Use Case Name: Version No: 1.0

LogIn
Objective: Login to the system to booking purpose.
Created by: Borhan On (date): 16/12/2019
Last Update by: Saif On (date): 16/12/2019
Approved by: Ferdous On (date): 16/12/2019
User/Actor:
Customer,
Business Owner Contact <Tel no/email>
Name: Details:
Trigger:
User wants to login into the system
Frequency of Use:
Once user wanted to book packages
Preconditions
The user must have a register account

User should enter a valid username and password
Basic Flow
Step User Actions System Actions
1
The use case starts when the user The system will ask to user the username and password.
chooses the option ‘Login’. (A1)
2
User Enter username and password The system will show the login completed.
(E1)
Alternate Flow A1: Unauthorized attempt

1 User doesn’t have login access The system brings user to registration page
Exception Flow: E1: Invalid username and password

1 The system displays “wrong username or password”,
2
Use case Ends.
Post conditions
• The user should able to access book package and make payment
Special Requirements
• The system should be in user friendly condition.
Business Rules
• The Trip and travel plans must be made within the best seasonal conditions.
• Every trip plan should have suitable picture and theme (context) to attract users.
Other Notes (Assumptions, Issues,)
• Assumptions:
1. The user has a valid user id and password to complete the booking.
• Issues:
1. Website must be in optimal condition
4.3.4 Use Case Specification for View Package

View Package
Use Case ID: View package 1.0

View Package
Objective: View the package on Dream Travel website.
Created by: Hisyam On (date): 16/12/2019
User/Actor:
Customer, travelers, admin
Name: Details:
Trigger:
User wants to view the package.
Frequency of Use:
Regular
Preconditions
The user must have a register account
Basic Flow
1
The use case starts when the user The system will display the package.
chooses the option package.
2
User chooses a package. (A1) The system will go to booking system.
Alternate Flow A1: Unavailable package

1 The system displays the unavailable package by
showing indication that the package currently
unavailable.
Post conditions
• The user should able to access book package and make payment
• The system should be in user friendly condition.
Business Rules
• Assumptions:
2. The user has a valid user id and password to complete the booking.
• Issues:
4.3.5 Use Case Specification for Book Package
Book Package
Use Case ID: Booking 1.01

Package Booking
Objective: Booking Packages From online system.
Created by: Saif On (date): 27/10/19
Last Update by: Borhan On (date): 02/11/19
Approved by: Azlin binti nordin On (date):
User/Actor: Travelers, visitor, admin.
Business Owner Ferdous Contact 01145252533
Name: Details:
Trigger:
User wants to book a tour package
Frequency of Use:
Regularly.
Preconditions
1. The user must have a valid website and Bank account.
Basic Flow
1
The use case starts when the user The system will display the tour packages.
chooses the option ‘Package plan’.
2
User chooses a package. (E1) The system will display the full plan of the chosen
package including price.
3
User chooses ‘Booking’ option. The system displays booking options.
4.
The system prompts the user to input the number of
travelers.
5.
The user inputs the number of travelers. The system prompts the user to input travel period
6.
The user chooses a travel and return The system displays additional services.
date. (E2)
7.
The user chooses additional services. The system displays chosen service.
(A1)
8.
The system calculates total Price.
9.
The system displays total price
10.
The system displays payment methods
11.
The user chooses a payment option. The system prompts the user to Login.
(A2)
12.
The user enters username and The system verifies name and password. (A3)
password.
13.
The system displays payment options.
14.
The user chooses a payment method. The system brings user to banking system use case.
15.
User completes the transaction.
16.
The system update database.
17.
System displays booking confirmation.
18.
The System sends email to the user about booking
confirmation.
19.
The use case ends.
Alternate Flow A1: Choice of Service

1 User ignores service The use case returns to step 8.
Alternate Flow A2: Payment Cancellation

1 User cancels the payment process The use case returns to step 9.
Alternate Flow A3: Invalid name and password

1 The system displays “Invalid Name or, Password.
Please try again”.
2
The use case returns to step 12.
Exception Flow: E1: Unavailable Plan

1 The system displays “This plan is not currently
available”.
2
Use case Ends.
Exception Flow: E2: Unavailable schedule.

1 The system displays “The Traveling Date is not
Suitable ”.
2
Use case ends
Post conditions
• The user gets trip information through mail.
• The system should be robust enough to provide good service to the customers
• The system should be user friendly.
Business Rules
• Every trip plan interface should have suitable picture and theme (context) to attract users.
• Booking before three months will get an early bird discount.
Other Notes (Assumptions, Issues)

• Assumptions:
3. The user has a valid user id and password.
• Issues:
4.3.6 Use Case Specification for Make Payment
Make Payment
Use Case ID: Make Payment.1.0.3

Make Payment
Objective: Make payment to book the packages
Created by: Borhan On (date): 16/12/2019
User/Actor:
Travellers
Name: Details:
Trigger:
User will make payment to complete the booking
Frequency of Use:
often
Preconditions
User should be a register customer.

Admin must have a valid online bank account.
Basic Flow
1
The use case starts when users choose The system will indirect users to payment page
to payment option.
2
The system will display total summary of amount
Basic Flow
3
The user can input vouchers code The system will justify voucher
4
The system will re-calculate the total summary of amount
and display.
5
The user chooses a payment option
(online/credit or debit)
6
The users complete the transaction The system will show the message “payment received”
(A1) (E1)
7
Use case ends
Alternate Flow A1: Cancellation

1 Users deny to make payment The use case flow returns to booking use case
Exception Flow: E2: insufficient balance

1 The system displays “Error, insufficient balance for this
package”.
2
Use case ends
Post conditions
• The users should make the payment successfully
• Receive the payment confirmation.
1. The system should be robust enough to provide good service to the customers
Business Rules

• Assumptions:
The users should have internet to access payment.
• Issues:
Website must be in optimal condition
4.3.7 Use Case Specification for Update Booking Status
Update booking status
Use Case ID: Status 1.01

Status Update
Objective: Updating status after booking confirmation
Created by: Saif On (date): 14/12/19
Last Update by: Ferdous On (date): 15/12/19
Approved by: Borhan On (date): 15/12/19
User/Actor: Admin
Business Owner Contact
Name: Details:
Trigger:
User books a package and completes payment
Frequency of Use:
Regularly
Preconditions
2. The user must book a package.
Basic Flow
1
The use case starts when the user System will receive a confirmation of the booking. (E1)
completes payments.
Basic Flow
2
Admin will update booking status.
System will send an email to the user containing all

necessary information about the packages.
3
The use case ends.
Exception Flow: E1: Fails to receive confirmation

1 System does not receive payment confirmation or,
payment confirmation was wrong.
2
Use case ends.
Post conditions
None
Business Rules
• none
Other Notes (Assumptions, Issues)
• Assumptions: User has a valid bank account.
• Issues:
none
4.3.8 Use Case Specification for Update Package
Update Package
Use Case ID: Update Package.1.0.2

Update Package
Objective: Login to the system to booking purpose.

Created by: Ferdous On (date): 16/12/2019
Approved by: Borhan On (date): 16/12/2019
User/Actor:
Admin panel,
Name: Details:
Trigger:
Admin panel will update/add the packages
Frequency of Use:
Preconditions
The proposed package should be approved by admin panel

Admin must have access to update packages
Basic Flow
1
The use case starts when the authorized The system will display the packages list.
admin chooses the option ‘Update/Add
Package’. (A1)
2
Admin will choose update option (A2)
3
The admin enter the package
information and add the related image.
E.g. Package name, Destination and so
on (A1)
3
Admin chooses the Add/update button The use case ends.
(A1)
Alternate Flow A1: Cancellation

1 Admin ignores to update packages The use case returns to step 1.
Alternate Flow A2: Add Package

1 Admin chooses to add package System will redirect to add/update page.
Alternate Flow A2: Add Package

2 Input all required values and click
on Add package
3 System will add a package to the package list.
Exception Flow: E2: Ticket Problems

1 Admin enter the existing package name. The system displays “Error, This Package is already
exist”.
2
Use case ends
Post conditions
• The Admin should able to update new packages.
• The system should be robust enough to provide good service to the customers
Business Rules
• Assumptions:
1. The admin has authority to update packages.
• Issues:
4.3.9 Activity Diagram
Figure-3 Figure-4
Figure 4 is the countiounition of Figure 3. This usecase diagram represents Book Package use case.
Here, the diagram dipects the flow of the use case specification.
5 Design Phase
5.1 Design activities
5.1.1 Data/Class Design
Figure-5
Figure-5 shows the class diagram, where packages, registered_user, payments are classes. ID,
fname, lname etc. are attributes. Login(), booking() etc. are considered as behavior.
5.1.2 User Interface Design

We have used mock-ups user interface design. For the mock-up we used just in mind application.
Benefit:
1) Easy to use Software.
2) Multiple projects can run at the same time
Limitation:
1) After the free trial workspace becomes limited.
2) Software is quite heavy so not computers can run it with ease.
5.1.2.1 Home Page
Figure -1
Figure-1, is a mock-up for the Home Package use case.

5.1.2.2 Package Page
Figure -2
Figure-2, is a mock-up for the View package use case.

5.1.2.3 Booking Page
Figure -3
Figure-3, is a mock-up for the Book package use case.

5.1.2.4 Payment Page
Figure -4
Figure-4, is a mock-up for the make payment use case.

5.1.2.5 Update package
Figure -5
Figure-5, is a mock-up for the update package use case.

5.1.2.6 Update package
Figure -6
Figure-6, is a mock-up for the Login use case.
6 Implementation Phase
6.1 Implementation activities

In this phase, we completed the prototype. Instead of coding we used a prototyping software called
Wix. This site makes thing easy for beginners as it is created on the concept of drag and build.
Link to our website: https://ferdoustafe.wixsite.com/moonlighttravel
6.1.1 Home Page- Snapshot-1
6.1.1.1 Home Page- Snapshot-2

The snapshot 1-4, indicates the home page of our website.

Here the user can navigate among other pages, also have look at our website motto.
6.1.2 Package Page - Snapshot-1
This snapshot displays the package page, where the customer can view all the packages that is
available.
6.1.3 Booking page- Snapshot-1
This snapshot depicts the booking page. The user is redirected from the package by clicking the
booking button. Here the travellers can book the package.
6.1.4 Payment- Snapshot-1
This is the payment page, here the travellers can pay for the packages.
6.1.5 Update package - Snapshot-1
This is the update/add package page, here the admin can add/update the packages.
6.1.6 Package Page - Snapshot-1
The snapshot indicates the login page, here the user & admin can Login into the website.
7 Testing Phase
7.1 Testing activities
Project Name: Tour and Travel Reservation System

Test Case (01)
Test Case ID: TTRS_01 Login Test Designed by: Borhan
Test Priority (Low/Medium/High): High Test Designed date: 12/27/2019
Module Name: Login Test Executed by: Saif

Test Title: Verify login with valid username and
password Test Execution date: 12/27/2019
Description: Test the login page
Pre-conditions: User has a valid username and password.
Dependencies: None
Status
Expected
Step Test Steps Test Data Actual Result (Pass/ Notes
Result
Fail)
Navigate to login www.tourtravelreserva Login page is User is navigated to
1 page tion system Pass
displayed. login page
Username=
Provide valid
2 smborhan321@gmail. - - -
username com
3 Provide valid Password: - - -
password ed19201010
Click on Login Login button is User should be Display dashboard Pass
4 button clicked able to login with successful login
Post conditions:
User is validated with database and successfully login to account. The account session details are
logged in database.
Project Name: Tour And Travel Reservations System(TTR)
Test Case (02)

Test Case ID: TTRS_02 View package Test Designed by: Borhan
Test Priority (Low/Medium/High): High Test Designed date: 12/272019
Module Name: View package Test Executed by: Saif
Test Title: View the packages without booking. Test Execution date: 12/27/2019
Description: View all the available packages without being
an unregistered user.
Pre-conditions: User has an internet connection.
Dependencies: None
Status
Expected
Result
Fail)
Navigate to view Package button is Available User capable to see

1 package pages clicked Packages are available packages Pass
displayed
Post conditions:
User should able to view all the available packages.
Test Case (03)
Test Case ID: TTRS_03 Book Package Test Designed by: Borhan
Module Name: book package Test Executed by: Saif
Test Title: navigate to button book page for booking a
package Test Execution date: 12/27/2019
Description: click on book page from selected packages
Pre-conditions: User has a valid login access.

Dependencies: None
Status
Expected
Result
Fail)
Navigate to button Book package is Booking details Selected package is
1 called ‘book clicked are displayed sold out. fail
package’
User navigate to Booking details User able see booking pass
2 -
available packages are displayed summary.
Post conditions:
User should able to book a package
Test Case (04)

Test Case ID: TTRS_ Update packages Test Designed by: Borhan
Module Name: Update packages Test Executed by: Saif
Test Title: update the new packages and edit the existing
packages Test Execution date: 12/27/2019
Description: add or update the new packages.
Pre-conditions: An admin should have access to update the packages.
Dependencies: None
Status
Expected
Result
Fail)
Navigate to update Update button is Update Admin can access to

1 page clicked package form update package form Pass
is displayed
Package is
Check if the similar
Provide valid ready to A new package pass
2 name of packages are
package name display in updated
exist. interface
Post conditions:
Admin able to add or update a new package.
Test Case (05)
Test Case ID: TTRS_5_Payment Test Designed by: Borhan

Module Name: Payment Test Executed by: Saif
Test Title: Do payment for booking package Test Execution date: 12/27/2019
Description: verify the payment for booking confirmation.
Pre-conditions: User should have a valid online account

Dependencies: None
Status
Expected
Result
Fail)
User navigate to
Navigate to Payment button is Payment
1 online payment
payment button clicked summary is Pass
option
displayed
Payment is
Provide valid bank Bank data is Payment received by
2 successfully pass
requirements validated authority
done
Post conditions:
User must able to done payment for booking confirmation.
Test Case (06)
Test Case ID: TTRS_6 Update booking status Test Designed by: Borhan
Module Name: update booking status Test Executed by: Saif
Test Title: Confirm and update the booking by authority Test Execution date: 12/27/2019
Description: make invoice and confirm it by sending to
users.
Pre-conditions: User should do the payment successfully

Dependencies: None
Status
Expected
Result
Fail)
Admin click on Payment list is
1 Payment status
payment database checked Booking is confirmed Pass
is updated
User should User found an email
Click on auto Check the booking find a
2 with booking pass
invoice creator. ID confirmation confirmation.
email
Post conditions:
User should find an invoice through email.
Project Name: Tour and Travel Reservations System (TTR)

Test Case Template (07)
Test Case ID: TTR_01 DATE Test Designed by: Saif

Module Name: travel Period. Test Executed by: Borhan
Test Title: Verify Travel and Return Date Test Execution date: 21/11/2019
Description: Test the traveling date
Pre-conditions: User needs to fill the all the required information on the existing page.
Dependencies: None
Status
Step Test Steps Test Data Expected Result Actual Result (Pass/Fai Notes
l)
Travel Date = 20/11/19
1 Provide Travel Date - - -
2 Provide Return Date Return date = 23/11/19 - - -

User should be able to Display dashboard with Total
3 Click on Next button Next button is clicked Pass
procced to next page price & Payment option.
Post conditions:
Chosen date is validated with database.
Project Name: TOUR AND TRAVEL RESERVATION SYSTEM (TTP)
Test Case ID: TTP_02 payment validation Test Designed by: Borhan
Module Name: Payment Test Executed by: Saif al Faied
Test Title: Ensure the payment via online bank account Test Execution date: 11/22/2019
Description: Paying through valid online bank account by in directing
with valid username and password
Pre-conditions: User has a valid online bank account.
Dependencies: None
Status
Step Test Steps Test Data Expected Result Actual Result (Pass/Fa Notes
il)
Payment button has been Various bank name

1 Click on the payment button Travelers choose the preferred
clicked are shown (partner) Pass
bank option
Provide valid account Username:
2 - - -
username Borhan111213
Password:
3 Provide valid password - - -
Ed19201010
Travelers should be
Bank will pop up that a certain
Click on the confirm button System received data from able to complete
4 amount has been deducted Pass
(after seeing actual amount) bank payment based on
from your account.
sufficient balance
Post conditions:
Travelers should receive a receipt of payment.
Test Case ID: TTR_03_cost_calculation Test Designed by: Borhan

Module Name: Total cost calculation Test Executed by: Ferdouss
Test Title: Check the total cost Test Execution date: 20/11/2019
Description: Test price calculation
Pre-conditions: User has to choose a package and needs to fill up necessary information.
Dependencies: None
Status
Step Test Steps Test Data Expected Result Actual Result (Pass/Fa Notes
il)
1 Click on additional activity Types of service Different types of User is navigated to types of
Pass
service are displayed. service
2 Provide an accommodation Five Star - - -
3 Provide room type King size bed - - -
User should be able
4 Click on the pay button Pay button is clicked to see payment Display booking summary Pass
method
Post conditions:
User able to make payment.

Test Case ID: TTR_04_webpage Test Designed by: Hisyam

Test Priority (Low/Medium/High): Medium Test Designed date: 20/11/2019
Module Name: web page Test Executed by: Ferdous
Test Title: How to browse into our webpage Test Execution date: 20/11/2019
Description: Test webpage
Pre-conditions: None
Dependencies: None
Status
Step Test Steps Test Data Expected Result Actual Result (Pass/Fai Notes
l)
https://ferdoustafe.wixsi
1 Insert our webpage URL User is navigated to
te.com/moonlighttravel travel home page Pass
home page
User is Navigated to travel
2 Click on selecting package te.com/moonlighttravel/ Package Page display Pass
package page
dream-travel
3 Click on About us te.com/moonlighttravel/ About us page display User will see website details Pass
book-online
4 Close webpage - - - -
Post conditions:
User able to access Dream Travel webpage
8 References and Acknowledgments

• http://tryqa.com/what-is-spiral-model-advantages-disadvantages-and-when-to-use-it/
• https://www.quora.com/What-is-tour-and-travel-management
• Roger S.pressman, 7th edition, Software engineering a practitioners approach.
• http://bokardo.com/principles-of-user-interface-design/
• http://softwaretestingfundamentals.com/test-case/
• https://www.toptal.com/designers/prototyping/guide-to-prototype-design
• https://project-management-knowledge.com/definitions/r/reporting-systems/

Final Project PDF

Uploaded by

Copyright:

Available Formats

Final Project PDF

Uploaded by

Document Information

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

Final Project PDF

Uploaded by

Copyright:

Available Formats

Project Report for Tour and travel reservation system

KULLIYYAH OF INFORMATION & COMMUNICATION TECHNOLOGY

CSC 1501 INTRODUCTION TO SOFTWARE ENGINEERING

TOUR AND TRAVEL RESERVATION SYSTEM

NAME MATRIC NO. PARTICIPATION

Saif Al Faied 1828615 100%

Md Borhan Uddin 1822665 100%

Md Ferdous Ahmed Khan 1825869 100%

Muhammad Hisyam bin Malang 1822907 100%

1.1 Document Purpose

1.2 Project Scope

2.1 Project Perspective

2.2 Project Overview

2.3 Design and Implementation Constraints

2.4 Assumptions and Dependencies

• All staffs have enough knowledge on how the system works.

3.1 Software Process Model

3.1.1 Activities involved

4.1 Requirements Engineering activities

4.2 Scope Definition and Problem Analysis

Booking a tour package manually is very difficult as,

4.3 Requirements Analysis

4.3.1 Requirements Elicitation Strategy

i. Should system send invoice?

a. Truthfulness in every situation, Keeping a transparent transaction and Customer

4.3.2 Functional Requirements

4.3.3 Use Case Specification for Login.

Use Case ID: LogIn.1.0

Use Case Name: Version No: 1.0

The user must have a register account

Alternate Flow A1: Unauthorized attempt

Step User Actions System Actions

Exception Flow: E1: Invalid username and password

• The system should be in user friendly condition.

Other Notes (Assumptions, Issues,)

4.3.4 Use Case Specification for View Package

Use Case ID: View package 1.0

Use Case Name: Version No: 1.0

The user must have a register account

Alternate Flow A1: Unavailable package

Step User Actions System Actions

• The system should be in user friendly condition.

Other Notes (Assumptions, Issues,)

4.3.5 Use Case Specification for Book Package

Use Case ID: Booking 1.01

1. The user must have a valid website and Bank account.

Alternate Flow A1: Choice of Service

Alternate Flow A2: Payment Cancellation

Alternate Flow A3: Invalid name and password

Exception Flow: E1: Unavailable Plan

Exception Flow: E2: Unavailable schedule.

Other Notes (Assumptions, Issues)

4.3.6 Use Case Specification for Make Payment

Use Case ID: Make Payment.1.0.3

Use Case Name: Version No: 1.0

User should be a register customer.

Alternate Flow A1: Cancellation

Step User Actions System Actions

Exception Flow: E2: insufficient balance