Ets Fyp Report Nazim

Final Project Report
On
Expained Tourism System

(A web application)
Prepared By
Nazim Ali (Bcs-15-23)
Supervised By
Dr. Shafiq Hussain
Computer Sciences Department
Bahauddin Zakariya university, Sahiwal campus

DEDICATION
My Parents and Teachers all who’ve given me their support during the development
of this project and for giving good ideas to prove ourselves as intellectuals in front of
My Respected Teachers.
II
ACKNOWLEDGEMENT
Praise to Allah Almighty, Lord of the worlds, the Merciful and the Beneficent,
who gave us strength, thoughts and co-operative people to enable us to accomplish
this goal and fulfill the required functionalities.
This was all not possible without the guidance, continuous appreciation and moral
support by “Dr. Shafiq Hussain”. He was always there whenever we need him
help and ideas. We are really thankful to him who made our concepts clearer.
At last, we would like to acknowledge all of the assistance and contributions of
BZU Sahiwal campus for supporting us with all that is needed starting from the
books, and ending with the full care that it is providing us with, to help us to be
professionals in the field of Information Technology.
III
DECLARATION
I am hereby declaring that I have developed this application and accompanied

report entirely on the basis of my personal efforts. Not any of the portions of the
application work presented has been submitted of any application for any other
qualification or degree of this or any other university or institute of learning.
Student Name & Signature
Nazim ali
_______________
Submission Date: 24/04/19
IV
CERTIFICATE OF APPROVAL
It is to certify that the final year project of BS(CS) “Expained Tourism System
(A web application)” was developed by Nazim ali under the supervision of “Dr.
Shafiq Hussain” and that in him opinion, it is in scope, fully adequacy and quality
of the degree of Bachelors of Science in Computer Sciences.
Supervisor Head of Department
Dr. Shafiq Hussain Dr. Shafiq Hussain
Lecturer
Department of Computer Science Department of Computer Science
BZU, Sahiwal campus BZU, Sahiwal campus
______________________________ ______________________________
V
Table of Contents
1 INTRODUCTION ...............................................................................................1
1.1 Introduction ..................................................................................................2

1.2 Statement of the Problem ..............................................................................8
1.3 Benefit ...........................................................................................................4
1.4 Abstract..........................................................................................................5
1.5 Motivation .....................................................................................................6
1.6 Features..........................................................................................................7
1.7 Applications: .................................................................................................8
1.7.1 Administrator module: ..................................................................................9
1.7.2 Travels module: ...........................................................................................10
1.7.3 Reservations module: ..................................................................................12
1.7.4 Testimonials module: ..................................................................................13
1.8 OBJECTIVE:...............................................................................................14
1.9 Tools & Techniques……………………………………………………… 15
1.9.1 Hardware Details………………………………………………………………… 16
1.9.2 Software Details ...................................................................................................... 17
2 About Front End: ...............................................................................................18
2.1 PHP ..............................................................................................................19

2.2 HTML ..........................................................................................................20
2.3 CSS ..............................................................................................................21
2.4 Bootstrap......................................................................................................22
3 REQUIREMENT ANALYSIS ..........................................................................23
VI
Requirements Gathering Techniques ....................................................................24

3.1 Requirement Analysis .................................................................................25
3.1.1 Functional Requirements ........................................................................................ 26
3.1.2 Non-Functional Requirements ................................................................................ 27
3.2 Application Quality Attribute......................................................................28
3.2.1 Availability ............................................................................................................. 29
3.2.2 Maintainability ........................................................................................................ 30
3.2.3 Consistency ............................................................................................................. 31
3.2.4 Portability................................................................................................................ 32
3.2.5 Database Requirements ........................................................................................... 33
3.3 Use Cases.....................................................................................................34
3.3.1 UC1: Login ............................................................................................................. 35
3.3.3 UC3: Manage Members .......................................................................................... 36
3.3.4 UC4: Change Password .......................................................................................... 37
3.3.5 UC6: Logout ........................................................................................................... 38
3.4 The Necessity ..............................................................................................39
3.5.1 High Speed Internet Connection ............................................................................. 40
3.5.2 Signup ..................................................................................................................... 41
4 METHODOLOGY & WORKPLAN ................................................................42
4.1 Adopted Methodology .................................................................................43

4.2 Roles & Responsibilities .............................................................................44
5 SYSTEM ANALYSIS & DESIGN ...................................................................45
5.1 ER Diagram .................................................................................................46

5.2 Activity Diagram .........................................................................................47
5.2.1 Log in (user) ............................................................................................................ 48
5.3 Sequence Diagrams .....................................................................................49
5.3.1 Sequence diagram (search data).............................................................................. 50
5.3.2 Sequence diagram (fields recommendation) ........................................................... 51
5.4 Data flow diagram .......................................................................................52
5.4.1 Flow diagram (user panel) ...................................................................................... 53
VII
5.5 Class Diagram .............................................................................................54

5.6 Planning & Scheduling................................................................................55
5.6.1 Gantt chart ............................................................................................................... 56
6 SYSTEM IMPLEMENTATION .......................................................................57
6.1 Introduction .................................................................................................58

6.2 Screenshots ..................................................................................................59
7 SYSTEM TESTING ..........................................................................................60
7.1 Introduction .................................................................................................61

7.2 Testing Plan .................................................................................................62
7.2.1 Unit Testing ............................................................................................................ 63
7.2.2 System Testing ........................................................................................................ 64
7.2.3 Integration Testing .................................................................................................. 65
7.2.4 User Acceptance Testing ........................................................................................ 66
7.3 Test Cases ....................................................................................................67
7.4 Testing Results ............................................................................................68
8 CONCLUSION & FUTURE WORK ...............................................................69
8.1 Conclusion ...................................................................................................70

8.2 Future Work.................................................................................................71
8.3 Reference .....................................................................................................72
VIII
CHAPTER # 1
INTRODUCTION
1 INTRODUCTION
In this chapter, we will introduce this application, software tools, problem statement, objectives,
application, motivation relevance to courses and tools & techniques which are used to implement
this application
1.1 Introduction
Travel and Tourism management system:

This is an online project developed using Php and MySQL. The purpose of this project is to
provide the complete information about the Places available for a tour. There are 2 different
types of users. First the customer visits the site and enters the place from where to where he
wishes to travel. He also provides the date as when he would like to travel. Then he sends these
details to the travel and tourism agency. The employee of travel and tourism agency receives the
mail and check which Place is available for that day. If the customer agrees for any one of the
quotation, he can reply back along with agreed quotation. Then the agency will take down all the
details of the customer and will send a confirmation message to the customer. This software is
user friendly and helps in finding the vehicle sooner rather than wandering manually everywhere
to find for Place. After the travelling the customer can come back to the site and enter his
feedback about the travel and tourism agency. If any good feedback will be taken positively and
if any negative feedback too will be taken positively and try to improve what had lacked. The
report is also generated periodically and the database will be cleared according to the time span
for faster performance.
This project development a website for Tour & Travel management system with HTML-,
CSS, PHP as front-end & MYSQL as back-end. Tour & Travel management system
planning the tour for their customer. It is an application which decreases few efforts of
planning of trip or making of yours holidays happy. This system provides better services
for booking tickets & planning for visiting places & hotels facility & transportation mode.
1.2 Statement of the Problem
We know peoples are not aware of facilities of travel and tour agency, what different kinds of
tasks they can perform according to their interest and related thinking. They have no idea which
places and points are related to their holiday. They face a lot of difficulties in choosing their
visiting point. We are going to build an online “Expained tourism system” website to facilitate
peoples with finding points according to their interest and holiday. Where they can easily find
their visiting, point.
They can also find all information about visiting points where they can spend his holidays.
1.3 Abstract
I have developed this project using php language for front end and MySQL server for
back end.
This project has to maintain the records of:
 Admin enter his user id and password for login to enter master module screens.
 Admin can maintain his data sources.
 Customer will call/ visit with trip details.
 Customer enters his complete itinerary details with dates and time.
 Administrator will enter vehicle, Hostel, and activity details with tariff.
 Administrator giving information to generate various kinds of MS report.
 Customer will choose the city for visit and also chose the place and hotel for stay.
 Customer will choose the city for visit and also chose the bus for reached the required
destination.
 Customer will also give comment after trip.
8
1.4 Benefit
a) Faster processing time and more accurate data for travel requests and reimbursements
b) Ability for travelers to track authorization and reimbursement request status through the
system rather than via phone calls or campus mail
c) Major technological upgrades to the current travel system
d) Many new features and enhancements
1.5 Motivation
Motivation can be defined as an internal psychological force arising from an unsatisfied need,
which subsequently pushes individuals to engage in a specific need-fulfilling behavior or
activity. In tourism research, motivation is considered a major force in compelling tourist
behaviors. Psychosocial motivations in tourist behavior can be divided into ‘push’ and ‘pull’
factors leading individuals to travel.
Tourists from south country places often travel for a variety of reasons, including enjoying
holiday’s purposes cultural or family reasons; in order to combine a minor procedure.
1.6 Features
Tourism Website Builder is a complete Content Expained tourism System for the travel &
tourism industry that delivers the features most requested by independent tourism operators,
destination marketing groups, tourism associations and travel professionals.
Anyone - Anywhere - Anytime
All functions are secure, intuitive and user friendly, and can be operated by non-technical
persons at any time, from any remote location, with an Internet connection and Web browser. A
high speed Internet connection is not required.
1.7 Applications
This application is built such a way that it should suits for all type of visitors in future. So every
effort is taken to implement this project in this place, on successful implementation in this visit
points, we can target other most visit places in the country.
This application consists following modules.
1. Administrator module
2. Travels module
9
3. Reservations module
4. Testimonials module
1.7.1 Administrator module:

This module provides administrator related functionality. Administrator manages all information
and has access rights to add, delete, edit and view the data related to places, travels, routes,
bookings, hotels etc.
1.7.2 Travels module:

This module provides the details of various travel points. A user can select the appropriate visit
point depending on convenience and accessibility.
1.7.3 Reservations module:

This module provides functionalities that allow a user to book tickets or cancel previously
booked tickets. The module maintains the details of all reservations made so far and allows
administrator to either confirm or reject the bookings.
1.7.4 Testimonials module:

Users of this application can post their opinions, complaints and suggestions regarding this portal
and services to the administrator. Accordingly, the administrator can take various steps to act on
the complaints and suggestions.
1.8 Objectives
The objective of the Expained Tourism System project is to develop a system that automates the
processes and activities of a travel and the purpose is to design a system using which one can
perform all operations related to traveling.
The main objectives of our project are following

 Provide facility of finding your visiting points.
 Provide all information about your visiting points.
 All information about top visiting places of Pakistan (Hotel locations, Bus reservation,
etc).
10
1.9 Tools & Techniques
Expained Tourism System is Web based Project consists of software and hardware tools.
1.9.1 Hardware Details
 Processer--i3
 Hard Disk—1TB
 Memory—4GB RAM
1.9.2 Software Details
 Sublime Editor text

 My SQLI
 Xamp server
 Window xp, windows (7,8,10).
11
CHAPTER # 2
About Front End

The front end is an interface between the user and the back end. The front and back ends may be
distributed amongst one or more systems. In network computing, front end can refer to any hardware
that optimizes or protects network traffic. It is called application front-end hardware because it is placed
on the network's outward-facing front end or boundary. Network traffic passes through the front-end
hardware before entering the network.
These days, front-end development refers to the part of the web users interact with. In the past,
web development consisted of people who worked with Photoshop and those who could code
HTML and CSS. Now, developer’s need a handle of programs like Photoshop and be able to
code not only in HTML and CSS, bootstrap, which is a compiled library of JavaScript.
Most of everything you see on any website is a mixture of HTML, CSS, and Bootstrap, which
are all controlled by the browser. For example, if you’re using Google Chrome or Firefox, the
browser is what translates all of the code in a manner for you to see and with which to interact,
such as fonts, colors, drop-down menus, sliders, forms, etc. In order for all of this to work,
though, there has to be something to support the front-end; this is where the backend comes into
play.
12
2.1 PHP:-
Introduction
PHP is now officially known as “PHP: Hypertext Pre-processor”. It is a server-side scripting

language usually written in an HTML context. Unlike an ordinary HTML page, a PHP script is
not sent directly to a client by the server; instead, it is parsed by the PHP binary or module,
which is server-side installed. HTML elements in the script are left alone, but PHP code is
interpreted and executed. PHP code in a script can query databases, create images, read and write
files, talk to remote servers – the possibilities is endless. The output from PHP code is combined
with the HTML in the script and the result sent to the user’s web-browser, therefore it can never
tell the user whether the web-server uses PHP or not, because the entire browser sees is HTML.
PHP’s support for Apache and MySQL further increases its popularity. Apache is now
the most-used web-server in the world, and PHP can be compiled as an Apache module. MySQL
is a powerful free SQL database, and PHP provides a comprehensive set of functions for working
with it. The combination of Apache, MySQL and PHP is all but unbeatable.
That doesn’t mean that PHP cannot work in other environments or with other tools. In
fact, PHP supports an extensive list of databases and web-servers. While in the mid-1990s it was
ok to build sites, even relatively large sites, with hundreds of individual hard-coded HTML
pages, today’s webmasters are making the most of the power of databases to manage their
content more effectively and to personalize their sites according to individual user preferences.
13
Basic PHP Syntax
A PHP scripting block always starts with
<? php and ends with ?>.
A PHP scripting block can be placed anywhere in the document.

