Synopsis & SRS

7/28/2019 Synopsis & SRS

1/47

A

PROJECT REPORT

ON

SUBMITTED BY

.

Project in Charge Head of Department

External Examiner


2/47

INDEX

NEED FOR COMPUTERIZATION

DISADVANTAGE OF MANUAL SYSTEM

PRELIMINARY INVESTIGATION

SOFTWARE AND HARDWAREREQUIREMENTS

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


3/47

NEED FOR

COMPUTERIZATION


4/47

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.


5/47

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 OFMANUAL SYSTEM

1. Though we can store large amount of

data in files, its time consuming.

2. Due to manual system, accuracy

decreases.

3. Speed of work is very slow.

4. Manpower required is more for

maintaining accounts.

5. It is costlier than a computerized

system.


6/47

6. Handling of complex system is very

hard.

Due to these disadvantages we propose a

Computerized Airline Reservation System.

MERITS OF PROPOSED

SYSTEM


7/47

MERITS OF PROPOSEDSYSTEM

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.


8/47

REDUCTION IN MAINTAINENCE &

ORGANIZING COST.

CAN BE ACCESSED ANYTIME AT USERS

PREFERENCE.

SCOPE OF PROPOSED

SYSTEM


9/47

SCOPE OF PROPOSEDSYSTEM

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


10/47

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.


11/47

PRELIMINARY

INVESTIGATION

PRELIMINARYINVESTIGATION

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:-


12/47

Request Clarification

Feasibility Study

Request Approval

1. Request Clarification: -

Any request initiated by any

person must be examined to determine precisely

what the originator wants, before 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 &


13/47

personal requirements are estimated & project

planning is updated.


14/47

FACT FINDING TECHNIQUES

FACT FINDING TECHNIQUESBefore 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


15/47

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 fact-

finding 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 which can lead to more honest

responses.

Analyst often uses open-ended

questionnaires to learn about feelings, opinion and


16/47

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: - Observation allows analyst to

collect the information, they cannot obtain by other

fact finding techniques. Through observation

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.


17/47

FEASIBILITY STUDY

FEASIBILITY STUDY

Designing of any system includes firststep, which is preliminary investigation. It is

important and essential part on which the whole

system depends. Study of preliminary


18/47

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.


19/47

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 and available manpower. In this

phasecost of hardware, software as well as

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:


20/47

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.


21/47

E.R. & DATA FLOW

DIAGRAM


22/47

Entity Relationship (E.R.)Diagram


23/47

DATA FLOW DIAGRAM

The Data Flow Diagram (D.F.D) serves twopurposes:

1.To provide an indication of how data

are transformed as they move throughthe system.2.To depict the functions that transforms

the dataflow. The DFD providesadditional information domain andserves as a basis for modeling offunction.

It is a graphical representing that depictsinformation flow the transforms that areapplied as data move from input to output.The basic flow of data flow diagram is alsoknown as data flow graph or bubble chart.


24/47

Context Level DFD

1.0 level DFD


25/47

2.0 level DFD

3.0 Level DFD


26/47

DATA DICTIONARY


27/47

DATA DICTIONARY

DFDs themselves not describe all

details about data flows. For investigationone additional tool is used to support DFDswhich is called Data Dictionary. DD providesadditional information about the system. DDis called catalog or central repository.

DD is an analysis tool thatprimarily records the information content ofdata. It stores definition of all datamentioned in DFD and in processspecification.

Components of DataDictionary:

1. Data Elements: DD consists of detailedinformation of the data used.

2. Data Names: To distinguish an item, ameaningful name given to data parameter iscalled as data name.

3. Data Description: Sometimes because offield size restriction Data name itself doesntgive the meaning of data parameter. Data

Description precisely states what data itemsrepresents in the system.


28/47

4. Aliases: One data item may be referred

by different names depending upon who isusing it. The additional names given to dataitem are called as aliases.

5. Data Type: It identifies the type of datai.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 someadditional prefixes are added are called asdata values.

8. Range: It gives information about thelowest and highest possible value stored in

the data item.

9. Data Structure: Data structure is basedon sequential relationship among the dataitem. It will give information about theformation of the data item.


29/47

Sr.

No.Field Name Data Type

Table

NameDescription

1 airport_id Integer Airport

Contains the

Airport ID of the

Airport.

2 airport_name String AirportContains the name

of the Airport.

3 country String Airport Contains the nameof country of

airport.

4

5 route_id Integer routeContains the Route

ID. of the Route.

6 start_ap Integer route

Contains the

Airport ID of the

DepartureAirport.

7 end_ap Integer route

Contains the

Airport ID of the

Arrival Airport.

8 flight_id Integer flightrouteContains the Flight

ID of the flight.

9 start_time Date/Time flightroute

Contains the

flights Departure

Time.

10 end_time Date/Time flightroute

Contains the

Flights Arrival

Time

11 seats Integer flightrouteContains the no. of

seats in Plane.

12 scheme_id Integer scheme

Contains the

Scheme ID of the

Scheme.

13 scheme_name String scheme

Contains the name

of the Discount

Scheme.


30/47

Sr.No.

Field Name Data Type Table Name Description

14 scheme_desc String scheme

Contains the

Details and

Description of

the Scheme.

15 discount Integer scheme

Contains the

Scheme

Discount.

16 passenger_id Integer passenger

Contains the

