A

Project Report

INDIAN AIRLINES
In fulfillment of MCA

Indian Airlines

Submitted by:

VIKAS KUMAR BHARTI (200900106)

&

YENGKHOM DEEPAK KUMAR (200900111)

Submitted to:
Mrs. PALIKA CHOPRA
(Course co-ordinator)

THAPAR UNIVERSITY, PATIALA-147004

1
 What is a Software Requirements Specification?

An SRS is basically an organization's understanding (in writing) of a customer or potential

client's system requirements and dependencies at a particular point in time (usually) prior to
any actual design or development work. It's a two-way insurance policy that assures that both
the client and the organization understand the other's requirements from that perspective at a
given point in time. The SRS document itself states in precise and explicit language those
functions and capabilities a software system (i.e., a software application, an ecommerce Web
site, and so on) must provide, as well as states any required constraints by which the system
must abide. The SRS also functions as a blueprint for completing a project with as little cost
growth as possible. The SRS is often referred to as the "parent" document because all
subsequent project management documents, such as design specifications, statements of
work, software architecture specifications, testing and validation plans, and documentation
plans, are related to it. It's important to note that an SRS contains functional and
nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to
technology or business issues, or any other information other than what the development
team understands the customer's system requirements to be. A well-designed, well-written
SRS accomplishes four major goals:

 It provides feedback to the customer. An SRS is the customer's assurance that the
development organization understands the issues or problems to be solved and the
software behavior necessary to address those problems. Therefore, the SRS should be
written in natural language (versus a formal language, explained later in this article),
in an unambiguous manner that may also include charts, tables, data flow diagrams,
decision tables, and so on.

 It decomposes the problem into component parts. The simple act of writing down
software requirements in a well-designed format organizes information, places
borders
around the problem, solidifies ideas, and helps break down the problem into its
component parts in an orderly fashion.

2
 It serves as an input to the design specification. As mentioned previously, the SRS
serves as the parent document to subsequent documents, such as the software design
specification and statement of work. Therefore, the SRS must contain sufficient detail
in the function system requirements so that a design solution can be devised.

 It serves as a product validation check. The SRS also serves as the parent document
for testing and validation strategies that will be applied to the requirements for
verification

.
SRSs are typically developed during the first stages of "Requirements Development,"
which is the initial product development phase in which information is gathered about
what requirements are needed--and not. This information-gathering stage can include
onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-investment
(ROI) analysis or needs analysis of the customer or client's current business
environment. The actual specification, then, is written after the requirements have
been gathered and analyzed.

3
 PREFACE

We feel great pleasure in doing our project “INDIAN AIRLINES”.

This project is all about the “Marketing initiatives taken by Indian Airlines” with a rapidly
changing technological, social, economical, political-legal and the trend towards
globalization of business and industry, emerging of various private airlines; effective
marketing management has become a very challenging job.

In this project we have analyzed the different promotional fares implemented by Indian
Airlines and have feedback regarding their effectiveness and whether they should continued
or discontinued on different sectors.

4
 CONTENT
1. Introduction
o Indian airline – a profile 4
o Fleet 4
o Indian airlines network 6
2. Problem definition
o Manual system
o Technical system
o Need of Airline system
3. Feasibility Study
o Economical feasibility 7
o Technical feasibility 7
o Operational feasibility 7
4. Specific Requirements
o Hardware Requirements 9
o Software Requirements 9
 Operating system
 Microsoft Visual Basic 6.0 11
 Microsoft Access 13
5. System Analysis
o Block diagram 15
6. System design
o Entity set 16
o Relation set 16
o Data flow 16
o Process condition 16
7. Data Flow Diagram
o Level 0 data flow diagram 17
o Level 1 data flow diagram
o Level 2 data flow diagram
o Level 4 data flow diagram
8. Additional Comments 18

5
o

6
 INDIAN AIRLINES – A PROFILE

The airline is set up under the Air Corporations Act, 1953 with an initial capital of Rs. 32
million and started operations on 1 August 1953. It was established after legislation came into
force to nationalize the entire airline industry in India. Two new national airlines were to be
formed along the same lines as happened in the United Kingdom with British Overseas
Airways Corporation (BOAC) and British European Airways (BEA). Air India took over
international routes and Indian Airlines Corporation (IAC) took over the domestic and
regional routes.
Indian Airlines Corporation inherited a fleet of 99 aircraft including 74 Douglas DC-3
Dakotas, 12 Vickers Vikings, 3 Douglas DC-4s and various smaller types from seven airlines
that made it up.
Fleet

Indian Airlines operates an all-Airbus fleet consisting of the Airbus A320 family. As of
March 2009 the average age of Indian Airlines' fleet was 12.58 years.