On servers with shorthand support enabled you can start a scripting block with
<? And end with ?>.
However, for maximum compatibility, we recommend that you use the standard form
(<?php) rather than the shorthand form.
A PHP file normally contains HTML tags, just like an HTML file, and some PHP scripting code.
2.2 HTML
HTML or Hyper Text Markup Language is the standard markup language used to create web
pages.
HTML was created in 1991 by Tim Berners-Lee at CERN in Switzerland. It was designed to
allow scientists to display and share their research.
HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets
(like <html>). HTML tags most commonly come in pairs like <h1> and </h1>, although some
tags represent empty elements and so are unpaired, for example <img>. The first tag in a pair is
the start tag, and the second tag is the end tag (they are also called opening tags and closing
tags).
The purpose of a web browser is to read HTML documents and compose them into visible or
audible web pages. The browser does not display the HTML tags, but uses the tags to interpret
the content of the page. HTML describes the structure of a website semantically along with cues
for presentation, making it a markup language rather than a programming language.
14
HTML elements form the building blocks of all websites. HTML allows images and objects to
be embedded and can be used to create interactive forms. It provides a means to create structured
documents by denoting structural semantics for text such as headings, paragraphs, lists, links,
quotes and other items. It can embed scripts written in languages such as Java Script which affect
the behavior of HTML web pages.
HTML is descriptive markup language. Library of various markup languages is defined in

various browsers.
a) HTML Images - The <img> Tag and the Src Attribute
In HTML, images are defined with the <img> tag.
The <img> tag is empty, which means that it contains attributes only, and has no closing tag.
To display an image on a page, you need to use the src attribute. Src stands for "source". The
value of the src attribute is the URL of the image you want to display.
Syntax for defining an image:
<img src="url" alt="some text">
b) HTML FORMS
HTML forms are used to pass data to a server.
The <form> tag is used to create

an HTML form:
<form>
.input elements.
</form>
15
An HTML form can contain input elements like text fields, checkboxes, radio-buttons, submit
buttons and more. A form can also contain select lists, text area, field set, legend, and label
elements.
c) Image tag (<img>) :

To add an image to an HTML document, we just need to include an <IMG> tag with a
reference to the desired image. The <IMG> tag is an empty element i.e. it doesn’t require a
closing tag and we can use it to include from small icons to large images.
Syntax: <img src=”URL” alt=”alternative text”>
d) HTML Lists:
An ordered list:
An unordered list:
 The first list item
 List item
 The second list item
 List item
 The third list item
 List item
2.3 CSS
CSS tutorial or CSS 3 tutorial provides basic and advanced concepts of CSS technology. Our
CSS tutorial is developed for beginners and professionals. The major points of CSS are given
below:
a) CSS stands for Cascading Style Sheet.

b) CSS is used to design HTML tags.
c) CSS is a widely used language on the web.
16
d) HTML, CSS and JavaScript are used for web designing. It helps the web designers to
apply style on HTML tags.
Cascading Style Sheets (CSS) is a style sheet language used for describing the look and
formatting of a document written in a markup language. While most often used to style web
pages and user interfaces written in HTML and XHTML, the language can be applied to any
kind of XML document, including plain XML, SVG and XUL. CSS is a cornerstone
specification of the web and almost all web pages use CSS style sheets to describe their
presentation.
CSS is designed primarily to enable the separation of document content from document
presentation, including elements such as the layout, colors, and fonts. This separation can
improve content accessibility, provide more flexibility and control in the specification of
presentation characteristics, enable multiple pages to share formatting, and reduce complexity
and repetition in the structural content (such as by allowing for table less web design).
CSS can also allow the same markup page to be presented in different styles for different
rendering methods, such as on-screen, in print, by voice (when read out by a speech-based
browser or screen reader) and on Braille-based, tactile devices. It can also be used to allow the
web page to display differently depending on the screen size or device on which it is being
viewed. While the author of a document typically links that document to a CSS file, readers can
use a different style sheet, perhaps one on their own computer, to override the one the author has
specified.
With plain HTML you define the colors and sizes of text and tables throughout your pages. If
You want to change a certain element you will therefore have to work your way through the
Document and change it. With CSS you define the colors and sizes in "styles". Then as you
Write your documents you refer to the styles. Therefore: if you change a certain style it will
Change the look of your entire site. Another big advantage is that CSS offers much more
Detailed attributes than plain HTML for defining the look and feel of your site.
2.4 Bootstrap
17
Bootstrap is a language which is used for designed and make a website attractive for user and
viewer’s.
Different Tags
<div> Element </div>
Div is used for make ant box or any other thing in which we make any table any form an thing .
CHAPTER # 3
REQUIREMENT ANALYSIS
3 REQUIREMENT ANALYSIS
In this chapter requirements analysis is discussed. For developing any project, the major problem
is requirement gathering. Asking questions from clients is straight forward than collecting
requirements. We will also focus on functional and non-functional requirements.
The procedure for gathering requirements has its own defined procedure according to the
complexity of the application. To define project schedule and processing, different models and
techniques also focused on this chapter.
Requirements Gathering Techniques
A requirement can be defined as a condition or capability that must be processed by a product or

