A PROJECT REPORT ON

SUBMITTED BY .

Project in Charge

Head of Department

External Examiner

INDEX
NEED FOR COMPUTERIZATION DISADVANTAGE OF MANUAL SYSTEM PRELIMINARY INVESTIGATION SOFTWARE AND HARDWARE REQUIREMENTS MANUAL SYSTEM FEASIBILITY STUDY FACT FINDING TECHNIQUES ER DIAGRAM DATA FLOW DIAGRAM DATA PROCESS DATA DICTIONARY INPUT OUTPUT SCREENS SOFTWARE TESTING AND IMPLEMENTATION BENEFITS OF THE SYSTEM DRAWBACKS AND LIMITATIONS CONCLUSION BIBLOGRAPHY

NEED FOR COMPUTERIZATION

NEED FOR COMPUTERIZATION

The work that was being carried out with the help of manual system had to be transferred to the computer & internet for variety of reasons. The manual system is slowly being passed out and all the activities that are being carried out by manual system are to be taken into care of, by the computer system. There were many systems that demanded computerization but were not being covered by the manual system. Actual time required for solution of particular task takes lot of time but with computer system it is very fast and easy by using query facility. In manual system reports, storage, calculation and other documentation takes more time that causes delay in processing, so by computerization of the system this delay processing problem is solved. In the existing system the user cannot get fast service, but by computerization it is done much faster.

The most important advantage computerization is that International Business is also possible very easily. The computerized system is customer friendly and saves lot of time and energy of our precious customer because it eliminates long waiting time and many more things.

DISADVANTAGES OF MANUAL SYSTEM

1. Though we can store large amount of data in files, its time consuming. 2. Due to manual system, accuracy

decreases. 3. 4. Speed of work is very slow. Manpower required is more for

maintaining accounts. 5. It is costlier than a computerized

system.

6.

Handling of complex system is very hard.

Due to these disadvantages we propose a Computerized Airline Reservation System.

MERITS OF PROPOSED SYSTEM

MERITS OF PROPOSED SYSTEM

MENU DRIVEN AND USER FRIENDLY. ALL IMPORTANT DATA IS MAINTAINED. DATA ACCURACY. UPDATIONS OF FILES ARE DONE. ALL INFORMATION AT A GLANCE. LESS PAPER WORK.

 REDUCTION

IN

MAINTAINENCE

&

ORGANIZING COST. CAN BE ACCESSED ANYTIME AT USERS PREFERENCE.

SCOPE OF PROPOSED SYSTEM

SCOPE OF PROPOSED SYSTEM

The proposed system is designed by talking into consideration all the limitations of manual system. Existing manual system & as per the requirement suggested by user. It is designed in such a way that it hold all the information that we need for data processing & to generate various reports as per requisition. Major advantages of proposed system over manual system are: 1. Time sharing 2. Rapid information processing 3. Accurate report generation 4. Less paper work 5. Fast & reliable information distribution 6. Reduction in cost

System is designed in Java language, as per Object Oriented Programming (OOP) package, used java features such as platform independent. It is stored in form of tables in OOP files handling in database. System is developed using Microsoft Access which is database management system. The applications are made user friendly through java using Swing and reports are displayed in HTML. Windows is user friendly Operating System & Hence it is used for this application in order to facilitate users.

PRELIMINARY INVESTIGATION

PRELIMINARY INVESTIGATION
While designing any system preliminary investigation is an important & essential part. Any person related with the system initiates the request when that request is made, preliminary investigation starts. The system has its foundation on preliminary investigation. It has been done by following techniques:-

 Request Clarification Feasibility Study Request Approval

1. Request Clarification: Any what the originator request wants, initiated before by any person must be examined to determine precisely system investigation is started.

2. Feasibility Study: The feasibility study is useful to evaluate the cost & benefit of the system requested. It tries to anticipate future scenarios of software development. Types of Feasibility Study: 1. Technical Feasibility 2. Economical Feasibility 3. Operational Feasibility

3. Request Approval: The request received from various people is studied for its feasibility & that request, which is feasible are approved. After requests are approved its cost/priority, completion time &

personal

requirements

are

estimated

&

project

planning is updated.

FACT FINDING TECHNIQUES

FACT FINDING TECHNIQUES

Before starting the actual development of

the system, system analyst collects the important information about manual system from the user department. In order to collect this information, system analyst prefers any of the following fact finding techniques. There are four types of Fact finding techniques as follows.

