Travels and Tourism Management System: Government College University Faisalabad

Government college university Faisalabad
TRAVELS AND TOURISM MANAGEMENT

SYSTEM
By
Momna Safdar 2018-GCUF-062772

Ayesha Abdul Ghafar 2018-GCUF-062775
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE
DEPARTMENT OF COMPUTER SCIENCE
Government College University Faisalabad
i|Page
Table of Contents
Revision History ................................................................................................................................. vi

Chapter 1....................................................................................................................................... 1
1. Introduction ................................................................................................................................ 1
1.1 General Information .................................................................................................................. 1
1.2 Purpose .................................................................................................................................... 1
1.3 Document Conventions ............................................................................................................ 2
1.4 Project Objective ...................................................................................................................... 2
GiveAccurateInformation. ........................................................................................................... 2
1.5 Intended Audience and Reading Suggestions .......................................................................... 3
1.6 Project Scope ........................................................................................................................... 3
Chapter 2....................................................................................................................................... 3
Overall Description ......................................................................................................................... 3
2.1 Product Perspective ................................................................................................................. 3
2.2 Product Features ...................................................................................................................... 3
2.2.2 Data Flow Diagram(DFD) ...................................................................................................... 3
2.3 User Classes and Characteristics ............................................................................................. 5
2.3.1. Admin Authentication ........................................................................................................ 5
2.3.2. User Registration .............................................................................................................. 6
2.3.3 Package Creation .............................................................................................................. 7
2.3.4 Package Booking ............................................................................................................... 7
2.3.5 Booking Confirmation/Manage ........................................................................................... 8
2.3.7. Issue Ticket ....................................................................................................................... 9
2.5 Design and Implementation Constraints ................................................................................... 9
2.6 User Documentation ................................................................................................................. 9
2.7 Analysis Model ....................................................................................................................... 10
2.2.1 SDLC methodologies ....................................................................................................... 10
2.8 Need for Computerization ....................................................................................................... 12
Chapter 3..................................................................................................................................... 12
3.1 System Features .....................................................................................................................12
3.1.1 User data ............................................................................................................................. 12
ii | P a g e
3.2 Feasibility Report .................................................................................................................... 13
3.3 Technical Feasibility ............................................................................................................... 13
3.4 Operational Feasibility ............................................................................................................ 14
3.5 Economical Feasibility ............................................................................................................ 15
Chapter 4..................................................................................................................................... 15
External Interface Requirements .................................................................................................. 15
4.1 User Interface Requirements...................................................................................................15
4.3 Software Interfaces................................................................................................................. 15
4.4 Communications Interfaces .................................................................................................... 16
Chapter 5..................................................................................................................................... 16
Other Nonfunctional Requirements ...............................................................................................16
5.1 Safety Requirements……………………………………………………………………………..……16
5.2 Security Requirement………………………………………………………………………………….16
5.3 Software Quality Attributes ..................................................................................................... 16
5.4 Performance Requirements .................................................................................................... 16
5.5 Strategic Approach to Software Testing .................................................................................. 17
5.6 Unit Testing ............................................................................................................................ 17
5.7 Conditional Testing ................................................................................................................. 18
5.8 Data Flow Testing................................................................................................................... 18
5.9 Loop Testing........................................................................................................................... 18
Chapter 6..................................................................................................................................... 19
WBS Project Management ............................................................................................................19
Chapter 7……………………………………………………………………………………………………20
Analysis Model…………………………………….….…………………………………………………... 20
7.1 Use Case Diagram ..................................................................................................................20
7.2 Class Diagram ........................................................................................................................21
7.3 Object Diagram .......................................................................................................................22
7.4 Sequence Diagram…………………………………………………………………………………….23
7.5 Activity Diagram………………..………………………………………………………………………24
7.6 Collaboration Diagram ............................................................................................................25
7.7 State Transition Diagram ........................................................................................................26
7.8 ERD ...................................................................................................................................... 26
Chapter 8…………………………………………………………………………………........................28
Tools & Technologies……………………………………………………………………………….....….28
8.1 Programming Languages…………………………………………………………………………….28
iii | P a g e
HTML ........................................................................................................................................ 28
CSS (Cascading Style Sheets) ................................................................................................. 28
JavaScript ................................................................................................................................. 29
8.2 Databases/Data storages…………………………………………………………………………….30
• MySQL ....................................................................................................................................... 30
• Database.................................................................................................................................... 30
8.3 Operating System……………………………..……………………………………………………….30
Appendix A: Glossary…………………...………………….………………………………………………30
References ................................................................................................................................... 31
Appendix B: Check List ..................................................................................................................32
Appendix C: Supervisory Committee..............................................................................................33
iv | P a g e
LIST OF FIGURES
Figure 1 DFD ..................................................................................................................................... 4
Figure 2 Admin Authentication ........................................................................................................... 5
Figure 3 User Registration ................................................................................................................. 6
Figure 4 Package Creation ................................................................................................................ 7
Figure 5 Package Booking ................................................................................................................. 7
Figure 6 Give Feedback ..................................................................................................................... 8
Figure 7 User documentation ........................................................................................................ …10
Figure 8 WBS………………………….….…...….…...………………………………………………...……19
Figure 9 Use Case Diagram…………………......………………...……………………………………......20
Figure 10 Class Diagram………………......………………...……………………………………..............21
Figure 11 Object Diagram…………………......………………...…………………………………….........22
Figure 12 Sequence Diagram…………………...………………...……………………………………......23
Figure 13 Activity Diagram…………………......………………...………………………...…...………......24
Figure 14 Collaboration Diagram…………………......….……....…………………….………………......25
Figure 15 State Transition Diagram…………....………….……...……………………………………......26
Figure 16 ERD ………………….....………..……...……………………………………………………......27
Figure 17 HTML……………………………………………………………………………………………....28
Figure 18 CSS………………………………………………………………………………………………...29
v|Page
Revision History
Name Date Reason For Changes Version
vi | P a g e
Chapter 1
1. Introduction
Travel and tourism management system is used to book a tour from anywhere in the world by
a single dynamic website which will help the user to know all about the places and tour details
in a single website. The admin can add packages to the website from a certain travel agents
and hotels by create a tour page. Then the users can sign in and book each project, they can
be confirmed by the admin in them manage booking page. The user can see the confirmation
in their booking page. It is an easiest platform for all travelers which can be easily booked and
know the all details. Tour Management system is a dynamic website for tourism business. It
is dynamic and responsive web design. It is also called travel technology solution for agencies
& tour operation. Nearly everyone goes on a vacation for this ‘a Tourism management system’
would play a vital role in planning the perfect trip. The tourism management system allows the
user of the system access all the details such as location, events, etc. The main purpose is to
help tourism companies to manage customer and hotels etc. The system can also be used for
both professional and business trips.
1.1 General Information