an application. Techniques that can be used for collecting requirements are as follows:
 By questionnaire and survey

 By interview
 By observations
18
 Using software tools

 Using techniques for decision making
The techniques we have used to collect requirements are observations and interviews.
3.1 Requirement Analysis
Requirements analysis is the process of planning, forecasting and studying the overall customer
needs of the application requirements. Requirements analysis is further divided into two parts:
1. Functional Requirements
2. Non-Functional Requirements
3.1.1Functional Requirements
Functional requirements are the requirements that should be provided by an application. It is

defined as a service statement. Functional requirements tell how an application should behave in
different situations and how it will react to a particular input.
Functional requirements of the are as follows: The main functions of our project are following
 Provide facility of finding your correct visit point.

 Makes easy to find point related to holiday duration.
 Customer can comment to ask some question.
 All information about top visiting points of Pakistan.
 Customer can create their info criteria and will upload their all data.
 Recommendations will be sending to their account.
 Customer received confirm message.
3.1.2 Non-Functional Requirements
Non-functional requirements are the constraints or checks on the services and functions
provided by an application such as constraints on the development standards/process and
constraints of time etc.
Non-Functional requirements of are as follows:
19
 Application shall provide better response and performance. It shall take initial load time
depending on internet connection strength.
 Application must be efficient.
 Application must be user interactive.
 Application must be secure by using different standard authentication.
3.2 Application Quality Attribute
3.2.1 Availability
 Application must be responsive and available at every time.

 Availability of any speed internet connection is the major requirement of the application.
3.2.2 Maintainability
Making changes or upgradeability in the site will not be that much difficult. By having some
knowledge of programming, some features of the application might be converted to a new
version.
3.2.3 Consistency
When an administrator is updating information consistency must hold there.
3.2.4 Portability
ETS is web application that is why there is no problem in portability process.
3.2.5 Database Requirements
In this section, the database requirements for this application are mentioned:
We used MYSQL Server for database purpose.
3.3 Use Cases
An important part of the analysis phase is to drawing the diagrams of Use cases. They are used
through the phase of analysis of a project to find and divide functionality of the application.
Application is separated into actors and use cases.
20
Actors play the role that is played by the application users. Use cases define the application
behavior when one of the actors sends any particular motivation. This type of behavior can be
described by text. It describes the motivation nature that activates use case, the inputs and
outputs to some other actors and the behavior of conversion of inputs to the outputs. Usually the
use case describes everything that can go wrong during the detailed behavior and what will be
helpful action taken by the application.
Some of the use cases are as follows:
Some of the use cases are as follows:
3.3.1 UC1: Login
Actor: User
Figure 3.1: Login (use case)
Pre-Condition:
1. For the member, he/she must have registered already in application by the administrator.
2. User must enter correct Email address and password for login.
Post-Condition:
User can access to application’s main features.
Basic Path:
1. Enter Email-Address and password for login.

2. The application verifies the correct format and valid email address and Password.
21
3. If provided inputs are correct, the application displays the all other user’s content of the
application and session of particular user started.
Constraints:
1. If provided email address and password are incorrect or invalid, application redirect to
main page.
Non-Functional Requirements:
1. Short Response Time

2. Better performance
3. Availability
3.3.2 UC2: Manage Members
Actor: Administrator
Figure 3.2: Manage Members (Use Case)
Pre-Condition:
1. UC1 & UC2

2. The member’s detail is required.
Post-Condition:
1. The member information should be edited and deleted.
22
Basic Path:
1. The administrator views the member’s detail and then select a particular member to
perform these activities.
2. Update information of specific member by entering updated information and click on
update button.
3. The application verifies the valid entered inputs and updated.
4. For deleting information of specific member, applications display the message of
confirmation.
5. Administrator clicks on delete button for deleting that member.
6. The application commits changes to the database.
Non-Functional Requirements:
1. Better response
2. Easy to use
3. Secure
4. Availability
5. Short response time.
3.3.3 UC3: Change Password
Actor: User
23
Figure 3.3: Change Password (Use Case)
Pre-Condition:
3. UC1
Post-Condition:
1. Password must be updated into the database.

2. User can view new password in a text field.
Basic Path:
1. User select change password menu from sidebar menu list.

2. User enters new password to update old password.
3. The application verifies and updated into database.
4. Click on Logout to check whether the password has changed or not.
CONSTRAINTS:
1. User must enter valid inputs for password.
NON-FUNCTIONAL REQUIREMENTS:
1. Short response time.

