You are on page 1of 10
INSTITUTE FOR ADVANCED COMPUTING AND SOFTWARE DEVELOPMENT AKURDI, PUNE SRS ON “TOURS AND TRAVELS” DAC-Aug-2016 Submitted
INSTITUTE FOR ADVANCED COMPUTING AND SOFTWARE DEVELOPMENT AKURDI, PUNE SRS ON “TOURS AND TRAVELS” DAC-Aug-2016 Submitted

INSTITUTE FOR ADVANCED COMPUTING AND SOFTWARE DEVELOPMENT AKURDI, PUNE

SRS ON

“TOURS AND TRAVELS”

DAC-Aug-2016

Submitted By :

Group No:G-046

Honey Alwani(1003)

Palak Elhance(1061)

Mr. Dhananjay N. Patil

Course Coordinator

Mr. Mahendra Waghmare

Project Guide

Table of Contents List of Figures 2 1.0. Introduction 1

Table of Contents

1

  • 1.1. Purpose.................................................................................................3

  • 1.2. Scope of Project......................................................................................3

  • 1.3. Glossary................................................................................................3

  • 1.4. References.............................................................................................4

  • 1.5. Overview of Document............................................................................4

2.0.Overall Description

  • 2.1 System Environment...............................................................................

  • 2.2 Functional Requirements Specification.......................................................

  • 2.3 User Characteristics...............................................................................5

  • 2.4 Non-Functional Requirements.................................................................5

  • 3.0. Requirements Specification

6

  • 3.1 External Interface Requirements.............................................................6

  • 3.2 Functional Requirements..........................................................................

3.2.1 Search Article.........................................................................................

  • 3.2.2 Communicate....................................................................................

  • 3.2.3 Add Author.......................................................................................

  • 3.2.4 Add Reviewer....................................................................................

  • 3.2.5 Update Person..................................................................................

  • 3.2.6 Update Article Status.........................................................................

  • 3.2.7 Enter Communication.........................................................................

  • 3.2.8 Assign Reviewer................................................................................

  • 3.2.9 Check Status....................................................................................

    • 3.2.10 Send Communication......................................................................

    • 3.2.11 Publish Article................................................................................

    • 3.2.12 Remove Article...............................................................................

  • 3.3 Detailed Non-Functional Requirements.....................................................6

    • 3.3.1 Logical Structure of the Data.............................................................6

    • 3.3.2 Security...........................................................................................

Index

List of Figures

Figure 1 – Use case..........................................................................................7 Figure 2 - DFD...............................................................................................23 Figure 3 - ERD...............................................................................................25

  • 1.1. Purpose

Introduction

The objective of the project is to develop a system that automates the processes and activities of a travel and tourism agency. The purpose is to design a system using which the user/visitor will be able to view various locations and places, and can read the information of the locations and details like what are those places famous or special for etc. and can book the tickets for the place where the user wishes to visit. He/she can also view various packages that are available and can book them through agents. Moreover the user can also have a guide being booked for the place that he/she will be visiting. Also the user can form a group and chat with other users. User can also ask queries and give their feedback.

  • 1.2. Scope of Project

Initial functional requirements will be: -

Secure registration and profile management facilities for Customers

Creating a wish list depending upon the likes and dislikes so that user can be suggested places as per his/her likings.

Adequate payment mechanism and gateway for all popular credit cards, cheques and other relevant payment options, as available from time to time.

Browsing through the locations the user will be able to find the route that would be available to reach the desired location that he has selected and the mode of transportation option along with the guide option will also be provided to the user.

Appropriate mechanism optios have been used so that the user can give his wish list and is able to search various locations, guide and packages accordingly.

Also the feedback option is provided, so that user can give feedback for the locations and facilities which they have chosen or are provided with. Also the facility of rating is given for the locations visited by the user which can be viewed by visitors and other users.

Also a profile of each user is maintained where there would be places visited by the user, his/her likes and kind of places preferred and have been visited and also chat option would be available.

The visitor will be able to view the homepage and various locations and the information provided for that location.

Initial non functional requirements will be: -

Secure access of user’s details. 24 X 7 availability. Better UI design so that user can use website easily. Advertisements of packages and various preferred and popular locations where it will effectively catch the users attention and as a source of revenue. In addition to the above mentioned points, due to the highly evolving nature of the project, the

following are planned to be delivered if deemed necessary:

More payment gateways.

Dynamic price model by which prices can be changed based on various transportation cost and other expenses.

Term

Definition

Route

Describing various routes that will be available for the user to reach the destination easily and all the details of various stops, hotels, restaurants

during the route and transportation facility.

Administrator

Database Management, Contact and authorizing the users , View all

details, Advertising the locations.

Database

Collection of all the information monitored by this system.

Field

A cell within a form.

User

A member of the website listed in the users database and having a

profile built.

Visitor

Anyone visiting the site to search locations and read their details and

reviews of the users.

feedback

Suggestions and reviews of the user about the website, locations visited

by the user, and transportation facility

query

Questions asked by users regarding various bookings, guide, locations

and transportation

Software

A document that completely describes all of the functions of a

Requirements