Indian Airlines Fleet

Passengers
In Order
Aircraft (Business/Economy Notes
Service s
)

2 120 (14/106)
Airbus 5 dry leased.
19 – 122 (8/114)
A319-100 Widescreen PTV with AVOD.
3 144 (0/144)

24 dry leased.
Airbus
43 4 146 (20/126) Current fleet of old A320-200s due to
A320-200
be replaced by 2014.

Airbus
19 1 172 (20/152) Widescreen PTV with AVOD.
A321-200

Total 86 5

7
 Indian
इंडियन

IATA ICAO Call sign

IC IAC INDAIR

Founded 1953
Hubs Indira Gandhi International Airport
Secondary hubs  Chhatrapati Shivaji International
Airport
 Chennai International Airport
 Netaji Subhash Chandra Bose
International Airport

Focus cities  Ahmedabad

 Bangalore
 Hyderabad

Frequent flyer program Flying Returns

Alliance Star India Regional
Fleet size 95
Destinations 64 excel. Subsidiaries
Company New Horizons. Enduring
Slogan Values
Parent company NACIL
Headquarters Mumbai, India
Website www.indianairlines.in

8
INDAIN AIRLINES NETWORK

9
 PROBLEM DEFINTION

The definition of our problem lies in manual system and a fully automated system.

Manual system : The system is very time consuming and lazy. This system is
more prone to errors and sometimes the approach to various problems is unstructured.

Technical system : With the advent of latest technology if we do not update our
system then our business result in losses gradually with time. The technical contains the tools
of latest trend i.e. computers printers, fax, Internet etc. The system with this technology is
very fast, accurate, user-friendly and reliable.

Need of Airlines system

A few factors that direct us to develop a new system are given below:-

1. Faster system
2. Accuracy
3. Reliability
4. Informative
5. Reservation and cancellations from anywhere to any pace

AIRLINES SYSTEM

RESERVATION CANCELLATION

UPDATE

10
 FEASIBILITY STUDY

Feasibility study is to check the viability of the project under consideration. Theoretically
various types of feasibilities are conducted, but we have conducted three types of feasibilities
explained as under.

ECONOMIC FEASIBILITY

With the manual system the operating cost of the system is about 60 Lacks P.A. This cost
comprises salary of 25 people, stationary, building rent, electricity, water, telephone etc. But
with the new system this reoccurring cost comes out to be about 20 lacks P.A. Hence the new
system is economically feasible.

TECHNICAL FEASIBILITY

The new system requires only 6 trained people to work with the system and in overall 10
people per office is sufficient. So we will identify 6 best people from existing system and
train them.

As our existing system is purely manual, so we need a onetime investment of Rs 4 Lacks for
the purchase of 7 computers, 5 Ticket printers, a laser printer, AC and networking etc. It
requires 20 Lacks P.A. as an operating cost.

With the above details our system is technically feasible as after investing 24 lacks in a year,
the company is still saving Rs 25 Lacks P.A.

OPERATIONAL FEASIBILITY

The new solution is feasibility in all sense but operational it is not. The new system demands
the expulsion at least 15 people from the company. It creates an environment of joblessness
and fear among the employees. It can lead to an indefinite strike in the company also. So the
management must take corrective actions prior in advance in order to start the further
proceedings.

11
 SPECIFIC REQUIREMENTS

1. HARDWARE REQUIREMENTS

The basic hardware we use for complete our project on “INDIAN AIRLINES” is given
below:-

PROCESSOR : Intel® Core™ 2 duo T6600 @ 2.20 GHz

MEMORY : 2008 MB

HDD : 320 GB

CD ROM : Sony

SCREEN : 800 X 600 is basic screen resolution.

PRINTER : hp

2. SOFTWARE REQUIREMENTS

Operating system:

 Windows XP or Windows Vista home basic

Microsoft visual Basic:

History: -VB 1.0 was introduced in 1991. The drag and drop design for creating the user
interface is derived from a prototype form generator developed by Alan Cooper and his
company called Tripod. Microsoft contracted with Cooper and his associates to develop
Tripod into a programmable form system for Windows 3.0, under the code name Ruby (no
relation to the Ruby programming language).

Tripod did not include a programming language at all. Microsoft decided to combine Ruby
with the Basic language to create Visual Basic.

The Ruby interface generator provided the "visual" part of Visual Basic and this was
combined with the "EB" Embedded BASIC engine designed for Microsoft's abandoned
"Omega" database system. Ruby also provided the ability to load dynamic link libraries
containing additional controls (then called "gizmos"), which later became the VBX interface.