Interview

 Questionnaire Record Review Observation 1.

Interview:

Analyst

uses

interview

techniques to collect information of system from individuals or smaller groups. The respondent is generally current users of existing system or potential are proposed system. This technique requires some more times than the other factfinding techniques. It is important to remember that the respondent and analyst should converse only during the interview. Interview techniques allow analyst to discover the area of misunderstanding and unrealized expectation and even indication of resistance to the proposed system.

2. Questionnaire: -

The use of questionnaires

allows the analyst to collect the information about various accept of system, from large number of person. The use of standardized question format can yield more reliable greater anonymity for respondent responses. Analyst often uses open-ended questionnaires to learn about feelings, opinion and which can lead to more honest

general experiences on to explore a process or problem.

3. Record Review: -

Many kinds of records and

reports can provide analyst valuable information about organization and operation. In record review analyst examines information that has been about system and user. Record exception can be perform at the beginning of the study as an introduction or later in the study as a basis for comparing actual operation with for the record indicates should be happening.

4. Observation: fact finding

Observation allows analyst to Through observation

collect the information, they cannot obtain by other techniques. analyst can obtain first information about how activities are carried out. This method is most useful when analyst need to actually observe how documents are handling, how process are carried out and weather the specific steps are actual followed.

FEASIBILITY STUDY

FEASIBILITY STUDY
Designing of any system includes first step, which is preliminary investigation. It is important and essential part on which the whole system depends. Study of preliminary

investigation is done through different type of feasibility studies.

The Feasibility Serves as:

1. To identify the scope of current system to be studied. 2. To identify the problems and unexploited opportunities in the current system that may be manual or automated. 3. To identify the major objectives of the new system. 4. To estimate roughly the cost of each possible solution to the user problem and identify that solution that satisfies the user need within his budget & schedule. 5. To developed rough estimates of the benefits and drawback of each solution. 6. To developed outline of how the project may be carried out with an idea of resources required. 7. To obtain user and management views on all above procedures. 8. To obtain decision from the user and from the management onto commit of at least analysis part of the project.

The different types of feasibility study that are carried out during the project development are as follows.

1. Technical feasibility study:

This is study of hardware, software Requirement phasecost and of available manpower. as In well this as hardware, software

technical equipment are considered and found that whether the required system is technically feasible for organization or not.

2. Economical Feasibility Study:

In this study he benefits of the system are considered by means actual cost /benefits analysis. While considering these benefits system tangible and intangible benefits are also considered and find out that whether cost is acceptable or not i.e. to find out the economical feasibility of purposed system. It consists of one time cost and recurrent cost.

3. Operational Feasibility Study:

Operational feasibility of the system depends on various factors such as the user friendliness of system, operating case user attitude towards the same. The system designed in such a way that it will cope up with the future development requirement.

The new system being presentable will catch users attention and interest there by reducing confusion and resistance. The users satisfaction will at least determine the proposed systems feasibility. Operational feasibility study must be carried out because it is necessary to consult the user to see whether the proposed system solves the objectives or not.

E.R. & DATA FLOW DIAGRAM

Entity Relationship (E.R.) Diagram

DATA FLOW DIAGRAM

The Data Flow Diagram (D.F.D) serves two purposes: 1.To provide an indication of how data are transformed as they move through the system. 2.To depict the functions that transforms the dataflow. The DFD provides additional information domain and serves as a basis for modeling of function. It is a graphical representing that depicts information flow the transforms that are applied as data move from input to output. The basic flow of data flow diagram is also known as data flow graph or bubble chart.

Context Level DFD

1.0 level DFD

2.0 level DFD

3.0 Level DFD

DATA DICTIONARY

DATA DICTIONARY
DFDs themselves not describe all details about data flows. For investigation one additional tool is used to support DFDs which is called Data Dictionary. DD provides additional information about the system. DD is called catalog or central repository. DD is an analysis tool that primarily records the information content of data. It stores definition of all data mentioned in DFD and in process specification.

Components Dictionary:

of

Data

1. Data Elements: DD consists of detailed

information of the data used.

2. Data Names:

To distinguish an item, a meaningful name given to data parameter is called as data name.

3. Data Description: Sometimes because of

field size restriction Data name itself doesnt give the meaning of data parameter. Data Description precisely states what data items represents in the system.