proposed system and the constraints under which it must operate. For

Specification

example, this document.

staff

Handling all the details of users and visitors, authorizing user and

managing various reports.

1.4. References

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications. IEEE Computer Society, 1998.

1.5. Overview of Document

The next chapter, the Overall Description section, of this document gives an overview of the functionality of the website. It describes the informal requirements and is used to establish a context for the technical requirements specification in the next chapter.

The third chapter, Requirements Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the website.

Both sections of the document describe the same website in its entirety, but are intended for different audiences and thus use different language.

2.3

User Characteristics

The User is expected to be Internet literate and be able to use a search engine. The main screen of the Tours and Travels Website will have the search function for searching of various locations and a link to view the user profile and change his/her details would be provided.

The user will be able to book guide as well as flight, trains, bus or car as per his need to reach the destination.

He user will also be able to give feedback ,ask queries, read information about locations and chat with other users and can also form a chat group.

  • 2.4 Non-Functional Requirements

The Tours and Travels website will be on a server with high speed Internet capability. The website developed here assumes the use of a tool such as Tomcat for connection between the Web pages and the database. The speed of the User’s connection will depend on the hardware used rather than characteristics of this system. The Tours and Travels will run on the staff PC and will contain an Oracle database. Oracle is already installed on this computer and is a Windows operating system.

3.0.

Requirements Specification

  • 3.1 External Interface Requirements

The only link to an external system is the link to the Tours And Travels Database to verify the user is authorized or not. As soon as the user is authorized a profile of his various details entered during registration would be reflected into it along with his/her profile picture. Also the user would be able to then chat with other users and see the places visited by other users and there reviews.

  • 3.2 Detailed Non-Functional Requirements

    • 3.2.1 Logical Structure of the Data The logical structure of the data to be stored in the database is given below.

    • 1.2.2 .Functional Requirement: Number of Modules After careful analysis the system has been identified to have the following modules: 1) Administrator module 2) Travels module 3) Routes module 4) Reservations module 5) Testimonials module.

      • 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, restaurants etc.

  • 2. TRAVELS MODULE:

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

  • 3. ROUTES MODULE:

This module provides information related to various routes connecting sources and destinations. For each route, information such as source, destination, fare, reservation details,

pick up points etc. are provides. Only administrator can add, delete, edit and manage the data. Users can only view the information.

  • 4. 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.

  • 5. 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.

3.2.3 Hardware Requirement:

HARDWARE REQUIREMENT

PROCESSOR

:

Pentium IV & Above.

RAM

:

1 GB & Above.

HARD DISC SPACE :

40 GB & above.

MONITOR

:

Color

SOFTWARE REQUIRMENT:

Operating System

: Windows

Technology

: Java and J2EE

Web Technologies

: Html, JavaScript, CSS

IDE

: My Eclipse

Web Server

: Tomcat

Database

: MySql5.0

Java Version

: J2SDK1.5

Software Life Cycle Model:

In order to make this Project we are going to use Classic LIFE CYCLE MODEL .Classic life cycle model is also known as WATER FALL MODEL. The life cycle model demands a Systematic sequential approach to software development that begins at the system level and progress through analysis design coding, testing and maintenance.

Java Version : J2SDK1.5 Software Life Cycle Model : In order to make this Project we

The Classic Life Cycle Model

The waterfall model is sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception initiation, Analysis, Design (validation), construction. Testing and maintained.

This is the most crucial phase for the whole project, here project team along with the customer makes a detailed list of user requirements. The project team chalks out the functionality and limitations(if there are any) of the software they are developing, in detail. The document which contains all this information is called SRS, and it clearly and unambiguously indicates the requirements. A small amount of top-level analysis and design is also documented. This document is verified and endorsed by the customer before starting the project. SRS serves as the input for further phases.

2) Software requirement Analysis: =

Using SRS as input, system design is done. System design included designing of software and hardware i.e. functionality of hardware and software is separated-out. After separation design of

software modules(see

what is modularity) is done.The design process translates requirements into

representation of the software that can be assessed for quality before generation of code begins. At the same time test plan is prepared, test plan describes the various tests which will be carried out on

the system after completion of development.

3) Design:

Software design is actually a multi-step process that focuses on distinct attributes of the program data structure, software architecture, procedural detail and interface of the software that can be assessed or quality before coding begins .Like requirement the design is documented and becomes part of the software.

4) Coding:

The design must be translated into a machine readable form. The coding step performs this task. If design is programmed in a detailed manner, coding can be accomplished mechanically.

5) Testing:

Now the units of the software are integrated together and a system is built. So we have a complete

software at hand which is tested to check if it meets the

the customer. Testing is done, as per the steps defined in the test plan, to ensure defined input

produces actual results which agree with the required results. A test report is generated which contains test results.

6) Maintenance:

Software will undoubtedly undergo change after it is Delivered to the customer .Change will occur because errors have been encountered because the software must be able adopted to accommodate changes in its external environment because the customer requires functional or performance enhancement enhancements. The classic life cycle is the oldest and most widely used paradigm or software engineering

Conclusion:

Using this project “Tours And Travels” the user can easily book tickets and find out information about various locations.