Information to be provided in this sectio1n gives a specific name to the project as well as pertinent
information about the personal involved.
Project Name: Travels and Tourism Management System Starting Date: 1 NOV 2021
Controlling Agency: Government College University Faisalabad Final Date: 1 JAN 2022
Prepared by: Momna Safdar and Ayesha Abdul Ghafar Authorized by: GCUF
1.2 Purpose
During covid19 pandemic people were stuck in homes. Going for tours is necessary for
healthy life so we are providing a platform for those who want to go for tours. Especially we
are focusing on international tourists to get benefit from this platform.
1|Page
1.3 Document Conventions

In this document we are using Times New Roman as our font style. Heading size will be 18
and sub heading will be of 14. The paragraphs will contain number 12 font size. Line spacing
is 1.5.
1.4 Project Objective

The website generally intends to make things easier and facilitate tourists for going outside.
Tourists can simply check places, weather condition of that place and can book tours.
 Gives Accurate Information.

 Simplifies the manual work.
 It minimizes the documentation related work.
 Provides up to date information.
 Travelers details can be provided.
 booking confirmation notification
Agency Goals Project Objectives
Minimized the complexities and calculations It is a user-friendly application for tourism

for easy to use. management which provide the user to book a tour
from anywhere in the world by a single website.
Documented the operations to improve quality. It will help the user to know all about the places
and tour details in a single website.
Documented the operations to improve The website generally intends to make things easier
quality. and facilitate tourists for going outside.
2|Page
1.5 Intended Audience and Reading Suggestions

