1.

INTRODUCTION
1.1. OVERVIEW OF THE PROJECT

“Sai tours” The tourism management is useful for the customer registration. It provides the

facility to the customers or the users to have complete information about the Tours and Travels at

one place. This project is very dynamic and very easy to understand, the interface of the website is

very easy and anybody can easily work in our project, this project can provide all the description

about the packages and tours such as tour images, description and some important information

about the tours.

The tours and travels website is also very useful because the customer don’t have to visit to

booking office, he can easily book his ticket via this website and he can also pay the payment with

two popular way of payment that is paypal and the credit card, so he can book ticket without any

kind of harassment.

A brief description are provided into the documentation in technology used for front-end

and back-end instruction.

All the covered commitments and provided utilities are described in the proposed system.

MODULE IS:

 Administrator module,

 tour package module,

 travels module,

 passenger module,

 booking modules,

1
MODULE DESCRIPTION:

1) Employee 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, bookings, etc.

2) Tour package module

This module provides from customer to user related functionality.
Customer decides package details and no of days, date of traveling, no of persons, hotels and
prize and discounts.

User manages and enters the package details of travel from customers interest and
need. Only administrator can add, delete, edit and manage the data. Users can only view the
information

3) Travel module:

This module provides the details of various travel agencies. A user can select the
appropriate agency depending on convenience and accessibility.

This module provides information related to the places of the customer and the
available drivers and vehicles of customer need to reach the destinations and the vehicle no
and drivers name, drivers phone no and address. Where these details will be added to both
customer and admin for security purpose and give a trusted service for the tour.

User manages and enters the package details of travel from customers interest and
need. Only administrator can add, delete, edit and manage the data. Users can only view the
information

2
4) passenger details:

This module provides and stores the information of the passenger who is
booking the tour package. Information such as passenger name, passenger phone no, address,
tour packages that the customer booked, tour date and prices of the tour.

User manages and enters the package details of travel from customers interest and
need. Only administrator can add, delete, edit and manage the data. Users can only view the
information

5) booking 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.2 ORGANIZATION PROFILE

“Sai tours” was started in the year 1999 as a travels concern in pollachi. It was originally set
up provide customer services for customer all over the world.

They deal with all kinds of tour booking with different states. In this concern employee
undergoes an extensive interview process that ensure the right character attributes with
commitment and a passion of success. It enhance of the industry knowledge and technical skill to
ensure excellent performance. 10 employees are working, salary starts from 5000 to 7000 and it
includes provident fund and medical allowances.

Formula to success

 Build proprietary, branded solutions leveraging the company’s core products and services.
 Provide customer with outstanding service.
 Deliver high quality solutions that meet the customer’ needs.

2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

3
 The records in the tourism management are maintained partially automated in earlier
system, and some of the easy maintained process been not added to be correct in all details of
the such as adding and updating employee details, tour package details, travel details and etc…

Employee and customer details can be difficult to respond to as information is different

places and may even require that find the right person being able to when mistakes are made or
changes or corrections are needed often a manual transaction be completely redone rather than
just updated.

With manual system the level of service is dependent on individuals and the
requirement on management to run training continuously for staff to keep them motivate ensure
they are following the correct procedures.

2.1.1 DRAWBACKS OF EXISTING SYSTEM

 The process takes lot of time.

 Providing all information is not possible.
 It could not be assured for accuracy.
 Loss of data.
 Higher cost

2.2 PROPOSED SYSTEM

The proposed system is partially automated in most of the fields and details to store in
tourism management system. Through this system the user can easily add employee details,
tour package details, travel details, passenger details and booking details and those details can
be updated easily.

Tour & Travels will work to booking its services and packages by application.
There are several services and packages are available at the one place.
If the new user are visited the project and wants to book the tickets. So first they
have to register and then the user will able to book the tickets.
Some other functionality of that site is that register user will change, its login information,
Other module will also included as like the, travels, Package, Hotel e.t.c

4
2.2.1 ADVANTAGES OF THE PROPOSED SYSTEM

• Improve the relationship with the customers

• Improve the quality of the product
• Availability
• Better data Security
• Easy to navigate the system

2.3 SYSTEM SPECIFICATION

HARDWARE SPECIFICATION:

Processor : Intel core i3

RAM : 2 GB

Hard disk : 232 GB

Mouse : wireless Mouse

Keyboard : Standard Keyboard

Mother board : Generic PnP Moniter

SOFTWARE SPECIFICATION:

Operating system : Windows 7

Front End : VB. Net (2008)

Back End : Microsoft access database 2007

2.3.1 ABOUT THE SOFTWARE

VISUAL BASIC.NET

Visual basic .net has many new and improved languages features such as inheritance,
interfaces and overloading that make it a powerful object oriented programming language.

5
Other new language features in Visual basic .net include structured exception handling.
Customs, attributes and common language specification (CLS)compliance.

2.3.2FEATURES OF VISUAL BASIC.NET

Here are some features of visual basic .net,

• Visual basic.net, the latest version basic, includes many new features. The visual basic
.net supports interfaces but not implementation inheritance.
• Visual basic .net supports implementation inheritance, interfaces and overloading,
addition, Visual Basic.Net supports multithreading concept.
• Visual Basic.Net supports many new or improved object oriented programming
language features such as inheritance, overloading, the override keyword interfaces,
shared members and constructors.

MICROSOFT ACCESS DATABASE

MICROSOFT ACCESS administration tool and monitor and administrate databases,

user print and data. It is a data driven application. The MICROSOFT ACCESS database is a
open source, so we can contribute project as well. The benefits are,

• Free of cost
• No professional support
• Ideal for individual users/developers/students/business
having more time and money.
• Create a simple database and populate with a table.

3. SYSTEM DESIGN
3.1 DESIGN NOTATION

3.1.1 SYSTEM FLOW DIAGRAM

6
 user

login

Admin Tour Travel passanger Booking

package details details
details details details

Admin Tour travel Passenger Booking

database database database database database

process

Admin Tour Travel passanger Booking

report
report report report report

3.1.2 DATA FLOW DIAGRAM

7
Context level:

Tour package details

travel details employee details

Tourism

management system

passenger details Booking Details

Level 0:

admin tourism management system

login

8
Level 1:

admin sold sales

buys

Sales details

purchase

Purchase details

Level 2:
9
 admin login View
transaction

buys

Purchase Making delivery

product food

makes

Purchase
employee Employee
details
details

sales

Maintain sales sales stock

details available
e

sold

Maintain Customer Maintain

customer stock details
details

generate

report

3.1.3 ENTITY RELATIONSHIP DIAGRAM

E_id addr 10
 E_name I_id
p-id
Billamt
sal dob aamrt
amt
Produc Purchase
Employee cost
t
phno
desig qty
I_name
dor blood

Maintenc
e

S_id S_name

I_id
instock
Supplier k

Stock

cost item

qty
I_name

Balanc
e

I_name
name

Amt
Bill Sales qty

I_id
amt
date

phno

3.2 DESIGN PROCESS

11
3.2.1 INPUT DESIGN

The screen is designed for entering or viewing for performing the modification. The
screen is designed for user friendly and appropriate aim. In accurate input data is the most
common cause of errors in data processing. Errors found at the data entry can be controlled
by the proper input design. The input was designed with the following objectives.

 To produce a cost effective method.

 To get the highest level of accuracy.
 To ensure that the input is acceptable and understandable by the people who are using
it.

The screens for the proposed system are,

Login:

Login application takes username and password as input. The existence of username
and password is checked by the system and corresponding error messages are displayed.

Purchase:

A new product can be added to the database when it is purchased. It is added through
its purchase id and product id.

Sales:

It is used to add the details of the sold food based on sales id and food is that is
created from making of the food

Employee:

It is used to insert the details of the employee those who are working in the shop
through employee id.

Supplier:

It is used to insert the details of the supplier those who are supplier to the shop
through supplier id

3.2.2 OUTPUT DESIGN

12
 Computer output is the most important and direct source of information in the user.
Efficient, intelligible output design should improve the systems relationship with the user and
help in decision making. A major form of output is hard copy from printer. Output generally
refers to the information that is generated by the system.

The output design process involves,

 Identify system outputs and review logical requirements.

 Specify physical output requirements.
 As necessary, design any preprinted forms.
 Design, validate and test outputs using some combination of,
 Layout tools (hand sketches, spacing charts or CASE tools).
 Prototyping tools (spreadsheet, PC DBMS, 4GL).
 Code generating tools(report writer).