Passenger ID

no.

17 name Text passenger

Contains the

Passenger

Name.

18 gender Text passengerContains the

Passengers sex.

19 nationality text passenger

Contains the

Passengers

Nationality

20 ticket_id Integer passengerticket

Contains the

Passengers

Ticket ID.

21 class_type Text passengerticket

Contains the

class-type of the

ticket.

22 fare_paid Integer passengerticket

Contains the

fair paid by thePassenger

23 j_date Date/Time passengerticketContains the

Jorney Date.

24 cancel_no Integer cancelContains the

cancellation no.

25 Cancel_date Date/Time cancel

Contains the

ticket

Cancellation

Date.


31/47

FILE DESIGN


32/47

FILE DESIGN

1. Table Name: Airport

Description: Contains all Details aboutAirport Record.

2. Table Name: Route

Description: Contains all Details about

Air-Route Record.

Field Name Data type

route_id Number

start_ap Number

end_ap Number

miles Number

3. Table Name: Flightroute

Field Name Data typeairport_id Number

airport_name Text

Address Text

city Text

country Text


33/47

Description: Contains all Details aboutFlight-Route Record.


flight_id Number

start_time Date/Time

end_time Date/Time

s_airport Number

e_airport Number

miles Number

First Number

Business Number Economy Number

4. Table Name: Scheme

Description: Contains all Details aboutthe Ticket Scheme and discounts.


scheme_id Number

scheme_name Text

period Number

scheme_desc Text

scheme_disc Number

5. Table Name: Passenger

Description: Contains all Details aboutPassenger.


passenger_id Number

passport_no Text

name Text

address Textage Number


34/47

gender Text

email_id Text

nationality Text

6. Table Name: Passengerticket

Description: Contains all Details aboutPassengers ticket.

Field Name Data typeticket_id Number

passenger_id Number

scheme_id Number

class_type Text

fare_paid Number

flight_id Number

j_date Date/Time

7. Table Name: Cancel

Description: Contains all Details aboutTicket cancellation Record.

Field Name Data typecancel_no Number

date Date/Time

ticket_id Number


35/47

SOFTWARE TESTING AND

IMPLEMENTATION


36/47

SOFTWARE TESTING ANDIMPLEMENTATION

Software testing is the process of executing aprogram with an objective of finding an error.Software quality should be primary concerned insoftware development efforts. Software testing &evaluation are traditional methods of checkingsoftware quality. Software testing is successfullyonly if all errors from it are removed. The techniquethat finds max errors is good testing techniques.The prime objective of testing is to test the codewith 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:

InputsOutputs


37/47

BBT is related with input and output with

internal structure of program. In BBT it is checked ifsome input is given, then whether specific output isproduced by the programs or not. Various sets ofinput test cases are prepared and applied on aprogram & corresponding output produced.

BBT is used to find errors like:

1. Incorrect & missing functions2. Interfacing errors3. Initialization & termination errors4. Errors in external database access5. Performance errors

2. WHITE BOX TESTING:

WBT is related with the structure ofprogram.To test the logic of the program, various tests aredesigned 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 toensure their validity.

3. PERFORMANCE TESTING:

Performance testing determines the

length of system used by the system to processtransaction data. This test is conducted prior to


38/47

implementation to determine how long it takes toget response to an query, make a backup copy of afile. Performance testing is designed to test runtime performance of software within context of an

integrated system. Performance testing is carriedout 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 thesystem. It verifies that system procedures operateto system specification & that integrity of importantdata is maintained. Compressive test report isprepared.

5. STRESS TESTING:

It determines whether the system will

handle the volume of activities that occur when thesystem is at peak of the processing demand. E.g.Test the system by activating all the terminals ofthe system at the same time. The main goal of thestress testing is to test performance of the systemunder max use of memory, disk space.


39/47

HARDWARE AND SOFTWAREREQUIREMENTS

Minimum Software Requirements:

Software is the collections of programs. For

running of the system Software is needed.

Operating System : Windows 98/ 2000/ XP/

Vista. Application : Microsoft Access.

Editor : Notepad.

Software : 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 : 128 MB

Hard Disk : 20GB ( 2GB free Hard Disk

Space)


40/47

Display Type : Standard VGA Monitor

Printer : Inkjet / Laser

Mouse : Standard PS/2 compitable

mouse

Keyboard : Standard 101/102-key

Keyboard.

CD Rom , CD Writer

SYSTEM FEATURE


41/47

SYSTEM FEATURE

While designing system, it has tobe internally manipulated all aspects i.e.

logical flow of data to user. The system

provides effect functionally with inbuilt

triggers and constraints user at database

level. They reduce chances of entering

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.


42/47

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


43/47

DRAWBACKS ANDLIMITATIONS

The system has some drawbacks andlimitations 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.


44/47

Human mistakes due to inefficiency,

fatigue, lack of time and rectification

needed due to manual work.

CONCLUSION


45/47

CONCLUSION

THE SYSTEM WILL MAKE DAILY

TRANSACTION IN SHORT TIME & REPORT

GENERATED VERY EASILY & CORRECTLY

WHICH WAS SO COMLICATED IN PREVIOUS

MANUAL SYSTEM BECAUSE EVERYTHING

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


46/47

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.


47/47

5. JAVA SCRIPT & JSCRIPT:

-By Jowrski.

Documents

Synopsis & SRS