12
Language Feature: Like the BASIC programming language, Visual Basic was designed to
be easily learned and used by beginner programmers. The language not only allows
programmers to create simple GUI applications, but can also develop complex applications.
Programming in VB is a combination of visually arranging components or controls on a
form, specifying attributes and actions of those components, and writing additional lines of
code for more functionality. Since default attributes and actions are defined for the
components, a simple program can be created without the programmer having to write many
lines of code. Performance problems were experienced by earlier versions, but with faster
computers and native code compilation this has become less of an issue.

Although programs can be compiled into native code executables from version 5 onwards,
they still require the presence of runtime libraries of approximately 1 MB in size. This
runtime is included by default in Windows 2000 and later, but for earlier versions of
Windows like 95/98/NT it must be distributed together with the executable.

Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g., text
boxes, buttons, etc.) on the form (window). Controls have attributes and event handlers
associated with them. Default values are provided when the control is created, but may be
changed by the programmer. Many attribute values can be modified during run time based on
user actions or changes in the environment, providing a dynamic application. For example,
code can be inserted into the form resize event handler to reposition a control so that it
remains centered on the form, expands to fill up the form, etc. By inserting code into the
event handler for a key press in a text box, the program can automatically translate the case of
the text being entered, or even prevent certain characters from being inserted.

Visual Basic can create executables (EXE files), ActiveX controls, or DLL files, but is
primarily used to develop Windows applications and to interface database systems. Dialog
boxes with less functionality can be used to provide pop-up capabilities. Controls provide the
basic functionality of the application, while programmers can insert additional logic within
the appropriate event handlers. For example, a drop-down combination box will
automatically display its list and allow the user to select any element. An event handler is
called when an item is selected, which can then execute additional code created by the
programmer to perform some action based on which element was selected, such as populating
a related list.

Alternatively, a Visual Basic component can have no user interface, and instead provide
ActiveX objects to other programs via Component Object Model (COM). This allows for
server-side processing or an add-in module.

The language is garbage collected using reference counting, has a large library of utility
objects, and has basic object oriented support. Since the more common components are
included in the default project template, the programmer seldom needs to specify additional
libraries. Unlike many other programming languages, Visual Basic is generally not case
sensitive, although it will transform keywords into a standard case configuration and force the
case of variable names to conform to the case of the entry within the symbol table. String
comparisons are case sensitive by default, but can be made case insensitive if so desired.

The Visual Basic compiler is shared with other Visual Studio languages (C, C++), but
restrictions in the IDE do not allow the creation of some targets (Windows model DLLs) and
threading models.

13
Microsoft Access:-

History: Access version 1.0 was released in 13 November 1992, quickly followed in
May 1993 by an Access 1.1 release to improve compatibility with other Microsoft products
and include the Access Basic programming language.

Microsoft specified the minimum hardware requirements for Access v2.0: Microsoft
Windows v3.1 with 4 MB of RAM required, 6 MB RAM recommended; 8 MB of available
hard disk space required, 14 MB hard disk space recommended. The product was shipped on
seven 1.44 MB diskettes. The manual shows a 1993 copyright date.

Originally, the software worked well with relatively small databases but testing showed some
circumstances caused data corruption. For example, file sizes over 10 MB were problematic
(note that most hard disks were smaller than 500 MB at the time this was in wide use), and
the Getting Started manual warns about a number of circumstances where obsolete device
drivers or incorrect configurations can cause data loss. With the phasing out of Windows 95,
98 and ME, improved network reliability, and Microsoft having released 8 service packs for
the Jet Database Engine, the reliability of Access databases has been vastly improved in both
size and number of users.

With Office 95, Microsoft Access 95 became part of the Microsoft Office Professional Suite
joining Microsoft Excel, Word, and PowerPoint and transitioning from Access Basic to
Visual Basic for Applications (VBA). Since then, there have been releases of Microsoft
Access with each release of Office. This includes Access 97 (version 8.0), Access 2000
(version 9.0), Access 2002 (version 10.0), Access 2003 (version 11.5), and Access 2007
(version 12.0).

The native Access database format (the Jet MDB Database) has also evolved over the years.
Formats include Access 1.0, 1.1, 2.0, 95, 97, 2000, 2002, and 2007. The most significant
transition was from the Access 97 to the Access 2000 format; which is not backward
compatible with earlier versions of Access. At the time of this writing, all newer versions of
Access support the Access 2000 format. New features were added to the Access 2002 format
which can be used by Access 2002, 2003, and 2007.

In Access 2007, a new database format was introduced: ACCDB. The ACCDB supports
complex data types such as multivalve and attachment fields. These new field types are
essentially record sets in fields and allow the storage of multiple values in one field.