The main output of the system is,

Purchase report:

It includes the product id, purchase id, product name, quantity and amount of the
product.

Sales report:

It includes the details of the sold food such as food details form the making and
customer id and the amount of the product to be paid.

Employee report:

It displays the details of the employee such as employee id, name, desigination, salary
etc.

Stock report:

It is used to display the availability of the product quantity.

3.2.3 DATABASE DESIGN

13
 A database is a collection of inter-related data store with a minimum of redundancy to
serve many applications. It minimizes the artificiality embedded in using separate file. The
primary objectives are fast response time to inquire more information at low cost, control
redundancy, clarity and ease or use accuracy and fast recovery. The overall objective in the
development of a database is to treat and organizational resource and as an integrated whole.

Database Management System (DBMS) allows the data to be protected and organized
separately from other resources like hardware, software and programs. DBMS is a software
package, which contains components that are not frond in other data management packages.
The significance of DBMS is the separation of data as seen by the programs and data as
stored on the direct access storage devices, i.e. the difference between the logical and
physical data.

TABLES

Table Name: Pur

Primary key: P_id

Field name Data type Length Description

P_id int 02 Purchase id

Bill_no int 02 bill id

Cost int 10 Amount

I_id int 02 Item id

I_name Text 10 Item name

Quantity int 1 Supplier name

Table Name: Sup

primary key: S _id

14
Field name Data type Length Description

S_id int 10 - Supplier id

S_name text 10 supplier name

Cost int 10 Cost

Item text 10 Item name

Table Name: emp

Primary key: emp_id

Field name Data type Length Description

Eid Text 10 Employee id

Ename Text 20 Employee name

Sal int 10 salary

Add Text 50 Address

P_no Number 10 Phone number

Des Text 10 desigination

Dob int 06 Date of birth

Blood int 05 Blood group

Dor Text 10 Date of releave

Table Name: Sup

Primary key: Sup_id

15
Field name Data type Length Description

Sup_id Text 10 Date of making

Sup_name Text 10 Jewel id

Item Text 10 Jewel type

Cost Text 15 Jewel name

Quantity Number 10 quantity

Table Name: Sal

Primary key: s_id

Field name Data type Length Description

Name text 10 Costomer name

Phno int 10 Phone number

Date Date&time 10 Date time

I_id int 15 Item id

I_name Text 10 Item name

Qun Int 10 quantity

Price int 10 Item price

T_cost int 10 Total amount

4. SYSTEM TESTING AND IMPLEMENTATION

16
4.1 SYSTEM TESTING

System testing is done after integration testing is complete. System testing should test
functional and non-functional requirements of the software. Testing the software or software
application as a whole is referred to as System Testing of the software. System testing of the
application is done on complete application software to evaluate software’s overall
compliance with the business / functional / end-user requirements. The system testing comes
under the knowledge of the interior design.

Software testing is the process of executing the program with the sole interest of
finding an error. A good test is the one that has a high probability of finding the yet
undiscovered error. This enables users to detect errors and correct it without affecting any
other modules. Whenever the program was not executing the required result. Thus all the
modules are tested separately with test data. Errors are isolated and corrected. To check error
handling paths uncorrected data is entered and tested.

Functional Test

Functional test cases involved exercising the code with nominal input values for
which the expected results are known, as well as boundary values and special values, such as
logically related inputs, files of identical elements, and empty files.

Performance Test

It determines the amount of execution time spent in various parts of the unit, program
throughput, and response time and device utilization by the program unit.

Stress Test

Stress test is those test designed to intentionally break the unit. A great deal can be
learned about the strength and limitations of a program by examining the manner in which a
programmer in which a program unit breaks.

Unit test

17
 Unit testing refers testing of the all individual program. This is sometimes called as
program testing. This test should be carried out during programming stage in order to find the
errors in coding and logic for each program in each module. In this project, the user must fill
each field otherwise the user to enter the values.

Unit testing is conducted to verify the functional performance of each modular

component of the software. Unit testing focuses on the smallest unit of the software design
(i.e.), the module. The white-box testing techniques were heavily employed for unit testing.