2. Efficient
3. Availability
4. Secure
24
3.3.4 UC4: Logout
Actor: User
Figure 3.4: Logout (Use Case)
Pre-Condition:
1. UC1
Post-Condition:
1. Main page displayed to the user.
Basic Path:
1. The member can perform activities with or without login.

2. Click the logout for logging out.
3. Clicks on logout to close the connection with the application and application move the
user towards main page of the application for login again if he/she wants to.
25
NON-FUNCTIONAL REQUIREMENTS:
1. Secure
2. Reliable
3. Better performance
4. Short Response Time
3.4 The Necessity
There are some necessities for this online application portal to run properly are as follows:
3.4.1 High Speed Internet Connection
Online application portal requires high speed internet connection to run properly.
3.4.2 Sign In
The admin must be sign in with application before using application portal.
26
CHAPTER # 4
METHODODLOYAND WORKPLAN
4 METHODOLOGY & WORKPLAN
In this chapter, we will discuss that what are the existing methodologies and which one we have
chosen for implementation of this project in an effective way, also we will discuss advantages of
adopted methodology.
What is methodology and why we need it?
Whenever a small or large project has started to develop, first thing all of programmers required
is methodology. Methodology is a way of developing a project, in which all of the programmers
gather the user’s requirements, design the project, implement it, and after all this testing and
maintenance of the project, in a satisfaction of user and according to the project requirements.
4.1 Adopted Methodology
“Incremental model” is used to develop this project, in which we divided our work in multiple
modules. All these modules are further divided into more easily managed modules which made
up the actual implementation of the requirements.
Reason behind using this model is:
 It is easy to test and debug the product during iterations.

 Software released in increments over time is more likely to satisfy changing user
requirements than if it were planned as a single overall release at the end of the same
period.
 Generates working software quickly and early during the software life cycle.
 This model is more flexible – less costly to change scope and requirements.
 It is easier to test and debug during a smaller iteration.
 In this model customer can respond to each built.
 Lowers initial delivery cost.
 Easier to manage risk because risky pieces are identified and handled during it’d
iteration.
Figure 4.1: Adopted Methodology
4.2 Roles & Responsibilities
Project development team is consisting of one member. In order to accomplish a goal,

documentation and development is done by only one person.
19
CHAPTER#5
SYSTEM ANALYSIS & DESIGN
SYSTEM ANALYSIS & DESIGN
In this chapter requirements analysis, feasibility study, planning, forecasting, modeling,

scheduling and design of the project is discussed. For developing any project, the major problem
is requirement gathering. Asking questions from clients is straightforward than collecting
requirements. We will also focus on functional and non-functional requirements.
The procedure for gathering requirements has its own defined procedure according to the
complexity of the application. To define project schedule and processing, different models and
techniques also focused on this chapter.
5.1 ER Diagram
22
5.2 Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modeling Language,
activity diagrams are intended to model both computational and organizational processes (i.e.,
workflows), as well as the data flows intersecting with the related activities.
5.2.1 Log in (user)
Figure 5.1: Activity diagram (login)
23
5.3 Sequence Diagrams
Sequence diagram uses concept of a Message-Sequence-Chart. It shows interactions of objects in

a sequence of time. It shows the classes and objects involved in the scenario and the message
sequence between the objects which is desired to carry out the functionality of a given scenario.
Sequence diagrams are usually related with the understanding of use case in the logical View of
the system which is under development. “Sequence diagrams are sometimes called event
diagrams, timing diagrams, event scenarios”.
A parallel vertical line on sequence diagram is called lifeline. Different objects or processes that
live simultaneously, and, on horizontal arrows, the messages exchanged, in the order in which
processes occur. This allows some specification of some simple runtime scenarios in a graphical
pattern.
5.3.1Sequence diagram (search data)
Figure 0.2: Sequence Diagram (search data)
24
5.3.2 Sequence diagram (fields recommendation)
Figure 0.3: Sequence Diagram
5.4 Data flow diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. A DFD is often used as a preliminary step
to create an overview of the system without going into great detail, which can later be elaborated.
DFDs can also be used for the visualization of data processing .
25
5.4.1Flow diagram (user panel)
Figure 5.4: Flow diagram (user panel)
5.5 Class Diagram
The class diagram is the main building block of object direct modeling. It is used both for
general conceptual modeling of the systematic of an application, and for detailed modeling
translating the models into programming. Class diagrams can also be used for data modeling.
The classes in a class diagram represent both the main objects and or interactions in the
application and the objects. In the class diagram these classes are represented with boxes which
contain three parts
 The upper part of holds the name of the class

 Next one holds the parameters of the class
 Last one holds the methods of the class