Students name: Momna Safdar and Ayesha Abdul Ghafar
Internal supervisor: Muhammad Umair
External supervisor:
1.6 Project Scope

As we know that some tours management websites already exist but the unique thing in our
website is that the user will able to check the place where he wants to visit. For Example, if
someone want to visit Murree he can first check the weather condition on this website, the
videos of that place and road map of that place.
Chapter 2
Overall Description
2.1 Product Perspective
As discussed before this type of website already exist but we are going to add some extra
features in this website. The website will be accepting online payment, there will be full
information of that place which user want to visit. The payment will be secure and no one
will be able to get know the secret information of the user.
2.2 Product Features

Below are describe the product features that are:
2.2.2 Data Flow Diagram(DFD)
A data flow diagram is graphical tool used to describe and analyze movement of data through
a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output, through processed, may be
described logically and independently of physical components associated with the
system. These are known as the logical data flow diagrams. The physical data flow
diagrams show the actual implements and movement of data between people, departments
and workstations. A full description of a system actually consists of a set of data flow
diagrams. Using two familiar notations Yourdon, Gene and Sarsen notation develops the
data flow diagrams. Each component in a DFD is labeled with a descriptive name. Process
is further identified with a number that will be used for identification purpose. The
3|Page
development of DFD’S is done in several levels. Each process in lower level diagrams can
be broken down into a more detailed DFD in the next level. The lop-level diagram is often
called context diagram. It consists a single process bit, which plays vital role in studying the
current system. The process in the context level diagram is exploded into other process at
the first level DFD.
The idea behind the explosion of a process into more process is that understanding at one
level of detail is exploded into greater detail at the next level. This is done until further
explosion is necessary and an adequate amount of detail is described for analyst to
understand the process.
Larry Constantine first developed the DFD as a way of expressing system requirements in
a graphical from, this lead to the modular design.
Figure 1: DFD Diagram

4|Page
2.3 User Classes and Characteristics

Here we will discuss the characteristics of User and Admin. These are given below.
Components: Here are describe the components of our methodology.
 Admin Authentication
 User Registration
 Package Creation
 Package Booking
 Booking Confirmation/manage
 Pay Online
 Give Feedback
 Issue Ticket
2.3.1. Admin Authentication

This module is mainly based on admin. System will check the admin user name and
password for authentication. After the verification for authorization the admin can be able to
precede the process. All works are done under his control.
Figure 2: Admin Authentication
5|Page
2.3.2. User Registration

This module covers the details about the registration of users which they can be register by
itself by adding data like name, password, email id and further details. After registration
they can be sign in by their username and password.
Figure 3: User Registration
6|Page
2.3.3 Package Creation
The admin can create packages by creating package page which the type, price, details, place
details all the travel tour package details can be added here. Which it will be showed in user
homepage.
Figure 4: Package Creation
2.3.4 Package Booking

In this module maintain the booking of travel packages by the user by selecting a various
package with date and certain comments.
Figure 5: Package Booking

7|Page
2.3.5 Booking Confirmation/Manage

Booking confirmation is the process of confirming the booked packages by the admin that is
booked by the user with date and comment. Also admin can manage the booking by
cancelling.
2.3.6 Online Payment
Online payment is for those who want to pay online.
2.3.7 Give Feedback
There will be a feedback option on the website. If a user wants to contact to the website
managers. If they are suggesting something or complaining.
Figure 6: Give Feedback
8|Page
2.3.7. Issue Ticket

Tickets can be issued for the user in the issue ticket page in the homepage of user the certain
booked packages only can be issued.
2.4 Operating Environment