4. Aliases: One data item may be referred

by different names depending upon who is using it. The additional names given to data item are called as aliases.

5. Data Type: It identifies the type of data

i.e. whether it is numeric, character, date etc.

6. Length:

It represents the amount of space required for the data item.

7. Data Values:

With data item some additional prefixes are added are called as data values.

8. Range:

It gives information about the lowest and highest possible value stored in the data item.

9. Data Structure: Data structure is based

on sequential relationship among the data item. It will give information about the formation of the data item.

Sr. Field Name Data Type No.

1 2 3 4 5 6 7 8 9 10 11 12 13 route_id start_ap end_ap flight_id start_time end_time seats scheme_id scheme_name Integer Integer Integer Integer Date/Time Date/Time Integer Integer String airport_id Integer

Table Name
Airport Airport Airport

Description
Contains the Airport ID of the Airport. Contains the name of the Airport. Contains the name of country of airport. Contains the Route ID. of the Route. Contains the Airport ID of the DepartureAirport. Contains the Airport ID of the Arrival Airport. Contains the Flight ID of the flight. Contains the flights Departure Time. Contains the Flights Arrival Time Contains the no. of seats in Plane. Contains the Scheme ID of the Scheme. Contains the name of the Discount Scheme.

airport_name String country String

route route route flightroute flightroute flightroute flightroute scheme scheme

Sr. Field Name Data Type No.

14 scheme_desc String

Table Name

Description
Contains the Details and Description of the Scheme. Contains the Scheme Discount. Contains the Passenger ID no. Contains the Passenger Name. Contains the Passengers sex. Contains the Passengers Nationality Contains the Passengers Ticket ID. Contains the class-type of the ticket. Contains the fair paid by the Passenger Contains the Jorney Date. Contains the cancellation no. Contains the ticket Cancellation Date.

scheme

15 16 17 18 19 20 21 22 23 24 25

discount passenger_id name gender nationality ticket_id class_type fare_paid j_date cancel_no Cancel_date

Integer Integer Text Text text Integer Text Integer Date/Time Integer Date/Time

scheme passenger passenger passenger passenger passengerticket passengerticket passengerticket passengerticket cancel cancel

FILE DESIGN

FILE DESIGN
1. Table Name: Airport Description: Contains all Details about Airport Record.
Field Name airport_id airport_name Address city country Data type Number Text Text Text Text

2. Table Name: Route Description: Contains all Details about Air-Route Record.
Field Name route_id start_ap end_ap miles Data type Number Number Number Number

3. Table Name: Flightroute

Description: Contains all Details about Flight-Route Record.

Field Name flight_id start_time end_time s_airport e_airport miles First Business Economy Data type Number Date/Time Date/Time Number Number Number Number Number Number

4. Table Name: Scheme Description: Contains all Details about the Ticket Scheme and discounts.
Field Name scheme_id scheme_name period scheme_desc scheme_disc Data type Number Text Number Text Number

5. Table Name: Passenger Description: Contains all Details about Passenger.

Field Name passenger_id passport_no name address age Data type Number Text Text Text Number

gender email_id nationality

Text Text Text

6. Table Name: Passengerticket Description: Contains all Details about Passengers ticket.
Field Name ticket_id passenger_id scheme_id class_type fare_paid flight_id j_date Data type Number Number Number Text Number Number Date/Time

7. Table Name: Cancel Description: Contains all Details about Ticket cancellation Record.
Field Name cancel_no date ticket_id Data type Number Date/Time Number

SOFTWARE TESTING AND IMPLEMENTATION

SOFTWARE TESTING AND IMPLEMENTATION

Software testing is the process of executing a program with an objective of finding an error. Software quality should be primary concerned in software development efforts. Software testing & evaluation are traditional methods of checking software quality. Software testing is successfully only if all errors from it are removed. The technique that finds max errors is good testing techniques. The prime objective of testing is to test the code with intention to find errors.

TESTING STRATEGIES:

No single technique is available which will find all errors. It may be good if 1. There is a high probability of finding errors. 2. It is not redundant. 3. It is simple to execute. 4. It should trace back to customer requirement.

1. BLACK BOX TESTING:

Inputs Outputs

BBT is related with input and output with internal structure of program. In BBT it is checked if some input is given, then whether specific output is produced by the programs or not. Various sets of input test cases are prepared and applied on a program & corresponding output produced.