26
Figure 0.5: Class diagram (ETS)
5.6 Planning & Scheduling
5.6.1 Gantt chart
A Gantt chart is a scheduling technique that is used commonly in project management. It is one
of the useful and common ways of representation of activities displayed in contrast to time. On
the vertical side of the chart activities list is displayed and on the top a time scale which is
appropriate. A bar represents each activity’s length and also shows the start date, end date and
duration of the activity. This shows following information.
 “What the different activities are?”

 “When an activity starts and ends?”
 “How much long each activity is scheduled to finish?”
 “The start and finish date of the whole project.”
27
Key Milestones of the Project with dates

Table 0-1: Project Plan & Key Milestones
Key Milestones of the Project with dates

S. No Elapsed time since start of the Milestone Deliverable
project
1. 1 Month ( November 2018) Analysis & Complete Research
Requirements Proposal
2. 1 Month ( December 2018) Planning, scheduling Report
and purchase of
hardware
3. 1 month (January 2019) Modeling & design Report
4. 2 month ( February 2019) Coding & testing Software System
5. March 2019 Deployment Hardware &
Software System
28
CHAPTER#6
SYSTEM IMPLEMENTATION
6 SYSTEM IMPLEMENTATION
In this chapter, we’ll focus on an implementation of “Expained Tourism System” application.

Where administrator and user can perform many activities on web application.
6.1 Introduction
The most important goal of this phase is to develop the application. The work in this phase
should be much more straightforward as a result of the work done in the planning and design
phases. This phase involves changing design specifications into executable programs. When the
design is there, developers can have an idea on looks of application. All that is needed by
developers is to put them at one place to understand about the intended project.
6.6 Screenshots
Login page
This is login page. User gives information about him like email, and password and creates an
account.
Figure 6.1: Sign In (Screenshot)
Home page
This activity is a home page or menu page for user. User see programs, visit places detail and also
go for booking.
Figure 6.2: Home Page (Screenshot)
38
Admin detail page (admin panel)

This activity is on admin side. Admin can view information of all other admins. Admin also can
add new admin.
Figure 6.3 Admin detail (Screenshot)
Users detail page

This activity is also in admin panel. Admin view all users their information and also delete user.
Figure 6.4: Users detail (Screenshot)
39
Visiting point’s info

In this screen shot you see the visiting places for visit.
Figure 6.5: Visiting points detail (Screenshot)
Hotel information (admin panel)

Admin can view all reserved hotel. Update any information and also delete any data.
Figure 6.6: Hotel info (Screenshot)
40
Rooms Information
You see all the rooms and hotel and select any one form the admin panel.
Figure 6.7: Room info (Screenshot)

Places information
You see the all most famous places and most attractive places here.
Figure 6.8: Places info (Screenshot)
41
CHAPTER#7
SYSTEM TESTING
7 SYSTEM TESTING
In this chapter, we will discuss the testing phase of developed application “Expained Tourism
System” in different manner to know that how much efficient and effective application is?
7.1 Introduction
A process of performing as application or program with the intention of finding errors and
whether the application is fulfilling user needs. It can also be defined as the ability of a program
in meeting the required or desired results.
In many methodologies of software engineering, a separate phase is called phase of testing which
is performed after the completion of the implementation. There is a benefit in using this approach
that it is hard to see one's own mistakes, and a fresh eye can find observable errors much faster
than the person who has read the material many times.
7.2 Testing Plan
A process of performing as application or program with the intention of finding errors and
whether the application is fulfilling user needs.
7.2.1 Unit Testing
The software units in an application are modules and routines that are assembled and
integrated to perform a specific function. Unit testing focuses first on modules, independently of
one another, to locate errors. This enables, to detect errors in coding and logic that are contained
within each module. This testing includes entering data and ascertaining if the value matches to
the type and size supported by php. The various controls are tested to ensure that each performs
its action as required.
42
Commonly used method is White-Box Testing method. Every time a component of the program
is changed, it can be run for testing that is the biggest and famous benefit of this testing phase.
Issues that are arise during this phase, allowing being resolved as quickly as possible. Unit
testing is familiar by software developers. It allows them to test their application units before
move them to testers for formal testing.
7.2.2 System Testing
To test the complete application as a whole, system testing has been used. It is beneficial to
check whether the application meets its requirements and fulfill Quality Standards.
7.2.3 Integration Testing
Integration testing allows the software developers to integrate all of the components/ units of the
application within a program and then test them in a group. Basically, this testing level is used to
catch the defects in the user interface between the functions/ modules. It is useful to determine
how logically and efficiently all the units/ components are running together.
Here the streaming module and encoding module options are integrated and tested. This testing
provides the assurance that the application is well integrated functional unit with smooth
transition of data.
7.2.4 User Acceptance Testing
User acceptance of an application is the key factor for the success of any application. The
application under consideration is tested for user acceptance by constantly keeping in touch with
the application users at time of developing and making changes whenever required.
43
7.3 Test Cases
Table 7-1: Testing Cases
Test Cases Objectives
1 To make sure that user can easily