The operating environment for this website is that it will be hosted online. And the operating
system for travels and truism management system is as given below.
 Distributed database
 User/server system
 Operating system: windows
 Database
 Platform: PHP
2.5 Design and Implementation Constraints

Our projects need both hardware and software. In hardware, we need computer/laptop. In
software requirements, we need Sublime platform and different languages like HTML, CSS
and PHP etc.
2.6 User Documentation

Our aim is to create a user-friendly user interface. Interface will require user name, email
etc. to login and then other simple things like picture. After these logins, the user will get
homepage and other activities option on user interface.
9|Page
Figure 7: User documentation
2.7 Analysis Model

After analyzing the requirements of the task to be performed, the next step is to analyze the
problem and understand its context. The first activity in the phase is studying the existing
system and other is to understand the requirements and domain of the new system. Both
the activities are equally important, but the first activity serves as a basis of giving the
functional specifications and then successful design of the proposed system. Understanding
the properties and requirements of a new system is more difficult and requires creative
thinking and understanding of existing running system is also difficult, improper
understanding of present system can lead diversion from solution.
In the analysis model we will discuss the methodologies and these are given below.
2.2.1 SDLC methodologies
This document plays a vital role in the development of life cycle (SDLC) as it describes the
complete requirement of the system. It means for use by developers and will be the basic
10 | P a g e
during testing phase. Any changes made to the requirements in the future will have to go
through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software
Development and Enhancement. This model was not the first model to discuss iterative
development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase
starts with a design goal and ends with a client reviewing the progress thus far. Analysis
and engineering efforts are applied at each phase of the project, with an eye toward the end
goal of the project.
The steps for Spiral Model can be generalized as follows:
 The new system requirements are defined in as much details as possible. This
usually involves interviewing a number of users representing all the external or
internal users and other aspects of the existing system.
 A preliminary design is created for the new system.
 A first prototype of the new system is constructed from the preliminary design. This
is usually a scaled-down system, and represents an approximation of the
characteristics of the final product.
A second prototype is evolved by a fourfold procedure:

I. Evaluating the first prototype in terms of its strengths, weakness, and risks.
II. Defining the requirements of the second prototype.
III. Planning a designing the second prototype.
IV. Constructing and testing the second prototype.
At the customer option, the entire project can be aborted if the risk is deemed too great. Risk
factors might involve development cost overruns, operating-cost miscalculation, or any other
factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
The existing prototype is evaluated in the same manner as was the previous prototype, and
if necessary, another prototype is developed from it according to the fourfold procedure
outlined above.
The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.
11 | P a g e
The final system is constructed, based on the refined prototype.

The final system is thoroughly evaluated and tested. Routine maintenance is carried on a
continuing basis to prevent large scale failures and to minimize down time.
2.8 Need for Computerization

We all know the importance of computerization. The world is moving ahead at lightning
speed and everyone is running short of time. One always wants to get the information and
perform a task he/she/they desire(s) within a short period of time and too with amount of
efficiency and accuracy. The application areas for the computerization have been selected
on the basis of following factors:
 Minimizing the manual records kept at different locations.
 There will be more data integrity.
 Facilitating desired information display, very quickly, by retrieving information from users.
 Facilitating various statistical information which helps in decision-making?
 To reduce manual efforts in activities that involved repetitive work.
 Updating and deletion of such a huge amount of data will become easier.
Chapter 3
3.1 System Features
System features are the most important part of the system. Here is describe the system
features below:
3.1.1 User data
This will store the data of the users for future use. For example, if a user wants to visit us in
future we can give them discounts also.
3.1.2 Information about visits
It will store all information about all tours we have visited.
3.1.3 Software Interfaces
In the below table explain the software interface.
12 | P a g e
Software used Description
Operating system We have chosen Windows operating system for its best support
and user-friendly.
Database To save the user records. We have chosen SQL.
PHP To implement the project we have chosen PHP language for

its more interactive support .
3.2 Feasibility Report