Prior to the introduction of Access, the desktop database market was dominated by Borland
with their Paradox and dBase programs, and FoxPro. Microsoft Access was the first mass
market database program for Windows. With the purchase of FoxPro and incorporating its
Rushmore query optimization routines into Access, Microsoft Access quickly became the
dominant database for Windows effectively eliminating the competition which failed to
transition from the MS-DOS world.

14
Access's initial codename was Cirrus; the forms engine was called Ruby. This was before
Visual Basic - Bill Gates saw the prototypes and decided that the BASIC language
component should be co-developed as a separate expandable application, a project called
Thunder. The two projects were developed separately as the underlying forms engines were
incompatible with each other; however, these were merged together again after VBA.

Features: - Users can create tables, queries, forms and reports, and connect them together
with macros. Advanced users can use VBA to write rich solutions with advanced data
manipulation and user control.

The original concept of Access was for end users to be able to “access” data from any source.
Other uses include: the import and export of data to many formats including Excel, Outlook,
ASCII, dBase, Paradox, FoxPro, SQL Server, Oracle, ODBC, etc. It also has the ability to
link to data in its existing location and use it for viewing, querying, editing, and reporting.
This allows the existing data to change and the Access platform to always use the latest data.
It can perform heterogeneous joins between data sets stored across different platforms.
Access is often used by people downloading data from enterprise level databases for
manipulation, analysis, and reporting locally.

There is also the Jet Database format (MDB or ACCDB in Access 2007) which can contain
the application and data in one file. This makes it very convenient to distribute the entire
application to another user, who can run it in disconnected environments.

One of the benefits of Access from a programmer's perspective is its relative compatibility
with SQL (structured query language) — queries can be viewed graphically or edited as SQL
statements, and SQL statements can be used directly in Macros and VBA Modules to
manipulate Access tables. Users can mix and use both VBA and "Macros" for programming
forms and logic and offers object-oriented possibilities. VBA can also be included in queries.

Microsoft Access offers parameterized queries. These queries and Access tables can be
referenced from other programs like VB6 and .NET through DAO or ADO. From Microsoft
Access, VBA can reference parameterized stored procedures via ADO.

The desktop editions of Microsoft SQL Server can be used with Access as an alternative to
the Jet Database Engine. This support started with MSDE (Microsoft SQL Server Desktop
Engine), a scaled down version of Microsoft SQL Server 2000, and continues with the SQ
Server Express versions of SQL Server 2005 and 2008.

Microsoft Access is a file server-based database. Unlike client-server relational database

management systems (RDBMS), Microsoft Access does not implement database triggers,
stored procedures, or transaction logging. Access 2010 (not released) does have table level
triggers and stored procedures built into the ACE data engine.

15
 SYSTEM ANALYSIS

This was the most important phase of my project life cycle. It had connected my maximum
time. The block diagram given bellow depict various fact were understood by one during the
analysis phase.

BLOCK DIAGRAM

BOOKING
DEPARTMENT

Flight maintenance D Receive customer request

Booking, cancellation AIRLINE Passenger list and confirm list
RESERVATION
SYSTEM
PASSENGER REPORT

Waiting list &

Cancellation
Data storage Data access

DATA BASE
Ticket reservation Passenger list
Cancellation, fleet info
Request for inquiry flight information & faire details

16
 SYSTEM DESIGN

In this phase initially designed E-R diagram of the process , in order to identify various
entities and relationship set, entity set, attributes, link attributes. The diagram of this process
as under

Relationship set
Entity set

Condition checking

Direction of data flow

17
 DATA FLOW DIAGRAM
In order to design a better solution we had designed the DFD (Data Flow Diagram) for
system including all technical processing detail is given below.

LEVEL 0 DATA FLOW DIAGRAM

REQUEST FOR INFORMATION FLIGHT/FARE/DISCOUNT

PASSENGER
INFORMATION

1.0 GENERAL ENQUARY

BOOKING ENQUARY

2.0 PASSENGER ENQUARY

NEW PNR INFO

RESERVATION
REQUEST
3.0 BOOKING ENQUARY

TICKET CONFORMATION
& STATUS

CANCELLATION REQUEST 4.0 CANCELLATION

ACKNOWLEGMENT

18
 ADDITIONAL COMMENTS

 Compactness: - The project describes the various procedures that are defined in a
rigid and enterprising way to the user.

 Speed: - The speed of the project is tremendous and works on a platform which is
very convenient and efficient to work on and provides the user with speed which is
better than good.

 Portability: - The project we developed at our workstation is portable at all the other
system and can be transferred from one computer to another with little or no
modification at all.

 Time saving: - The process is quite time saving due to the various categories that
have been included. A general knowledge about computers let the user share the full
experience.

**********THE END**********

19