understand and can use the application
2 Make sure that user can easily login
3 Make sure that administrator can easily

update, delete anything.
4 Make sure that admin can view detail of

users.
5 Make sure that user can easily view fields

and places details.
6 Make sure that related recommendation of

fields sent to user.
44
Make sure that the application run at

7
cross-platforms successfully.
7.4 Testing Results
Table 7-2: Testing Result
CRITERIA Test Status REMARKS
All the graphical user interface options display successfully.
Test successful None
Enter valid login user email address and password and then
press login
Add, delete, update and view admin using database
45
Admin view detail of users. Test successful None
User All details are shown against specific user’s ID. Test successful None
Run application in different platforms Test successful None
Run application on low speed internet

46
CHAPTER # 8
CONCLUSION & FUTURE WORK
8 CONCLUSION & FUTURE WORK
In this chapter, we will discuss the results and discussions of this framework “Expained
Tourism System” with conclude remarks and will also discuss related future work of this
application.
8.1 Conclusion
“Expained Tourism system (website)” is developed for provide travel and tourism,
information. This application provides a platform to peoples which is best for him. What best
places which they want to visit. What they can do for relaxation after don a very hard work in
whole week.
This application provides such environment this is more efficient and user friendly.
8.2 Future Work
In next my first preference is to enhance this application by providing more new features that are
as follows:
 All famous places of Pakistan

 Provide Offline website
 Domain recommendation after Matriculation
 Place detail
 Provide all rent structure and location of hotel in site
 Provide best way for reached on famous points
 Provide location of all places nearest to user’s location
8.3 Reference
 Create ER diagram form http://www.draw.io

 Get some useful information from http://www.w3school.com
 Get bootstrap files from http://www.bootswatch.com
 Get JQuery file from http://www.JQuery.com
 Get Font -Awesome icon from http://www.font-awesome.com
…………………………………End………………………………………….
44

Ets Fyp Report Nazim

Uploaded by

Document Information

Original Description:

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

Ets Fyp Report Nazim

Uploaded by

Copyright:

Available Formats

Final Project Report

Expained Tourism System

Nazim Ali (Bcs-15-23)

Computer Sciences Department

Bahauddin Zakariya university, Sahiwal campus

I am hereby declaring that I have developed this application and accompanied

Student Name & Signature

Submission Date: 24/04/19

Supervisor Head of Department

Dr. Shafiq Hussain Dr. Shafiq Hussain

Department of Computer Science Department of Computer Science

BZU, Sahiwal campus BZU, Sahiwal campus

1.1 Introduction ..................................................................................................2

2.1 PHP ..............................................................................................................19

Requirements Gathering Techniques ....................................................................24

4.1 Adopted Methodology .................................................................................43

5.1 ER Diagram .................................................................................................46

5.5 Class Diagram .............................................................................................54

6.1 Introduction .................................................................................................58

7.1 Introduction .................................................................................................61

8.1 Conclusion ...................................................................................................70

Travel and Tourism management system:

1.2 Statement of the Problem

This application consists following modules.

1.7.1 Administrator module:

1.7.2 Travels module:

1.7.3 Reservations module:

1.7.4 Testimonials module:

The main objectives of our project are following

1.9 Tools & Techniques

1.9.1 Hardware Details

1.9.2 Software Details

 Sublime Editor text

About Front End

PHP is now officially known as “PHP: Hypertext Pre-processor”. It is a server-side scripting

Basic PHP Syntax

A PHP scripting block always starts with

<? php and ends with ?>.

A PHP scripting block can be placed anywhere in the document.

<? And end with ?>.

HTML is descriptive markup language. Library of various markup languages is defined in

a) HTML Images - The <img> Tag and the Src Attribute

In HTML, images are defined with the <img> tag.

Syntax for defining an image:

<img src="url" alt="some text">

HTML forms are used to pass data to a server.

The <form> tag is used to create

c) Image tag (<img>) :

Syntax: <img src=”URL” alt=”alternative text”>

a) CSS stands for Cascading Style Sheet.

<div> Element </div>

Requirements Gathering Techniques

A requirement can be defined as a condition or capability that must be processed by a product or

 By questionnaire and survey

 Using software tools

3.1 Requirement Analysis

Functional requirements are the requirements that should be provided by an application. It is

 Provide facility of finding your correct visit point.

Non-Functional requirements of are as follows:

3.2 Application Quality Attribute

 Application must be responsive and available at every time.

When an administrator is updating information consistency must hold there.

ETS is web application that is why there is no problem in portability process.