Acceptance testing

Acceptance Testing is a level of the software testing where a system is tested for
acceptability. The purpose of this test is to evaluate the system’s compliance with the
business requirements and assess whether it is acceptable for delivery. Formal testing with
respect to user needs, requirements, and business processes conducted to determine whether
or not a system satisfies the acceptance criteria and to enable the user, customers or other
authorized entity to determine whether or not to accept the system.

Integration testing

Integration testing is the phase in software testing in which individual software

modules are combined and tested as a group. It occurs after unit testing and before validation
testing. Integration testing takes as its input modules that have been unit tested, groups them
in larger aggregates, applies tests defined in an integration test plan to those aggregates, and
delivers as its output the integrated system ready for system testing.

White box testing

White-box testing (also known as clear box testing, glass box testing) tests internal
structures or workings of a program, as opposed to the functionality exposed to the end user.
White-box testing tests internal structures or workings of a program, as opposed to the
functionality exposed to the end-user.

The tester chooses inputs to exercise paths through the code and determine the
appropriate outputs. It can test paths within a unit, paths between units during integration, and
between subsystems during a system level test.

18
 In this system, using white box testing methods, Test cases are derived, the guarantee
that all independent paths with in a module have been exercised at least once, exercise all
logical decision on their true and false sides, all loops are executed at their boundaries and
within their operational bounds, internal data structures are exercised to ensure their validity.

Black box testing

Black box testing, also called as behavior testing, focus on the functional
requirements of the software. This testing enables the software engineer to derive sets of
input conditions that will fully exercise all functional requirements for a program.

Black box testing attempts to find errors in the following categories

1. Incorrect or missing functions

2. Interface errors
3. Errors in data structures or external data base access
4. Behavior or performance errors
5. Initialization and termination error

By applying black box techniques in this system, a set of test cases that satisfy the
following criteria were been created: Test cases that reduce, by a count that is greater than
one, the number of additional test cases are designed to achieve reasonable testing. The test
cases that define the presence or absence of classes of error are included.

Validation Testing

Verification and validation (V&V) is the process of checking that a software system
meets specifications and that it fulfills its intended purpose. It may also be referred to
as software quality control. It is normally the responsibility of software testers as part of
the software development lifecycle.

Error Messages Are Displayed

 Whenever user tries to enter duplicate values

 Whenever user gives data in wrong format
 Whenever user enters invalid data

19
4.2 SYSTEM IMPLEMENTATION

Implementation is the realization of an application, or execution of a plan,

idea, model, design, specification, standard, algorithm, or policy. The implementation view of
software requirements presents the real world manifestation of processing function and
information structures. System implementation is the process of developing the system based
on the user requirement that has to be enforced in any system while development. Security
window prohibits unauthorized users entering the system. Implementation is the stage of the
project when the system design is turned into fully working system. This stage consists of
following steps.

 Testing the developed program with the sample data.

 Detecting and correction of internal errors.
 Testing the system to see if it meets the user requirements.
 Feeding the real time data.
 Making changes as desired by the user.
 Training user personal.

As software is used, the customer/user will recognize additional functions that will
provide benefit. Perceptive maintenance extends the software beyond its original function
requirements.

20
 5. CONCLUSION AND FUTURE ENHANCEMENT

5.1 CONCLUSION:

The project is entitled as “JEWELLERY SHOP MANAGEMENT SYSTEM” has

been successfully developed and integrated. This system provides a high reliability.

Since the earlier version have many difficulties for the customers, suppliers, purchase
and sales details maintenance of the administrator. The new version is developed which will
overcome these difficulties. The program convention followed in the development of this
package ensures early maintenance. The system is highly flexible and modifications can be
done with minimum effort.

The system was able to process and updates the database with more easily. It helped in
developing a total integrated system.

The successful completion of the system resulted in

 Accurate results for every calculation and no data lose.

 Elimination of manual process.
 Fast data processing compared to manual processing.
 Generation of all reports
5.2 FUTURE ENHANCEMENT

This application can be easily implemented under various situations. We can add new
features as and when we require. Reusability is possible as and when require in this
application. There is flexibility in all the modules. This software is extendable in ways that its
original developers may not expect.

21