Project Tarun

8/8/2019 Project Tarun

1/60

Uttar Pradesh Technical University, Lucknow, India

A Project Report on:

AIRLINES RESERVATION SYSTEM

S.P.M PROJECT LAB

I.T. DEPARTMENT

Session: 2009-10

SUBMITTED BY :

Rahul Dayal : (0713213039)

Saurabh : (0713213046)

Saurabh Singh : (0713213047)

Tarun Verma :(0713213055)

Ramakant :(2813213004)

SUBMITTED TO

Mr. PUNIT BANSAL

(I.T. DEPT.)


2/60

UNDER THE GUIDANCE OF

Mr Puneet Bansal

Department of Information Technology

Greater Noida Institute of Technology


3/60

CERTIFICATE

This is to certify that project On

Placement Office

Automation

In the partial fulfillment of the requirement for the

award of Bachelor of Technology (B.TECH.) degree in

Information technology, Uttar Pradesh TechnicalUniversity, Lucknow. It is the record of their own work

carried by them under our guidance and supervision in

the department during the academic session 2009-

2010.

Prof. Sanjay Katiyar

Head of Department

Department of

Information technology

Guided by:

Mr. Puneet Bansal

Lecturer

Department of

Information technology.


4/60

ACKNOWLEDGEMENT

Many have contributed to the successful preparation and completion of this text.

We would like to place on record our grateful thanks to each of them. First and

foremost we will forever be indebted to our guide Mr Puneet Bansal, Lecturer,

G.N.I.T, Greater Noida. He has been one of earliest motivators and from the very

beginning he has been the source of all kinds of assistance.

This acknowledgement will not be complete without the mention of our respect

Head of Department, Prof. Sanjay Katiyar and all the staff members of the

Department of Information Technology for their regular encouragement and all

those who helped us directly or indirectly in our endeavors.

And last but not the least we all would like to thank our parents and other family

members for their unparallel support and guidance.


5/60

CONTENTS

1. Acknowledgement

2. Title of the project

3. Introduction

4. Abstract

5. Problem statement

6. Objective

7. Methodology

8. Scope

9. Zero level DFD

10. Gantt chart

11. Role of team members

12. System specifications

13. References


6/60


7/60

INTRODUCTION

Now a days each person is busy in their business work

& dont want to waste time even a single minute. Therefore he is totally depends on internet which is

easy in use & fast.

Online reservation software provides the information

about the arrival & dispatch time of flight with its date

& day , by which an individual can get informationalthough can reserve their ticket for particular flight .

.


8/60

Project Category

The product is a web application that is to be

implemented on local Internet. The advantage ofdeveloping the product as web application is that it need

not be installed on individual machines of clients. A web

application is installed on the server and client access it

using a browser.

The product comes under the category of MIS as it

captures information related to different operations of an

educational institution and generates various reports

which help the management in decision making.


9/60

ABSTRACT

Gives a clear view to the customer about the

current scenario of airlines flight .

Gives the details of the dispatch & arrival of the

flight.

Provide confirmation of ticket.

Ticket can be cancelled within a given time


10/60

PROBLEM STATEMENT

Updation of information takes much time.

Large maintenance is required to handle the database .

Format is difficult and could not be easily understood.

Processing slow.


11/60

OBJECTIVES

Objective of the AIRLINES RESERVATION SYSTEM can besummarized as:

To give a clear view to the customer about

the current scenario of airlines information.

Provide information of dispatch & arrival of

flights.

To make effortless updates & Managingdatabase.

To confirmation of ticket online .


12/60

THE PROPOSED SYSTEM

The proposed system is a computerized one. This has greater accuracy and efficiency. This takes

only limited time in finding the details. I did our best efforts to remove the problems occurring in

the Existing system .The main features in the existing system are given below:

Advantages of the proposed system are:

Very fast & easy access to the data.

The new system is more users friendly, reliable and flexible.

Timely Report generation.

Full automation of entire system.

Reduced paper work.

Less error prone.

Requirements From the System


13/60

Completeness: It was felt that all data should be stored

systematically & completely, so that the corresponding information

can be retrieved easily & with minimum efforts.

Efficiency: Controlled in terms of efficiency, data consistency &

data integrity.

Security: The new system developed should be secure enough so

that only the authorized people can access the services & the data