Preliminary investigation examines project feasibility; the likelihood the system will be useful
to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running
system. All system is feasible if they are unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
3.3 Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the following:
I. Does the necessary technology exist to do what is suggested?

II. Do the proposed equipment’s have the technical capacity to hold the data required to
use the new system?
13 | P a g e
III. Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
IV. Can the system be upgraded if developed?
V. Are there technical guarantees of accuracy, reliability, ease of access and data
security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation

System. The current system developed is technically feasible. It is a web based user
interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The
database’s purpose is to create, establish and maintain a workflow among various entities
in order to facilitate all concerned users in their various capacities or roles. Permission to
the users would be granted based on the roles specified. Therefore, it provides the
technical guarantee of accuracy, reliability and security. The software and hard requirements
for the development of this project are not many and are already available in-house at NIC
or are available as free as open source. The work for the project is done with the current
equipment and existing software technology. Necessary bandwidth exists for providing a
fast feedback to the users irrespective of the number of users using the system.
3.4 Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That
will meet the organization’s operating requirements. Operational feasibility aspects of the
project are to be taken as an important part of the project implementation. Some of the
important issues raised are to test the operational feasibility of a project includes the
following:
 Is there sufficient support for the management from the users?
 Will the system be used and work properly if it is being developed and implemented?
 Will there be any resistance from the user that will undermine the possible?
benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand,
the management issues and user requirements have been taken into consideration. So
14 | P a g e
there is no question of resistance from the users that can undermine the possible application
benefits.
The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.
3.5 Economical Feasibility

A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economic feasibility, the development cost in creating
the system is evaluated against the ultimate benefit derived from the new systems. Financial
benefits must equal or exceed the costs. The system is economically feasible. It does not
require any addition hardware or software. Since the interface for this system is developed
using the existing resources and technologies available at NIC, there is nominal expenditure
and economic feasibility for certain.
Chapter 4
External Interface Requirements
4.1 User Interface Requirements

We are aiming to design a user friendly interface for the website. If a user wants to check
the website so that he can’t face any difficulty in visiting the website.
4.2 Hardware Interfaces

This website can be run on any mobile, laptop or computer.
4.3 Software Interfaces

Describe the connections between this product and other specific software components
(name and version), including databases, operating systems, tools, libraries, and integrated
commercial components. Identify the data items or messages coming into the system and
going out and describe the purpose of each. Describe the services needed and the nature
of communications. Refer to documents that describe detailed application programming
interface protocols. Identify data that will be shared across software components. If the data
15 | P a g e
sharing mechanism must be implemented in a specific way (for example, use of a global
data area in a multitasking operating system), specify this as an implementation constraint.
4.4 Communications Interfaces

When a user is using this website he will have to login. Just simply for log in you will have to
register first and then log in by entering email and password only.
Chapter 5
Other Nonfunctional Requirements
5.1 Safety Requirements

While paying online the user need not to share his personal data with any other person.
5.2 Security Requirements

We recommend our users to have strong password which no any irrelevant person can guess.
5.3 Software Quality Attributes

This website provides quality tours for their customers. The customer can book a custom tour
for their families and can pay online. The customers can check the places first before booking
a tour.
5.4 Performance Requirements

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the
software engineering process that could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software. Testing is the
set of activities that can be planned in advance and conducted systematically. The underlying
motivation of program testing is to affirm software quality with methods that can economically
and effectively apply to both strategic to both large and small-scale systems.
16 | P a g e
5.5 Strategic Approach to Software Testing

The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the information
domain, functions, behavior, performance, constraints and validation criteria for software are
established. Moving inward along the spiral, we come to design and finally to coding. To
develop computer software, we spiral in along streamlines that decrease the level of
abstraction on each turn.
A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vertex of the spiral and concentrates on each unit of the software as
implemented in source code. Testing progress by moving outward along the spiral to
integration testing, where the focus is on the design and the construction of the software
architecture. Talking another turn on outward on the spiral we encounter validation testing
where requirements established as part of software requirements analysis are validated
against the software that has been constructed. Finally, we arrive at system testing, where
the software and other system elements are tested as a whole.
5.6 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the module.
The unit testing, we have is white box oriented and some modules the steps are conducted
in parallel.
 White Box Testing: This type of testing ensures that:

I. All independent paths have been exercised at least once
II. All logical decisions have been exercised on their true and false sides
III. All loops are executed at their boundaries and within their operational bounds
IV. All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form. We have created
independently to verify that Data flow is correct, all conditions are exercised to check their
validity, all loops are executed on their boundaries.
17 | P a g e
5.7 Conditional Testing

In this part of the testing each of the conditions were tested to both true and false aspects.
And all the resulting paths were tested. So that each path that may be generate on particular
condition is traced to uncover any possible errors.
5.8 Data Flow Testing

This type of testing selects the path of the program according to the location of definition and
use of variables. This kind of testing was used only when some local variable was declared.
The definition-use chain method was used in this type of testing. These were particularly
useful in nested statements.
5.9 Loop Testing

In this type of testing all the loops are tested to all the limits possible. The following exercise
was adopted for all loops:
All the loops were tested at their limits, just above them and just below them.
I. All the loops were skipped at least once.
II. For nested loops test the inner most loop first and then work outwards.
III. For concatenated loops the values of dependent loops were set with the help of
connected loop.
IV. Unstructured loops were resolved into nested loops or concatenated loops and tested
as above.
V. Each unit has been separately tested by the development team itself and all the input
have been validated.
18 | P a g e
Chapter 6
WBS Project Management
6.1 WBS
A work breakdown structure, or WBS, is a project management tool that takes a step-by-
step approach to complete large projects with several moving pieces. By breaking down
the project into smaller components, a WBS can integrate scope, cost and deliverables into
a single tool.
Figure 8: WBS
19 | P a g e
Chapter 7
Analysis Model
7.1 Use case Diagram

Use case diagram is a graphic depiction of interactions among the elements of Travels and
Tourism management system. It represents the methodology used in system analysis to
identify, clarify, and organized system requirement of tourism management system. The
main actors of Travels and Tourism Managements in this use case diagrams are: Admin,
System User, Agent, Students, who perform different type of use cases such as Customer,
Manage Travel Agents, Managed Package, Manager Transportation, Manage Booking,
Manage Hotel, Manage Tour Manage Users, and full Tourism Management System
operation.
Figure 9: Use Case Diagram
20 | P a g e
7.2 Class Diagram

Travels and Tourism management system class diagram describe the structure of a
Travels and Tourism management system classes, their attributes, operations or method
and the relationship among objects. The main classes of Travels and Tourism management
system are Package Transportation, Booking hotel, Tour, customers.
Figure 10: Class Diagram
21 | P a g e
7.3 Object Diagram

The use of object diagrams is fairly limited, mainly to show examples of data structures.
During the analysis phase of a project, you might create a class diagram to describe the
structure of a travel and tourism management system and then create a set of object
diagrams as test cases to verify the accuracy and completeness of the class diagram.
Figure 11: Object diagram
22 | P a g e
7.4 Sequence diagram.

It simply reveals the structure of a system, showing the sequence of messages and
interactions between actors and objects chronologically. Sequence diagrams show simple
iteration and branching. It is favorable for multi-tasking. This is the Login Sequence
diagram of Travels and Tourism Management system, where admin will be login in their
account using their credentials after login user can manage all the operations.
Figure 12: Sequence Diagram
23 | P a g e
7.5 State Transition Diagram

A state diagram is a type of diagram used in computer science and related fields to
describe the behavior of systems. State diagrams require that the system described is
composed of a finite number of states; sometimes, this is indeed the case, while at other
times this is a reasonable abstraction. Many forms of state diagrams exist, which differ
slightly and have different semantics.
Figure 13: State Transition Diagram
24 | P a g e
7.6 Activity Diagram

This activity diagram of Travels and Tourism Management System Which shows the flow
between the activity of Travel Agent, Package, Customer, Booking, Transportation. The
main activity involve in this diagram as follows.
 Travel Agent
 Package Activity
 Customer Activity
 Booking Activity
 Transportation Activity
Figure 14: Activity Diagram
25 | P a g e
7.6 Collaboration Diagram

UML Collaboration Diagram illustrates how components are wired together to larger
components and software systems that shows the structure of arbitrarily complex systems.
Concept Draw has 393 vector stencils in the 13 libraries that helps you to start using
software for designing your own UML Diagrams. You can use the appropriate stencils of
UML notation from UML Collaboration library with 36 object.
Figure 15: Collaboration Diagram
7.7 Entity Relationship Model

The relation upon the system is structure through a conceptual ER-Diagram, which not only
specifics the existential entities but also the standard relations through which the system
exists and the cardinalities that are necessary for the system state to continue.
26 | P a g e
The entity Relationship Diagram (ERD) depicts the relationship between the data objects.
The ERD is the notation that is used to conduct the date modeling activity the attributes of
each data object noted is the ERD can be described resign a data object description.
 The set of primary components that are identified by the ERD are
 Data object
 Relationships
 Attributes
 Various types of indicators.
The primary purpose of the ERD is to represent data objects and their relationships.
Figure 16: ER Diagram
27 | P a g e
Chapter 8
Tools & Technologies
8.1 Programming Languages

HTML, CSS, JavaScript, PHP
 HTML
HTML (Hypertext Markup Language) is the code that is used to structure a web page
and its content. For example, content could be structured within a set of paragraphs, a
list of bulleted points, or using images and data tables. As the title suggests, this article
will give you a basic understanding of HTML and its functions. Web browsers receive
HTML documents from a web server or from local storage and render the documents
into multimedia web pages. HTML describes the structure of a web page semantically
and originally included cues for the appearance of the document.
Figure 17: HTML
 CSS (Cascading Style Sheets)

Cascading Style Sheets (CSS) is a stylesheet language used to describe the
presentation of a document written in HTML or XML (including XML dialects such as
28 | P a g e
SVG, MathML or XHTML). CSS describes how elements should be rendered on screen,
on paper, in speech, or on other media. CSS is the language we use to style an HTML
document.CSS describe how HTML elements should be displayed.
Figure 18: CSS
 JavaScript
JavaScript is a scripting language that enables you to create dynamically updating
content, control multimedia, animate images, and pretty much everything else.
 PHP
PHP (Hypertext Preprocessor) is known as a general-purpose scripting language that
can be used to develop dynamic and interactive websites. It was among the first server-
side languages that could be embedded into HTML, making it easier to add functionality
to web pages without needing to call external files for data.
29 | P a g e
8.2 Databases/Data storages
MySQL, Database
• MySQL
MySQL is a relational database management system (RDBMS) developed by Oracle that is
based on structured query language (SQL). A database is a structured collection of data. It
may be anything from a simple shopping list to a picture gallery or a place to hold the vast
amounts of information in a corporate network.
• Database
Database languages, also known as query languages or data query languages, are a
classification of programming languages that developers use to define and access
databases, which are collections of organized data that users can access electronically. A
Database language has Data Definition Language (DDL), which is used to construct a
database & it has Data Manipulation Language (DML), which is used to access a database.
8.3 Operating System

Window
Appendix A: Glossary:
HTML: Hyper Text Markup Language
CSS: Cascading Style Sheet
SQL: Structure Query Language
PHP: Hypertext Preprocessor
30 | P a g e
References
Foster, D. (1985). Travel and tourism management. Macmillan Education Ltd.
Conrad, R., & Buck, M. (2007). Trends and Issues in Global Tourism... Berlin: Springer.
Singh, L. K. (2008). Fundamental of tourism and travel. Gyan Publishing House.
Evans, N., Storehouse, G., & Campbell, D. (2012). Strategic management for travel and
tourism. Taylor & Francis.
Gustafson, P. (2012). Managing business travel: Developments and dilemmas in corporate

