Software Requirement Specification

For
Online Tour &Travelling website
Submitted By: Ved Prakash
M.I.E.T College
CSE Branch

1. Project Profile
Project Definition

Tour and Travel Management System

Objective

Main Objective of this system is to provide Online Registration, Tour Package

Information, Ticket Booking, Online Payment and Searching Facility for
Customer and also Generate Different types of Report.

Front-end

Microsoft ASP.Net 2010 with c# Framework 4.0.

Back-end

SQL Server 2008.

Tools

M.S.Office, Adobe Photoshop.

Internal Guide

Mr. Dhaval k. Raval.

Submitted To

Department Of Computer Science

Developed By

1.

Patel Urvish k.

2.

Rajput Sureshji R.

2. Existing System
All Work are done Manually.
In Manual Booking System Customer has to go to the
Travelling office.
Ask Inquiry for Travelling then Book ticket Finally Pay Payment
& Collect Receipt.
Difficult To Maintain the Customer Details of Package and
Payment Receipt in Register.
They Register Tour Package in the notebook.
Add advertisement in Local newspaper or Local Market.
Use Travelling Facility For the Limited Area or Person.

3. Need for New System

To Create Web Based Application For our Organization.

To Provide Search Facility For Customer.
To Generate Different Types of Reports.
To Provide the online Ticket Booking and online Payment
Facility For Customer.
To Provide package Details.
Customer Can Cancel the Booking then Return 15% Less
Deduct From the Amount.

 Services provided by Tour and travels System.

VIEW PACKAGE
SEARCH PACKAGE
BOOKING
CANCLE BOOKING
ONLINE PAYMENT

4. Function Specification
Modules that will be there in the projects are :

Customer:
- Registration(Login)
- View package
- Search package
- Booking
- Give Payment
- booking Cancellation
- Give Feedback

Admin:

- registration(Login)
- Manage User
- Manage Tour-package
- Manage Ticket Booking
- Manage Payment
- View Cancellation
-View feedback

Visitor:
- View site
- Give feedback

TRAVELER :- Registration
-Login
-manage tour
- Manage tour package cost
- Manage Bus(travels)

User Specification
Admin:
- admin can manage the user and receive package from traveler & package
management.

Traveler:
- Traveler create the package and give to admin.

Customer:
- customer can view package and booking.

Visitor:
- Visitor view side and give feedback.

5. Hardware & Software Specification

Hardware Specification :
Server Side:
Processor

2.0 GHZ

RAM

2 GB

Hard Disk

30 GB free space

Client Side:
Processor

1.0 GHZ

RAM

512 MB

Hard Disk

2 GB free space

Software Specification :
Server Side:
Operating System

Window Server 2008 or any

compatible operating system.

Runtime Environment

.Net Framework 4.0

Web Server

IIS 7.0

Front End

Microsoft Asp.Net 2010 with c#

Back End
Other Tools

SQL server 2008

Adobe Photoshop,MS office,
Crystal Report 9.0

Client Side:
Operating System

Window XP or any compatible os.

Web Browser

Internet Explorer 6.0 or any

compatible web browser.

6. System
flowchart

7. Timeline Chart

8. E-R Diagram

9. UML Diagram
9.1 Use case Diagram

9.2 Activity Diagram

9.3 Class Diagram

9.4 Sequence Diagram

9.5 Collaboration Diagram

10. Data Dictionary

1.Table Name: Login_mst
Description: To store the admin, customer, Traveler Login
Details
Primary Key: User Name
DataTyp
e
Constraint Description

Sr.
no

Name

Username

Varchar(10) Primary Key

User_Type

Varchar(10)

Not null

To store the
username
To store user
type
like admin,
customer,travel
er
etc.

Password

nvarchar(10

Not null

To store the

)
password

2. Table Name: AgeRegistration_mst

Description: To store Agent Personal Information.
Primary Key: Company_name

Sr.
no
1

Constrain
Field Name Data Type t
Description
Name

Varchar(50)

Company_Nam
e
Varchar(50)

Not null

To store the Name of

agent.

Primary Key

To store Company
Name.

Address

Varchar(50)

Not null

To store address.

City

Varchar(50)

Not null

To store city.

Not null

To store Agent zip

code.

Zip_code

Numeric(18,0)

Country

Varchar(50)

Not null

To store country.

Mobile no

Numeric(18,0
)

Not null

To store mobile
number.

Email_id

Nvarchar(30)

Not null

To store the Email id.

Comment

Varchar(50)

Not null

To store Comment.

3.Table Name:
AgePackage_Management
Description: To store Agent
Package Detail.
Primary Key: Tour_id

Sr .
no

Field Name

Constrain
Data Type
t

Agent_Name

Numeric(18,0
Agent_mobile
)
Not Null

Varchar(50)

Company_Nam
e
Varchar(50)

Not Null

Not Null

Description

To Store Agent
Name.
To Store Mobile
number.
To Store company
Name.

Tour_id

Package_type

Numeric(18,0
)
Primary
Key
Varchar(50)

Not null

To Store Tour id.

To store Package
type
like royal, Holiday.

Sr .
no
6

Field Name Data Type

Category

Varchar(50)

Constraint Description

Not null

To store tour
Catrgory.

Not null

To store the tour

place.

Tour_place

Varchar(50)

Days

Numeric(18,0) Not null

To store tour days.

Numeric(18,0) Not null

To store tour
amount.

Amount

4. Table Name: Booking_mst