existing in the system can not be changed by any unauthorized

people.

Convenient Representation: Representation of the data should be

convenient so that any person can understand & access the data

easily.

Consistency of Results: Results that come after selecting the data

should be consistent.


14/60

SYSTEM DEVELOPMENT LIFE CYCLE

PHASES:

Initiation Phase

This activity requires a precise definition of problem in user terms. Initiation of a

system (or project) begins when a business need or opportunity is identified. In this

phase following factors are taken care of:

Is the problem solvable?

Which is the best strategy out of chosen one?

System Concept Development Phase

Once a business need is approved, the approaches for accomplishing the concept are

reviewed for feasibility and appropriateness. This part of phase requires gathering of

entire information about the working of work assigned. This also covers the

requirement of customers and then document properly.

Planning Phase

This phase is to completely understand the requirement of customer and then to

document them properly. This activity basically concerned with that of system such

as:

What are of the inputs of system?

What is the process required?

What are the outputs expected?


15/60

Requirements Analysis Phase

This phase requires gathering of entire information of the working of work

assigned. If the product involves developing new software for which no working

model exists then the information is collected through questionnaire.

Design Phase

In this phase the requirements specification are transformed into a structure that is

suitable for the implementation in some programming language.

Development Phase

The detailed specifications produced during the design phase are translated into

hardware, communications and executable software. Software shall be unit tested,

integrated, and retested in a systematic manner. Hardware is assembled and tested.

Integration and Test Phase

This is very important phase. It contributes to more satisfied users, lower

maintenance cost, and more accurate results. It involves testing of whole software.

The various components of the system are integrated and systematically tested. The

user tests the system to ensure that the functional requirements, as defined in the

functional requirements document, are satisfied by the developed or modified

system.

Implementation Phase

The system or system modifications are installed and made operational in a

production environment. The phase is initiated after the system has been tested and

accepted by the user. This phase continues until the system is in accordance with the

user requirements.

Operations and Maintenance Phase


16/60

The system is monitored for continued performance in accordance with user

requirements, and needed system modifications are incorporated. The operational

system is periodically assessed through In-Process Reviews to determine how the

system can be made more efficient and effective.

SDLC OBJECTIVES

This guide was developed to disseminate proven practices to system developers, project

managers, program/account analysts and system owners/users throughout the DOJ.

The specific objectives expected include the following:

To reduce the risk of project failure

To consider system and data requirements throughout the entire life of the system

To identify technical and management issues early

To disclose all life cycle costs to guide business decisions

To foster realistic expectations of what the systems will and will not provide.

To provide information to better balance programmatic, technical, management, and cost

aspects of proposed system development or modification

Key Principles

This guidance document refines traditional information system life cycle management

approaches to reflect the principles outlined in the following subsections. These are the

foundations for life cycle management.

Life Cycle Management should be used to ensure a Structured Approach to

Information Systems Development, Maintenance, and Operation.

It should support the use of an Integrated Product Team.

Each System Project must have a Program Sponsor.

A Single Project Manager must be selected for Each System Project.

A Comprehensive Project Management Plan is required for Each System Project.


17/60

Specific Individuals must be assigned to Perform Key Roles throughout the Life

Cycle.

SYSTEM REQUIREMENT ANALYSIS

At the heart of system analysis is a detailed understanding of all important facets of business area

under investigation. (For this reason, the process of acquiring this is often termed the detailed

investigation) Analyst, working closely with the employees and managers, must study the business

process to answer

These key questions:

What is being done?

How is it being done?

How frequent does it occur?

How great is the volume of transaction or decisions?

How well is the task being performed?

Does a problem exist?

If a problem exists, how serious is it?

If a problem exists, what is the underlying cause?

This may be divided into following areas of concern:

Product Definition


18/60

Feasibility Analysis

Project Plan

Team Structure

Development Schedule

Programming Languages and Development Tools

PRODUCT DEFINITION

In starting, the entire system was manual. So, there were lots of drawbacks of this system. It was

time consuming if we want to view details of anything. Also, there was lot of redundancy in records.

If it is required to update any record, then all the records & files maintained manually need to be

searched which took lot of time.

But, now to make it reliable, efficient & easily updatable, this new system has been developed. If

this system is applied, it will be very easy for the Peoples to use different government or private

services on the basis of their unique Id only. .

