SIT725 Software Engineering Project: Tourism Website Design 2018

This document presents a software engineering project focused on designing a web application for travel and tourism, specifically for international flight ticket booking. It includes key elements such as a home page with tour packages, a contact page, and a login page for customer details and booking management. The project outlines the product vision, backlog with use case and activity diagrams, domain analysis, and a product roadmap. It further details the UML profile for design, including content, navigation, and process classes, along with class, sequence, and navigation diagrams. The document also covers sprint planning and backlog, concluding with the successful creation of a website to book international flight tickets, also providing travel insurance and cab services. Desklib provides a platform to access this and other solved assignments.

Software Engineering

1 Introduction
In the application of the web can be using to the international booking flight tickets. It
contains the contact page, home page and login page. The login page in which contains
customer details and booking details. The home page contains the tour packages. In the
customer booking the flight tickets through the website (Chiou, Lin and Perng, 2011).The
travel insurance also provide for customer and cab service also.
2 Travel and Tourism Website
Home Page
1

Tour Package
Contact Page
2

Login Page
Various Package Details
3

Create New Account
Insurance
4

Cab Service
3 Planned Produce Backlog
3.1 Vision Statement of the Product
This web page refers to travel and tourism. The booking of the international flights is mainly
used for the web application. The product of the vision is the all passenger expectation to the
dedicated work on the web application. We have the world tour package. So, our service
depend upon the international flights.
5

3.2 Backlog of Product
3.2.1 Use case diagram
Use case for the process of Ticket booking
 Scenario of the Use case: Login
 Description of the Scenario
Client maintains the database. Both are login page to access to the web management.
But the database page only access by user. The customer create the account for
booking the ticket and the database maintain by the user. The customer login the page
using username and password. The customer create an account. They enter the first
name, last name, gender, and contact no, address, username and password for create
an account. The username and password created in particular customer. They are book
the flight ticket easily through username and password (Choi, Ok and Choi, 2015).
 Primary actor: Customer
6

o Pre-condition: The client will login to website for booking process.
 Post conditions:
o After website to the login the customer see the package details.
o Book the ticket for international tour package.
Name of Use case: User
 Scenario of the Use case: Proving customer support
 Description of the Scenario: The details of the customer are maintained in the
database. The customer can login the user page and customer page. First the customer
login the homepage and they enter their details. The data will be stored the backend
database. Every database store the user page. The customer book the flight tickets.
The data stored the user page and user allotted the seats.
 Primary actor: user
 Pre-condition: user must login to the webpage
 Post conditions:
o User logins to the webpage for booking.
o User views all the available packages (Gold, Premium, and Silver) and offered
offers.
o Verify the user information. Finally the user conform the booking.
3.2.2 Activity Diagram
The below diagram represents the activity diagram for the user.
The below diagram represents the Online payment diagram.
7

3.2.3 Domain Analysis
The below diagram represents the Domain analysis.
 Create an account for the customer to book the flight ticket.
 For a specific customer, the valid username and password is created.
 Login page of the customer consists of using username and password.
 All the data can stored in the user page.
 The customer book the tickets and the information stored the user page. The
information can be verified by the user and conform the booking.
8

Product Backlog
Epic -
Product
Theme Story Priority Estimation
Search Search
methods
Place Search
The customer search place by
keyword,
5 2
Category Search
The customer search the various
place. So it has the various categories
to search the place.
9 2
Advance
Search
Search By Price
The customer search the place
based on the price. It has an offer
and various package
6 3
Search By Location
The customer should be able search
the location by keyword.
9 2
Select the various place
The customer book the various
place and various date.
9 2
Change Quantity
The customer book the ticket
for our family members,
friends etc., They have to
change the tickets before
conformation and after
conformation.
Continue Booking
The customer can be change or
cancel the booking tickets.
5 5
Payment
Section
Pay with Credit or Debit Card
The customer payment of the
amount through via debit or
9 2
9

credit card.
User
Management
User Setup Setup Detail account
The payment details stored by
the user.
6 3
User information
The customer booking details
stored in database.
9 2
4 Part – 1 Product Roadmap
4.1 Market map
4.2 Market Event
The customer to access the web application using the booking details of the
international flight. The most of the customer can booking the tickets with the help of social
media. Thus, the product is marketed via, Facebook, YouTube and twitter. The insurance can
be applied for travelling and we give the cab service.
10

4.3 Architecture map
4.4 Future map
11