BBT is used to find errors like: 1. 2. 3. 4. 5. Incorrect & missing functions Interfacing errors Initialization & termination errors Errors in external database access Performance errors

2. WHITE BOX TESTING:

WBT is related with the structure of program. To test the logic of the program, various tests are designed which takes care of following: 1. Every system should be executed at least once. 2. Every path in the program must be executed at least once (path analysis). 3. Execute their entire loop on their boundaries & within operational boundaries. 4. Execute internal data structure & formulate to ensure their validity.

3. PERFORMANCE TESTING:
Performance testing determines the length of system used by the system to process transaction data. This test is conducted prior to

implementation to determine how long it takes to get response to an query, make a backup copy of a file. Performance testing is designed to test run time performance of software within context of an integrated system. Performance testing is carried out throughout all the steps in the testing process.

4. USER ACCEPTANCE TESTING:

An acceptance test has the objective of selling user on the validity & reliability of the system. It verifies that system procedures operate to system specification & that integrity of important data is maintained. Compressive test report is prepared.

5. STRESS TESTING:
It determines whether the system will handle the volume of activities that occur when the system is at peak of the processing demand. E.g. Test the system by activating all the terminals of the system at the same time. The main goal of the stress testing is to test performance of the system under max use of memory, disk space.

HARDWARE AND SOFTWARE REQUIREMENTS

Minimum Software Requirements:
Software is the collections of programs. For running of the system Software is needed. Operating System : Vista. Application Editor Software : : Microsoft Access. Notepad. Windows 98/ 2000/ XP/

: Jdk1.4.0 or higher.

Internet Explorer 4 or higher.

Minimum Hardware Requirements:

Physical requirement i.e. Monitor, CPU, Mouse etc. are called as Hardware requirements. Ram Hard Disk Space) : 128 MB : 20GB ( 2GB free Hard Disk

 Display Type : Standard VGA Monitor Printer Mouse mouse Keyboard Keyboard. CD Rom , CD Writer : Standard 101/102-key : Inkjet / Laser : Standard PS/2 compitable

SYSTEM FEATURE

SYSTEM FEATURE
While designing system, it has to be internally manipulated all aspects i.e. logical flow of data to user. The system provides level. effect functionally chances with of inbuilt entering triggers and constraints user at database They reduce garbage into system by effective filtration of date and provide it in more meaningful way to user functional complexity must be handled the database updated up to next process should be reusable into another. The software developed using Sun

Java which has any user interactions.

 The application are made user friendly through menu driven programming. This interface is graphical which is more attractive and understandable to user. File Handling helps in storing and retrieving data.

DRAWBACKS AND LIMITATIONS

DRAWBACKS LIMITATIONS

AND

The system has some drawbacks and limitations which are as follows: Searching for record is very difficult. It is a very vital problem faced by the user. The handling and recovery techniques are time consuming and volume of database increases. System requires standalone Software like Apache Tomcat4.0 for running. Keeping track of record is very difficult.

 Human mistakes due to inefficiency, fatigue, lack of time and rectification needed due to manual work.

CONCLUSION

CONCLUSION
THE SYSTEM WILL MAKE DAILY TRANSACTION IN SHORT TIME & REPORT GENERATED MANUAL VERY EASILY & CORRECTLY EVERYTHING WHICH WAS SO COMLICATED IN PREVIOUS SYSTEM BECAUSE HAD TO BE CARRIED OUT MANUALLY. THIS SYSTEM IS EASY TO UNDERSTAND AND OPERATE AND IT IS ALSO USER FRIENDLY. ALL THE DIFFICULIES OF THE SYSTEM HAVE BEEN REMOVED. THE USER CAN GET ALL THE INFORMATION HE

WANTS AS IT CAN HELP HIMSELF AND HE IS GUIDED THROUGH WITH ALL THE LINKS AND INFORMATION. ALSO LESS TIME IS REQUIRED FOR THE PROCESSING.

BIBLOGRAPHY
1. THE COMPLETE REFERENCE : -By Herbert Schildt. 2. SUN MICROSYSTEM JAVA SERVER PAGES: -By Cay S. Horstmann, Gray Cornell. 3. JAVA PROGARMMING: -By Black Book. 4. ADVANCED JAVA PROGARMMING: -By Khobragad.

5. JAVA SCRIPT & JSCRIPT: -By Jowrski.