An analyst is responsible for performing following tasks:

Gathered all facts about the present system from the employees.

Studied strength and weakness of the current system.

Determined what must be done to solve the problem.

Prepared a functional specifications document.


19/60

In order to reduce the time, there is a need for computerized system that cans retrieve data, insert

data, update existing data or delete existing data. These modules are developed with the aim of

reducing time, reducing manpower, reducing cost so that the records can be easily maintained. The

volume of work and complexity are increasing year by year. This system reduces complexity and

workload.

FEASIBILITY ANALYSIS

A feasibility study is conducted to select the best system that meets performancerequirement. This entails an identification description, an evaluation of candidate system

and the selection of best system for the job. The system required performance is defined by

a statement of constraints, the identification of specific system objective and a description

of outputs. Once scope has been identified, the task of Feasibility Analysis gets started.

Feasibility Analysis works on four dimensions:

Technical Feasibility

Financial Feasibility

Timely Feasibility

Operational Feasibility

I also investigated & found that system is feasible in all terms. The Feasibility Analysis for

this system is explained as under:


20/60

TECHNICAL FEASIBILITY: It is a measure of the practically specific technical solution and the

availability of technical resources and expertise..

Hardware used in this project are- P4 processor 2.4GHz, 512 MB RAM, 80 GB hard disk, floppy

drive. This hardware is already available on almost all the existing computer system. The software

likes SQL Server 2000, Web Services, ADO.Net, C#, .Net Framework and operating system

WINDOWS-XP used was already installed on the existing computer system. So no additional

hardware and software were required to purchase and it is technically feasible. The organization is

equipped with enough computers so that it is easier for updating. Hence the organization has no

technical difficulty in adding this system.

FINANCIAL FEASIBILITY: It looks at the financial aspects of the project. It determines whether

the management has enough resources and budget to invest in the proposed system and the

estimated time for the recovery of cost incurred. It also determines whether it is worthwhile to invest

the money in the proposed project. Financial feasibility is determined by the means of cost benefit

analysis. The proposed system is economically feasible because the cost involved in purchasing the

hardware and the software are within approachable.

TIMELY FEASIBILITY: This factor basically defines the feasibility in terms that will the project

time to market beat competition. Time is not far when just by clicking, you can view details. This

system is feasible according to time that has been given. It is easy to get details of anything within

fraction of seconds.

OPERATIONAL FEASIBILITY: The system resources are minimal. Thus, any organization with

field of Software Development Process possesses such minimal requirements. The system will be

used if it is developed well.

No major training and new skills are required as it is based on DBMS model.

It will help in the time saving and fast processing and dispersal of user request. New

product will provide all the benefits of present system with better performance.


21/60

Faster and systematic processing of the system.

Thus, the system that I developed is feasible in all terms.

SOFTWARE REQUIREMENT SPECIFICATION

Software requirement specification (SRS) is the starting point of the software development activity.

Little importance was given to this phase in the early days of software development. The emphasis

was first on coding and then shifted to design.

As systems grew more complex, it became evident that the goals of the entire system cannot be

easily comprehended. Hence the need for the requirement analysis phase arose. Now, for large

software systems, requirements analysis is perhaps the most difficult activity and also the most error

prone.

Requirement of a single Control Id for a single user using which the user can login and use all the

government or private services.

SYSTEM REQUIREMENTS

Processor INTEL PENTIUM III/IV OR

EQUUIVALENT

RAM 128 MB

HDD 10 GB(Minimum)

Software

Platform WINDOWS


22/60

Architecture JSP,DHTML

BACKEND

Ms Access

FRONTEND

Java

SYSTEM DESIGN

INTRODUCTION

System design provides the understandings and procedural details necessary for

implementing the system recommended in the system study. Emphasis is on the translating

the performance requirements into design specifications. The design phase is a transition

from a user-oriented document (System proposal) to a document oriented to the

programmers or database personnel.

System design goes through two phases of development:


23/60

1) Logical Design

2) Physical Design

Logical and Output Design:

The logical design of an information system is analogous to an engineering blue print of an

automobile. It shows the major features and how they are related to one another. The detailed

specification for the new system was drawn on the bases of users requirement data. The outputs

inputs and databases are designed in this phase.

External Outputs, whose destination is outside the organization,

Internal outputs, whose destination is with the organization.