travel management. Tourism management, 33(2), 276-284.
Goodrich, J. N., & Goodrich, G. E. (1987). Health-care tourism—an exploratory

study. Tourism Management, 8(3), 217-222.
Moutinho, L., & Vargas-Sanchez, A. (Eds.). (2018). Strategic management in tourism, cabi
tourism texts. Cabi.
Buhalis, D., & Costa, C. (Eds.). (2006). Tourism management dynamics: trends,
management and tools. Routledge.
Calantone, R. J., & Mazanec, J. A. (1991). Marketing management and tourism. Annals of
Tourism Research, 18(1), 101-119.
31 | P a g e
Appendix B: Check List
Check List Yes No
I. Starting/Ending Dates
II. Project Scope
III. Product modules (covering all aspects of scope)
IV. System Features (covering scope)
V. Interface Requirements
VI. Non-Functional Requirements
VII. WBS
VIII. Tools and Technologies Detail (for implementation)
IX. Plagiarism Report
32 | P a g e
Appendix C: Supervisory Committee
For Approval of any two Consultant Teachers
Teacher Consulted _. Teacher Consulted _.
Name: _ . Name: _ .
Designation: _ Designation: _
Comments: _ Comments: _
_ _
_ _
_ _
_ _
Signature: _ Signature: _
__
---------------------------------------------------------------------
33 | P a g e
(For office use only)

Date:
 Approved Group ID:
➢ Meeting Required: Date: Time: Place:
 Rejected
Remarks:
Project Title (if Revised):
Project Coordinator: _________________________________
34 | P a g e
35 | P a g e

Travels and Tourism Management System: Government College University Faisalabad

Uploaded by

Copyright:

Available Formats

Travels and Tourism Management System: Government College University Faisalabad

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

Travels and Tourism Management System: Government College University Faisalabad

Uploaded by

Copyright:

Available Formats

Government college university Faisalabad

TRAVELS AND TOURISM MANAGEMENT

Momna Safdar 2018-GCUF-062772

DEPARTMENT OF COMPUTER SCIENCE

Government College University Faisalabad

Revision History ................................................................................................................................. vi

1.1 General Information

1.3 Document Conventions

1.4 Project Objective

 Gives Accurate Information.

Agency Goals Project Objectives

Minimized the complexities and calculations It is a user-friendly application for tourism

1.5 Intended Audience and Reading Suggestions

1.6 Project Scope

2.2 Product Features

Figure 1: DFD Diagram

2.3 User Classes and Characteristics

Components: Here are describe the components of our methodology.

2.3.1. Admin Authentication

Figure 2: Admin Authentication

2.3.2. User Registration

Figure 3: User Registration

Figure 4: Package Creation

2.3.4 Package Booking

Figure 5: Package Booking

2.3.5 Booking Confirmation/Manage

2.3.7 Give Feedback

Figure 6: Give Feedback

2.3.7. Issue Ticket

2.4 Operating Environment

2.5 Design and Implementation Constraints

2.6 User Documentation

Figure 7: User documentation

2.7 Analysis Model

A second prototype is evolved by a fourfold procedure:

The final system is constructed, based on the refined prototype.

2.8 Need for Computerization

Software used Description

Database To save the user records. We have chosen SQL.

PHP To implement the project we have chosen PHP language for

3.2 Feasibility Report

3.3 Technical Feasibility

I. Does the necessary technology exist to do what is suggested?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation

3.4 Operational Feasibility

3.5 Economical Feasibility

4.1 User Interface Requirements

4.2 Hardware Interfaces

4.3 Software Interfaces

4.4 Communications Interfaces

5.1 Safety Requirements

5.2 Security Requirements

5.3 Software Quality Attributes

5.4 Performance Requirements

5.5 Strategic Approach to Software Testing

5.6 Unit Testing

 White Box Testing: This type of testing ensures that:

5.7 Conditional Testing

5.8 Data Flow Testing