Description: it can store Booking Detail.
Primary Key: Booking_id

Sr .
no
1

Field
Name

Booking_id

Data Type

Constraint

Description

Integer

Primary Key

To Store Booking id

Traveler_ name

Varchar (50)

Not null

To store Booking
traveler name

Package_id

Integer

Not null

To Store Package id

Package_name

Varchar(20)

Not null

To store package

name.

Create Date

Update Date

Date Time

Date Time

Not null

Create date of
record.

Not null

Update date of
record.

5. Table Name: category_master

Description: To store travels category Detail.
Primary Key: c_id
Sr . Field Name Data Type
no

C_id

Package_typ
e
Varchar(10)

category

Integer

Varchar(20)

Constraint

Description

Primary key

To store category
id.

Not null

To store the
package
type. Like holiday

Not null

To store category
like
royal, delux etc.

6. Table Name:
country_master Description:
To store country Detail.
Primary Key: country_id

Sr .
no
1

Field Name Data Type Constraint Description

Country_id

Integer

Primary Key To store the country id.

country

Varchar(10
)
Not null

To store the country

name.

7. Table Name: AdmPackage_management

description: it store the Package Detail Like type, days,
amount etc.
Primary Key: id
Sr.no Field Name

Id

Package Type

Category

Data
Type

constrain
t

Numeric(18,0
)
Primary Key

Varchar(30)

Varchar(15)

Description

To store Package id.

Not null

To store Package Type

like
Holiday, Royal etc.

Not null

To store Package
Category
like Group tour,

Tour_Place

Varchar(15)

Not null

adventure
tour etc.
To store Tour Place
name.

Days

Amount

Nchar (10)

Varchar(20)

Not null

Not null

To store tour package

Days.
To store Amount of
Tour
Packages.

8.Table Name: Feedback

Description: to store the feedback details.
Field
Name

Data Type

Constraint

Description

Name

Integer

Not null

To store name.

Emailid

Varchar(30)

Not null

To store email id.

Contact_no

Numeric(10)

Not null

To store contact no.

Not null

To store feedback
status.

Sr.
No

Feedback

Varchar(30)

11. Input Design

HOME PAGE

Description: Home page of Tour and Travel Management system.

REGISTRATION

Description: Registration Page for Agent.

TOUR PACKAGES

Description: Details of available Tour Packages.

BOOKING

Description: Booking Page to create Booking For Customer.

ADMIN LOGIN

Description: Admin Login Page admin login hear.

ADMIN HOME

Description: Home Page For Admin.

PACKAGE MANAGEMENT

Description: Admin Manage Package Management .

PACKAGE MANAGEMENT

Description: Admin Package Management information .

VIEW FEEDBACK

Description: Admin can view Customer and traveller Feedback.

CATEGORY

Description: Admin can add and view package category.

VIEW BOOKING INFO

Description: Admin Show customer Booking Details.

AGENT LOGIN

Description: Agent Login Page.

AGENT HOMEPAGE

Description: Home Page For Agent.

PACKAGE MANAGEMENT

Description: Agent manage the package Management.

PACKAGE MANAGEMENT

Description: Agent view package information.

FEEDBACK

Description: Customer and Visitor Give Feedback.

13.Testing
Sr No.

Test case

Expected

Actual

Pass/Fail

1.

Admin login case

Is admin Provided true username &

password for login?

Successfully login

Pass

2.

Invalid username/password case

Is username and password wrong then

error message

Error message

Fail

3.

View page case

Is requested page available?

Successfully view that page

Pass

4.

Test field

All information must be input

All information must be input

Pass

5.

Registration

Enter null in mandatory fields

It will show message that enter the

data.

Pass

Enter incorrect data

It will show message that enter the

correct data

Pass

6.

User login case

Is User provided true user name &

password for login?

Successfully login

Pass

7.

Invalid username/password case

Is username and password wrong then

error message

Error message

Fail

8.

View page case

Is requested page available?

Successfully view that page

Pass

9.

10.

Validation Test Cases

Manage Profile

Mandatory field should

not be blank

You have to enter some

value into mandatory
fields

Pass

The field value must have

the predefined range

Only 10 number are

enter in the field

Pass

A predefines format
should be follow

Check the proper

format of email-id

Pass

User can edit info of the

profile

The Message will be

Pass
displayed Profile edit
successfully.

14. POST
REVIEW

IMPLEMENTATION

After the system implemented and conversion is

completed, a review of system is usually
conducted by users and analyst this is called post
implementation review.
The most fundamental concern post
implementation review is determining the system
has met its objective, that is analyst want to know
if the performance level of the system has
improved and if the system is producing the result
intended.

 If neither is happening, one may question

whether the system can be considered
successful.
By using current system, all the requirements of
all users are fulfilled.

15. FUTURE ENHANCEMENT

In future we will give facility of online donation.

We will include more functionality as per user requirement.
Not a single website is ever consider as complete forever firstly because
there is always something new requirement also are growing day by day.
We want to improved our home page, as it is the main thing which
attracts all users.

16. BIBLIOGRAGHY
BOOKS :ASP.NET 3.5 BLACK BOOK
By: Kogent Solution Inc. dreamtech
PLATINUM EDITION
The Complete Reference ASP.NET
By: MACKDONALD MELTHEW(TMH)
3. System Analysis and Design Software Application
By: Brian Siler and Jeff Spots

WEB SITES :www.Google.com

www.Codeguru.com
www.Saveearth.org
www.Saveourearth.co.uk