Operational outputs, whose use is purely within the computer department e.g.,

program-listing etc.

Other important factors that were taken into consideration are:

The End user, who will use the output.

The actual usage of the planned information

The information that is necessary for presentation

When and how often output and their format are needed. While designing output for

project based Attendance Compilation System, the following aspects of outputs

designing were taken into consideration.

The outputs (i.e., well formatted table outputs in the screen itself) designed are simple

to read and interpret.

Format of each output was another important point taken into consideration. Output

media, for each output appropriate media is decided whether it will be displayed on

screen or will be taken to printer or both.

Other output design related specifications, i.e., how frequently the outputs will be

generated, how many pages or sheets approximately it will keep up, what is its

planned use and output distribution to users are also taken into account.

.


24/60

Output Sources:

Output contents originate from these sources:

Retrieval from a data source.

Transmission from a process or system activity.

Directly from an input source.

The information produced in an output can be presented as

Tabular contents

Graphic format

Using Icons

Output Definition:

The output should be defined in terms of:

Types of outputs

Content-headings, numeric, alphanumeric, etc.,

Format-hardcopy, screen, microfilm, etc.,

Location-local, remote, transmitted, etc.,

Frequency-daily, weekly, hourly, etc.,

Response-immediate with in a period, etc.,

.

SOFTWARE DESIGN


25/60

The purpose of this phase is to plan a solution for the problem specified by the requirement

document. This is first step in moving from the problem domain to solution domain. Designing

activity is divided into two parts.

a) System Design: It aims to identify the modules that should be in the system, the specification of

these modules and how they interact with each other to produce the desired result.

b) Detailed Design: The internal goal of each of the modules specified in the system design is

decided.

\

DATABASE DESIGN

A database is a collection of inter-related data stored with a minimum of

redundancy to serve many applications. It minimizes the artificiality embedded

in using separate files. The primary objectives are fast response time to

enquires, more information at low cost, control of redundancy, clarity and ease

of use, accuracy and fast recovery. The organization of data in a database aimsto achieve three major objectives, they are data integration, data integrity and

data independence. During the design of the database at most care has been

taken to keep up the objectives of the database design.

CODE DESIGN

The process of code is to facilitate the identification and retrieve of items of information.

The code should be simple and easy to understandable. The codes were designed in such a

way that the features such as optimum human oriented use and machine efficiency are

unaffect.

DATA FLOW DIAGRAM


26/60

Data Flow Diagramming is a means of representing a system at any level of detail with a graphic

network of symbols showing data flows, data stores, data processes, and data sources/destination.

The data flow diagram is analogous to a road map. It is a network model of all

possibilities with different detail shown on different hierarchical levels. This

processes of representing different details level is called leveling or

partitioning by some data flow diagram advocates. Like a road map, there is

no starting point or stop point, no time or timing, or steps to get somewhere.

We just know that the data path must exist because at some point it will be

needed. A road map shows all existing or planned roads because the road is

needed.

Terms used in DFD:

Process

Data flows

Actors

Graphical Representation:

Graphical Representation:


27/60

An actor is active object that drives the data flow graph by producing or consuming

values.

LEVEL ZERO DFD

Customer

Provid


28/60

SYSTEM TESTING

Here the System testing involved is the most widely used testing process consisting of five stages as

shown in the figure. In general, the sequence of testing activities is component testing, integration

testing, and then user testing. However, as defects are discovered at any one stage, they require

program modifications to correct them and this may require other stages in the testing process to be

repeated.

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance

and for ensuring the reliability of the software. The results of testing are used later on during

maintenance also.

Testing is vital to the success of the system. System testing makes a logical assumption that if the

parts of the system are correct, the goal will be successfully achieved. In adequate testing or non-

testing leads to errors that may not appear until months or even years later (Remember the New

York three day power failures due to a misplaced Break statement).

This creates two problems:

1. The time lag between the cause and the appearance of the problem.

2. The time interval effect of the system errors on files and the records on the system.

A small error can conceivably explode into a much larger problem. Effective testing early in the

process translates directly into long term cost savings from a reduced number of errors.


29/60

TESTING OBJECTIVES

The main objective of testing is to uncover a host of errors, systematically and with minimum effort

and time.

Stating formally, we can say,

Testing is a process of executing a program with the intent of finding an error.

A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if it exists.

The tests are inadequate to detect possibly present errors.

The software more or less confirms to the quality and reliable standards.

LEVELS OF TESTING

UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the

detailed design and the process specifications, testing is done to uncover errors within the boundary

of the module. All modules must be successful in the unit test before the start of the integration

testing begins.

INTEGRATION TESTING

After unit testing, we have to perform integration testing. The goal here is to see if modules can be

integrated properly, the emphasis being on testing interfaces between modules. This testing activity


30/60

can be considered as testing the design and hence the emphasis on testing module interactions.

SYSTEM TESTING

Here the entire software system is tested. The reference document for this process is the

requirements document, and the goal is to see if software meets its requirements.

Here entire HRRP has been tested against requirements of project and it is checked whether all

requirements of project have been satisfied or not.

ACCEPTANCE TESTING

Acceptance Testing is performed with realistic data of the client to demonstrate that the software is

working satisfactorily. Testing here is focused on external behavior of the system; the internal logic

of program is not emphasized.

WHITE BOX TESTING

This is a unit testing method, where a unit will be taken at a time and tested thoroughly at a

statement level to find the maximum possible errors.

I tested step wise every piece of code, taking care that every statement in the code is executed at

least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data, which is used to check all possible combinations of

execution paths through the code at every module level.

BLACK BOX TESTING


31/60

This testing method considers a module as a single unit and checks the unit at interface and

communication with other modules rather getting into details at statement level. Here the module

will be treated as a block that will take some input and generate output. Output for a given set of

input combinations are forwarded to other modules.

Graph based testing methods explore the relationship between and behavior of program objects.

Equivalence partitioning divides the input classes of data are likely to exercise specific software

function. Boundary values analysis probes the programs ability to handle data at the limits of

acceptability.

INFORMATION FLOW OF DATA FOR TESTING

Evaluation

Testing

Software

Configuration

Error

Rate

Data

Ex ected

Error


32/60

IMPLEMENTATION

Introduction

System implementation is the stage when the user has thoroughly tested the system and approves all

the features provided by the system. The various tests are performed and the system is approvedonly after all the requirements are met and the user is satisfied.

The system may be totally new; replacing an existing manual or automated system, or it may be a

major modification to an existing system. In either case, proper implementation is essential to

provide a reliable system to meet organizational requirements. Successful implementation may not

guarantee improvement in the organization using the new system (that is a design question), but

improper will prevent it.

Aspects of Implementation

The two aspects of implementation are:

Training Personnel

Conversion Procedures

Reliability

ModelDebug

Test Configuration

Predicted Reliability Correction


33/60

TRAINING

Even well designed and technically elegant systems can succeed or fail because of the way

they are used. Therefore the quality of the training received by the personnel involved with

the system in various ways helps or hinders, and may even prevent, the successful

implementation of an information system.

CONVERSION:

Conversion is the process of changing from the old system to the new system. There are

two methods of handling systems conversion:

Parallel Run

Immediate cut-off

Parallel Run

In this approach, the old system and the new system are used simultaneously for some

period of time so that the performance of the new system can be monitored and compared

with that of the old system. Also in case of failure of the new system, the user can fall back

on the old system. The risk of this approach is that the user may never want to shift to new

system.

Immediate cut-off

In this method, the use of the old system ceases as soon as the new system is

implemented and bought in to palace. The old system becomes redundant from the day of

implementation of the new system. There is the high risk involved in this approach if the

new system is not tested rigorously. This is because of the fact that if the new system fails,


34/60

then there will not be anything to fall back upon. The advantage of this approach is that

both the systems need not be used simultaneously.

Implementation Tools

The project was implemented using Active server pages, HTML. The implementation work

was carried out in Windows XP server platform.

1) J2ee

2) Web Services

3) Weblogic 8.1

Coding

This means program construction with procedural specifications has finished

and the coding for the program begins:

Once the design phase was over, coding commenced

Coding is natural consequence of design.

Coding step translate a detailed design representation of software into a programming

language realization.

Main emphasis while coding was on style so that the end result was an optimized code.

The following points were kept into consideration while coding:

Coding Style

The structured programming method was used in all the modules the project. It

incorporated the following features

The code has been written so that the definition and implementation of each function is

contained in one file.

A group of related function was clubbed together in one file to include it when needed

and save us from the labour of writing it again and again.


35/60

ADD DATA

import java.io.*;

import java.sql.*;

import javax.servlet.*;

import javax.servlet.http.*;

public class add extends HttpServlet

{

String Error,str,str1,fno,end,s1,cap;

int end1,end2,cap1;

Connection con;

Statement st;

ResultSet rst;

public void init(ServletConfig config)throws ServletException

{


36/60

super.init(config);

try

{

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

con=DriverManager.getConnection("jdbc:odbc:DSN","scott","tiger");

}

catch(Exception e)

{

Error="Exception in init:"+e;

}

}

public void doGet(HttpServletRequest req,HttpServletResponse res)throws

ServletException,IOException

{

PrintWriter out=res.getWriter();

res.setContentType("text/html");

fno=req.getParameter("flight_no");

end=req.getParameter("ending_seatno");

end1=Integer.parseInt(end);

end2=end1+1;

cap=req.getParameter("capacity");

out.println("");

out.println("");

out.println("function nam()");

out.println("{");


37/60

out.println("var a=document.forms[0].cat.value;");

out.println("if(a.length == 0)");

out.println("{");

out.println("alert(\"Null field\");");

out.println("document.forms[0].cat.focus();");

out.println("return;");

out.println("}");

out.println("else");

out.println("{");

out.println("for(i=0;i='a' && b ='A' && b


38/60

out.println("var a=document.forms[0].ticket.value;");

out.println("if(a.length == 0)");

out.println("{");


out.println("document.forms[0].ticket.focus();");


out.println("}");


out.println("{");

out.println("for(i=0;i=0 || b


39/60

out.println("var p= document.forms[0].end.value");

out.println("if(p.length == 0)");

out.println("{");


out.println("document.forms[0].end.focus();");

out.println("document.forms[0].end.value=\"\";");


out.println("}");


out.println("{");

out.println("var x=parseInt(document.forms[0].start.value);");

out.println("x.toString();");

out.println("var y=parseInt(document.forms[0].end.value);");

out.println("y.toString();");

out.println("if(ya){");


40/60

out.println("alert(\"ending seat no is greater than total capacity\");");

out.println("document.forms[0].end.focus();");

out.println("document.forms[0].end.value=\"\";");

out.println("}");


out.println("{");

out.println("for(i=0;i=0 && b


41/60

out.println("");

out.println("");

out.println("Flight No:");

out.println("Category:");

out.println("Cost Of

Tickets:");

out.println("Start Seat No:");

out.println("Ending Seat

No:");

out.println("");

out.println("");

out.println("");

}

catch(Exception e1)

{

out.println("Exception in connection:"+e1);

}

out.println("");

}

}

ADMINSTRATOR


42/60

import java.io.*;



public class admin extends HttpServlet

{



{



try

{

out.println("");

out.println("");

out.println("

");

out.println("");

out.println("Administration

");

out.println("Add Flight Details");

out.println("Modify Flight Details");

out.println("Delete Flight Details");


43/60

out.println("Concession Details");

out.println("Modify Concession Details");

out.println("Delete Concession Details");

out.println("");

out.println("");

}

catch(Exception e)

{}

}

}

DELETE DATA

import java.io.*;

import java.sql.*;



public class cdelete extends HttpServlet

{

Connection con;

Statement st;

ResultSetMetaData rmt;


44/60

ResultSet rst;

String Error;


{

super.init(config);

try

{


con=DriverManager.getConnection("jdbc:odbc:DSN","psrini","ssi");

}

catch(Exception e)

{

Error="Exception in init"+e;

}

}



{



out.println("");

out.println("Select Concession Type To Be Deleted");

out.println("Type Of Concession:");

try

{


45/60

st=con.createStatement();

rst=st.executeQuery("select type from concession_master");

rmt=rst.getMetaData();

int count=rmt.getColumnCount();

for(int i=1;i


46/60

}

INSERT DATA

import java.io.*;

import java.sql.*;



public class cinsert extends HttpServlet

{

Connection con;

PreparedStatement pst,pst1;

String code,des,per,d2;

int d;

public void doPost(HttpServletRequest req,HttpServletResponse res)throws


{



code=req.getParameter("code");

des=req.getParameter("desc");

d=des.indexOf("h");

d2=des.substring(d,des.length());

System.out.println("D2:"+d2);

per=req.getParameter("percent");

try


47/60

{



if(d2.equals("h"))

{

System.out.println("Srinivas");

pst1=con.prepareStatement("insert into cancellation_master

(code,description1,percentage1)values(?,?,?)");

pst1.setString(1,code);

pst1.setString(2,des);

pst1.setString(3,per);

pst1.executeUpdate();

}

else

{

pst=con.prepareStatement("insert into cancellation_master

(code,description,percentage)values(?,?,?)");

pst.setString(1,code);

pst.setString(2,des);

pst.setString(3,per);

pst.executeUpdate();

}

out.println("");

out.println("

");

out.println("Do you want to continue");


48/60

out.println("[ Yes ]

[ No ]");

out.println("");

}

catch(Exception e)

{

out.println("Exception in connection:"+e);

}

}

}

MODIFY

import java.io.*;

import java.sql.*;



public class cmodify extends HttpServlet

{

Connection con;

Statement st;

ResultSetMetaData rmt;

ResultSet rst;

String Error;


{

super.init(config);


49/60

try

{



}

catch(Exception e)

{

Error="Exception in init"+e;

}

}



{



out.println("");

out.println("Select Concession Type To Be Modified");

out.println("Type Of Concession:");

try

{


rst=st.executeQuery("select type from concession_master");

rmt=rst.getMetaData();

int count=rmt.getColumnCount();

for(int i=1;i


50/60

out.println(rmt.getColumnName(i));

while(rst.next())

{

out.println("");

for(int i=1;i


51/60


public class login extends HttpServlet

{

Connection con;



{



try

{



out.println("");

out.println("");

out.println("");

out.println("Enter the password ");

out.println("
");

out.println("User-Id :");

out.println("Password:");

out.println("");

out.println("");

out.println("");

out.println("");


52/60

}

catch(Exception e)

{

out.println("Exception in connection :"+e);

}

}

}

PAYMENT

import java.io.*;

import java.sql.*;

import java.util.*;



public class payment extends HttpServlet

{

Connection con;

Statement st;

ResultSet rst;

String str,rno,amt,total,date;

String

month[]={"jan","feb","mar","apr","may","jun","jul","aug","sep","oct","nov","dec

"};

int dt,mo,ye;




53/60

{



rno=req.getParameter("rno");

total=req.getParameter("total");

Calendar c=Calendar.getInstance();

dt=c.get(Calendar.DAY_OF_MONTH);

mo=c.get(Calendar.MONTH);

ye=c.get(Calendar.YEAR);

date=(dt+"-"+month[mo]+"-"+ye);

try

{


con=DriverManager.getConnection("jdbc:odbc:DSN","scott","tiger");


rst=st.executeQuery("select nvl(max(invoice_no),0)+1 from

payment_details");

while(rst.next())

str=rst.getString(1);

out.println("");

out.println("");

out.println("Payment

Details");

out.println("");

out.println("Invoice No:");


54/60

out.println("Res No:");

out.println("Amount:");

out.println("Date:");

out.println("Mode::Credit Card");

out.println(":Cheque");

out.println("");

out.println("");

out.println("");

out.println("");

}

catch(Exception e)

{

out.println("Exception in connection:"+e);

}

}

}


55/60

ROLE OF TEAM MEMBERS

This project is the result of the team work of all of us. We all divided this

task into different units which were completed by each member respectively

and at last integrated together to get this outcome.

1. REQUIREMENT ANALISIS - Rahul Dayal ,Saurabh,Saurabh

Singh,Tarun,Ramakant

2. DESIGNING - Rahul Dayal ,Saurabh,Saurabh


3. CODING - Rahul Dayal ,Saurabh,Saurabh


4. TESTING - Rahul Dayal ,Saurabh,Saurabh



56/60

GANTT CHART


57/60


58/60


59/60

THANK YOU

With A Happy Ending Note We Would Like To Thank College And Our

DepartmentIncluding All The Faculty Members For Providing Us A

Wonderful Opportunity To Prepare This Project. We Are Very Grateful To

All Those Who Were Involved In This ProjectWe Hope That Our

Project Is Linked By All Of You..

Thank You Very Much.!!!


60/60

TITLE OF THE PROJECT

Airlines Reservation System

Project Tarun

Documents

Transcript of Project Tarun