PROJECT SYNOPSIS

STUDENT DETAILS :

1. Name of the Program : Travel Management System

2. Name of the Student : Divya m. Bhuva

3. Roll Number : 1302014392

4. Session & Year : MCA 6th sem 2014

PROJECT DETAILS :

6. Title of the Project : Travel Management System

7. Problem Statement :

The project has minor limitations as compared to its effectiveness. As it is fulfilling the
requirements of end user, the limitations are negligible.

The limitations of the project are as follows:

The tour package and hotel detail management functionality in Travel Management System is
fully controlled by administrator. So administrator must be aware of all the factors that may
affect the system.
The Bus booking can only be cancelled within 12 hours.

8. Methodology to be used :

Several Meetings Conducted :

We conducted several meetings amongst ourselves and discussed on various aspects of the
system and collected Information about the proposed system to be developed by us. By
analyzing the workflow, we got a proper understanding of the requirements.
Meetings were conducted as and when necessary to gather requirements. We followed the
basic approach for requirements gathering.

Information Exchange :
 Communicating within ourselves exposed us to the basic functionality to be executed by the
system, so we got aware of our target to be met within the predefined deadline.
We set the milestones and baselines so that we could proceed with the system development
on schedule.

Understanding The Concept :

Direct communication through meetings introduced us to the current scenario and provided
us with the basic guidelines on which our system would be developed.
Free flow of ideas made us understand the benefits of our system. Our motto was to develop
a quality product so we laid emphasis on Quality Control right from when we understood the
concept.
Document Prototype :
All this discussions were documented for the future access. During the meetings itself, we
note important things discussed on paper. After understanding the reason why we are
developing the Site and how our Site would tackle problems, we prepared a document
prototype. The document gave us an idea about the workflow of our site. In brief, this
document guided us to develop the system in right way and correct us if anytime we stayed
away from our goals.
Requirement Analysis
Requirement analysis involves studying the workflow of the proposed
system.
The process of requirement analysis is carried out in three steps
1. Requirement anticipation
2. Requirement investigation
3. Requirement specification

1. Requirement Anticipation
Requirement anticipation is very important part of system designing. It is to
predict the future requirements based on the previous experience of user aptitude.
We have anticipated the requirements by careful analysis.
We have played an active role in the analysis of the website. Thus, most of the
requirements were judged well in advance.
A proper assessment was done regarding the possible futures of this site.

2. Requirement Investigation
 Requirement investigation is the actual study of the system. It involves an
accurate study of what all aspects your software would cover. In our case as we were
developing site, it covered answers to questions like:
What is the basic functionality of this Website?
How you can establish communication?
How automated do you want the application to be?
What kind of functionalities is to be developed to make system easy to use on
both client and admin side?
How can we build attractive site so that more and more users can use this
web site?
3. Requirement Specification
The information gathered during the system study was analyzed to
determine the requirement specifications. Based on the issues governing the system,
requirements in non-technical terms formulated.
We need to develop rough prototype to check the basic functionality of the
site.
If the major modules are not working properly then the site might not satisfy
the user.
Interaction between the operator and site must be fast and reliable.
As we have decided to develop a new system now it is time to determine the
new requirements for the new system. As the user is the most important part of any
system it is required to find the users requirements to develop a user-friendly
system rather than having to develop a developer friendly system.
Feasibility of Web based ERP System
The feasibility of our project has been judged on the basis of time, technology,
resources available and project length.
Time :
This project takes 4 Months to be completed and we have enough time to
build this system, so as far as the time is concerned this project is feasible.
Technology :
This project is built on ASP.Net with VB in Visual Studio 2008.Therefore
the technical risk is negligible, so problem is feasible.
 Resources :
We need good knowledgeable software engineers and practitioners. We
need Internet Network connection, Internet Information Services, Visual
Studio 2008, and SQL Server 2005. Also proper development tool is
needed to prepare documentation.
We have all the resources in the desired amount.
Project Size :
The Project size might be around 4000 LOC. This is just the rough
assumption because we dont have any basis of the past projects.
Thus the project overall feasibility is normal and therefore we have undertaken this project

Hardware Requirement:

Processor : Intel Pentium 4 CPU 2.40 GHz

Ram : 2 GB of RAM

HDD : 80 GB.

Printer : Laser Printer.

Software Requirement:

Operating System : Windows XP

Front-End : Microsoft Visual Studio 2010(Asp.Net with)

Back-End :Sql Server 2005

10. Tools and Techniques to be used for data analysis :

Registration: Any visitor can become a registered customer by registration process.

Login: Any registered customer or administrator can login to their account by this.

Password Management: The registered customer can change or recover their password.
 Select Route: It will show the details of available Route.

Select bus for booking: It will show the details of available bus.

Manage Selection: Booking/ Cancellation in registered customer selection of route or bus will
done.

Administrator login:Addition/ updation/ deletion of Route details and bus will done by the
administrator after the login.

GUIDE DETAILS :

1. Name of Proposed Guide : mr. sandip singh jodan

2. Guide registration No. (If available) : ITMH0039

3. Qualification : MCA

4. Total Experience : 4 YEARS

7. E mail id : jodansandip08@gmail.com

8. Contact No. : 9021881471

I Ms. Heena gajera hereby confirm willingness to guide Ms. Divya m bhuva
Rollno : 1302014392 , prabhat Infosys ltd. Whose project title is Blood Bank Management
System during the summer session os internal assessment marks to the university.

I hereby declare there project synopsis is an original work carried by me

and university of fulfillment of any course of study.

Place :
Date: