Management Information System

file on Indian Air Force

DELHI INSTITUTE OF RURAL DEVELOPMENT
AFFILATED TO GURU GOBIND SINGH INDRAPRASTHA
UNIVERSITY,
NEW DELHI

BACHELOR OF BUSINESS ADMINISTRATION

(2013-2016)

SUBMITTED TO: -

SUBMITTED BY:-

Ms. Neha Sabharwal

KARAN NAGPAL

(ASST. PROFESSOR)

Roll No: 05312401713

CERTIFICATE

This is to certify that KARAN NAGPAL, student of DELHI INSITUTE OF

RURAL DEVELOPMENT has completed her file of Computer Applications in
the year 2015 in final fulfilment of Bachelor of Business Administration (BBA).
She has successfully completed the file under my constant guidance and
support.

_______________________
Ms. Neha Sabharwal
(ASST. PROFESSOR)

ACKNOWLEDGEMENT
There is always a sense of gratitude which one express for others for their help and
supervision for achieving the goals. I too express my deep gratitude to each and everyone
who has been helpful to me for completing the file successfully.
I am highly obliged to our department who provided me necessary help in completion of the
file and all the staff members of the department. My regards and sincere thanks to our
worthy department who has shaped my understanding through their rich varied suggestions.
Above all no words can express my feelings to my parents, friends all those persons who
supported me during my file. I am also thankful to all the respondents whose cooperation and
support has helped me a lot in collecting necessary information.

STUDENT DECLARATION

This is to certify that I have completed the MIS Project titled Indian Air force under the
guidance of Ms. Neha Sabharwal in the partial fulfilment of the requirement for the award of
the degree of Bachelor in Business Administration from Delhi Institute of Rural
Development, New Delhi. This is an original work and I have not submitted it earlier
elsewhere.

Place: DELHI

Name- Karan nagpal

Enrol. No:- 05312401713
Batch: 2013-2016

INDIAN AIRFORCE SYSTEM

INTRODUCTION
The Indian Air Force (IAF; Devangar: , Bharatiya Vyu Sen) is the air
arm of the Indian armed forces. Its the World's 4th largest Airforce. Its primary responsibility
is to secure Indian airspace and to conduct aerial warfare during a conflict. It was officially
established on 8 October 1932 as an auxiliary air force of the British Empire and the prefix
Royal was added in 1945 in recognition of its services during World War II. After India
became independent from the United Kingdom in 1947, the Royal Indian Air Force served
the Dominion of India, with the prefix being dropped when India became a republic in 1950.
Since independence, the IAF has been involved in four wars with neighbouring Pakistan and
one with the People's Republic of China. Other major operations undertaken by the IAF
include Operation Vijay, Operation Meghdoot, Operation Cactus and Operation Poomalai.
Apart from conflicts, the IAF has been an active participant in United Nations peacekeeping
missions.
The President of India Pranab Mukherjee serves as the ex-officio Commander-in-Chief of the
IAF. The Chief of Air Staff, an Air Chief Marshal (ACM), is a four-star commander and
commands the Air Force. There is never more than one serving ACM at any given time in the
IAF. The rank of Marshal of the Air Force has been conferred once, to Arjan Singh, by the
President of India on 26 Jan 2002 and he became first five-star rank holding officer of IAF &
serves as the ceremonial chief.

In its publication the Military Balance 2010, the International Institute for Strategic Studies
(IISS) estimates that the Indian Air Force has a strength of 127,000 active personnel.
However, various reliable sources provided notably divergent estimates of its strength over
the years. Flightglobal (Flight International) estimates there to be around 1,820 aircraft in
service with the IAF. 905 Combat Planes ( 595 Fighters & 310 Attackers).[1]
Problems concerning the defence of India were reassessed in 1939 by the Chatfield
Committee. It proposed the re-equipment of RAF (Royal Air Force) squadrons based in
lndia but did not make any suggestions for the accelerating the then painfully slow growth of
IAF except for a scheme to raise five flights on a voluntary basis to assist in the defence of
the principal ports. An IAF Volunteer Reserve was thus authorised, although equipping of the
proposed Coastal Defence Flights (CDFs) was somewhat inhibited by aircraft availability.
Nevertheless, five such flights were established with No. 1 at Madras, No. 2 at Bombay, No.
3 at Calcutta, No. 4 at Karachi and No. 5 at Cochin. No. 6 was later formed at
Vizagapatanam. Built up around a nucleus of regular IAF and RAF personnel, these flights
were issued with both ex-RAF Wapitis and those relinquished by No. 1 Squadron IAF after
its conversion to the Hawker Hart. In the event, within a year, the squadron was to revert
back to the Wapiti because of spares shortages, the aged Westland biplanes being
supplemented by a flight of Audaxes.
At the end of March 1941, Nos. 1 and 3 CDFs gave up their Wapitis which were requisitioned
to equip No. 2 Squadron raised at Peshawar in the following month, and were instead issued
with Armstrong Whitworth Atalanta transports, used to patrol the Sunderbans delta area south
of Calcutta. No. 2 CDF had meanwhile received requisitioned D.H. 89 Dragon Rapides for
convoy and coastal patrol, while No. 5 CDF took on strength a single D.H. 86 which it used
to patrol the west of Cape Camorin and the Malabar Coast. Meanwhile the creation of a
training structure in India became imperative and RAF flying instructors were assigned to
flying clubs to instruct IAF Volunteer Reserve cadets on Tiger Moths.364 pupils were to
receive elementary flying training at seven clubs in British India and two in various princely
States by the end of 1941. Some comparative modernity was infused in August 1941, when
No. 1 Squadron began conversion to the Westland Lysander at Drigh Road, the Unit being
presented with a full establishment of 12 Lysanders at Peshawar by the Bombay War Gifts
Fund in the following November. No. 2 Squadron had converted from the Wapiti to the
Audax in September 1941 and, on 1 October No. 3 Squadron, similarly Audax-equipped, was
raised at Peshawar.

The IAF VR was now inducted into the regular IAF, the individual flights initially retaining
their coastal defence status, but with Japan's entry into the war in December, No. 4 Flight,
with four Wapitis and two Audaxes, was despatched to Burma to operate from Moulmein.
Unfortunately, four of the flight's six aircraft were promptly lost to Japanese bombing and,
late in January 1942, No. 4 Flight gave place in Moulmein to No. 3 Flight which had
meanwhile re-equipped with four ex-RAF Blenheim ls. For a month, these Blenheims were to
provide almost the sole air cover for ships arriving at Rangoon harbour.
The Motto of Indian Air Force has been taken from eleventh chapter of the Gita, the
Discourse given by Lord Krishna to Arjuna on the battlefield of Kurukshetra during the Great
War of Mahabharata. The Lord is showing His Supreme Divine form to Arjuna and the great
form of the Lord is reaching the sky with glory, evoking fear and loss of self-control in the
mind of Arjuna.The Indian Air Force, similarly, aims to overwhelm the adversaries with
application of aerospace power in defence of the nation.
The Indian Air Force (IAF) today, having completed the Platinum Jubilee of dedicated
service to the nation, is a modern, technology-intensive force distinguished by its
commitment to excellence and professionalism. Keeping pace with the demands of
contemporary advancements, the IAF continues to modernise in a phased manner and today it
stands as a credible air power counted amongst the fore-most professional services in the
world.
The primacy of Air Power will be a decisive factor in shaping the outcome of future conflicts.
In line with this dictum, the Indian Air Force (IAF) has developed into a major 'Component
of National Power', which can be applied quickly and decisively. The IAF has reoriented
itself to a multi-role capability of platforms and equipment, along with multi-skill capability
of personnel. The rapid economic growth of the country dictates the need to protect our
security interests extending from the Persian Gulf to the Straits of Malacca.
Over the years the IAF has grown from a tactical force to one with transoceanic reach. The
strategic reach emerges from induction of Force Multipliers like Flight Refuelling Aircraft
(FRA), Remotely Piloted Aircraft (RPA) and credible strategic lift capabilities. There is
emphasis on acquiring best of technology through acquisitions or upgradation, be it aircraft,
systems, precision missiles or net centricity. The main inductions and acquisitions by Indian
Air Force are given in the following paras.
IAF has started upgrading its combat aircraft fleet since the last few years in order to enhance
its operational capability and maintain its aircraft as modern weapon platforms, capable of
meeting the present challenges posed by the security scenario in our region. Of the available
fleet, MiG-21, MiG-27 and Jaguar aircraft have already been upgraded and Mirage-2000 and
MiG-29 aircraft are planned for upgradation. The Indian Air Force is considering upgrade of
its medium lift helicopters comprising Mi-8, Mi-17 and Mi-17-IVs, as also the AN - 32
transport aircraft, with the aim of improving their overall capability.
The IAF today is in the process of a most comprehensive modernisation plan. Over the next
few years, the force would induct more Su-30 MKI aircraft, the Light Combat Aircraft (LCA)
and the Medium Multi Role Combat Aircraft (MMRCA). There are plans to augment the
helicopter and transport fleets too. The IAF is also in the process of acquiring radars in
various categories to meet the Air Defence requirements, accurate and advanced weapons,

Network
Centric
Warfare
systems,
etc,
to
meet
its
assigned
tasks.
The Indian Air Force has seven commands, of which five are operational and two functional,
namely:
HQ Central Air Command, Allahabad
HQ Eastern Air Command, Shillong
HQ Western Air Command, New Delhi

OBJECTIVES
Our project introduces Indian Air Force system with an objective to make the system
more efficient, easier and fast. This project explores how computer technology can be
used to solve the problem of user.

The main objectives provided by this software are as follows:

The objective of Indian Air Force system is to give structural design to Indian air
force system.

The project provides functionality and flexibility to air force system such that one
can operate that system easily and efficiently.

This project also provides a complete set of solutions for some common and
specific areas of work in the air force system.

To provide customers of passenger services with reliable and accurate information

that is updated as new.

To improve and move towards the standardisation of the information and to provide
real time air force system.

To provide immediate results to various queries.

This project is dedicated to model existing Indian Air Force systems that aim at
development of Indian Air Force System that facilitates the air force customer to manage their
reservations.

IMPLEMENTATION (SRS)

Introduction: The introduction of the Software Requirement Specification states

the goals and objectives of the software, describing it in context of the computer
based system.

Information Description: It provides detailed description of the problem that the

software must solve. Information content, flow and structure are documented.
Hardware, Software and human interfaces are described for external system elements
and internal software functions.

Functional Description: A processing narrative is provided for each function,

design constraints are stated and justified, performance characteristics are stated, and
one or more diagrams are included to graphically represent the overall structure of the
software and interplay among software and other system elements.

Behavioral Description: This section of the SRS examines the operation of

software as a consequence of external events and internally generated control
characteristics.

Validation Criteria: It is probably the most important and ironically the most
often neglected section of the Software Requirement Specification. The section is

neglected because completing it demands a thorough understanding of the software

requirements. Specification of validation criteria acts as an implicit review of all other
requirements, so it is essential that time and attention is given to this section.

Bibliography and references: It is also important to put all the important

references at the end of the document so that any other programmer or user can refer
to them in case of any confusions or problems.

HARDWARE CONFIGURATION

Definition of Hardware:
Computer hardware is the collection of physical elements that constitutes a computer
system. Computer hardware refers to the physical parts or components of a computer such as
the monitor, mouse, keyboard, computer data storage, hard drive disk (HDD), system unit
(graphic cards, sound cards, memory, motherboard and chips), etc. all of which are physical
objects that can be touched.[1] In contrast, software is instructions that can be stored and run
by hardware.
Minimum Hardware Requirements for our Program
PROCESSOR: Pentium IV processor or Greater
RAM: 128 Mega Byte (MB) or Greater
HARDDISK: 1.2 Giga Byte (GB) or Greater
Keyboard & Mouse
MONITOR: Colour (For Best Result)
Printer

SOFTWARE CONFIGURATION

Definition of software:
Computer software, or just software, is any set of machine-readable instructions that directs
a computer's processor to perform specific operations. The term is used to contrast with
computer hardware, the physical objects (processor and related devices) that carry out the
instructions. Computer hardware and software require each other and neither can be
realistically used without the other.

Minimum Software Requirements for our Program

Operating System: Windows 2000/ XP /7
Supported Browser: Google chrome/Internet Explorer/ Mozilla Firefox / Opera

SDLC
System Development Life Cycle (SDLC) is the overall process of developing information
systems through a multi-step process from investigation of initial requirements through
analysis, design, implementation and maintenance.

MODEL

THE RAD MODEL (Rapid application development)

Rapid application development (RAD) is an incremental software development

lifecycle process model that emphasizes an extremely short development lifecycle.

The RAD model is a high-speed adaptation of linear sequential model in which

rapid development is achieved by using component based construction.

If the requirements are well understood and project scope is constrained, the RAD
process enables a development team to create a fully functional system within short
time periods (e.g., 60 to 90 days).

THE RAD MODEL

Business Modelling: The information flow among business function is model in a way that
answer the following question. What information drives the business process? What
information is generated? Who generates it?

Data Modelling: The information flow defined as a part of the business modelling phase is
refined into set of data objects that are needed to support the business. The characteristics
(called attributes) of each object are identified and relationship between these objects defined.

Process Modelling: The data objects defined in the data modelling phase are transformed to
achieve the information flow necessary to implement a business function. Processing
descriptions are created for adding, deleting, modifying, or retrieving a data object.

Application Generation:-RAD assumes the use of fourth generation techniques. Rather than
creating software using conventional third generation programming languages the RAD
process work to reuse existing program components. In all cases, automated tools are used to
facilitate construction of the software.

Testing And Turnover: Since the RAD process emphasizes reuse, many of the program
components have already been tested. This reduces overall testing time. However new
components must be tested and all interfaces must be fully exercised.
DISADVANTAGES:
For large but scalable projects, RAD requires sufficient human resources to create
the right number of teams.
If commitment fails, projects will fail.
RAD is not appropriate when technical risks are high.

FEASIBILITY STUDY
Feasibility Study is a step towards identification of the candidate system as a feasible
product. First the studies often pre-suppose that when the feasibility document is being
prepared, the analyst is in a position to evaluate solutions. Second, most studies tend to
overlook the confusion inherent in system development the constraints and the assumed
attitudes.
If the feasibility study is to serve as a decision document, it must answer three questions:

Is there a new and better way to do a job that will benefit the user?

What are the costs and savings of the alternatives?

What is recommended?

Feasibility Considerations:
There are three key considerations to the feasibility study:
1

Economic

Technical

Behavioral

FEASIBILITY ANALYSIS OF THE SYSTEM

Economic Feasibility:
The project was considered to be economically feasible because

The cost involved in developing the candidate system well under the budget of the
organization.

The Cost-Benefit Analysis tells us that the value of the benefits offered by the
proposed system is much higher than the cost.

Technical Feasibility:

The proposed system is technically feasible because all the necessary hardware and software
required for developing and installing the system is available with the organization.

Behavioral Feasibility:
The proposed system is also behaviorally feasible as it is very user friendly. Extensive
training of the users is not required. The users can easily learn to use the system and can
adapt themselves according to the system.

ANALYSIS

Analysis is the first technical step in the process of any software development. A careful
analysis can help the software designer and programmer to have a better insight of the
product to be created. A careless analysis can result into incomplete or dysfunctional
software. To avoid such a situation it is very important to properly identify the required
softwares features and create an effective design for it.
It is also important to analyze and find out whether the application being developed suits the
current hardware and software platform available or not. The application should be developed
well within time and should meet the specified requirements. If the application is being
developed for commercial purposes then a cost-benefit analysis becomes must to find out the
real value of the software product.

TECHNIQUES USED FOR ANALYSIS

On-Site Observations:

This is one of the main tools for gathering information. It is a process of recognizing and
noticing people, objects and occurrences to obtain information.
The major objective of this tools is to get as close as possible to the real system being studies.
For this reason it is extensively used by the system analyst during the development of a
particular system.

Guidelines for onsite observations

What kind of system is it?

Who are the important people in the system?

Who runs the system?

Apart from its formal function, what kind of system is it in comparison with other
systems in the organization? Is it primary or secondary contributor to the
organization?

It is to be kept in the mind that during observations the observer has to listen more than
talk and to listen with sympathetic and genuine interest when information is being
conveyed.

Types of observation methods:

Natural method :A natural observation occurs in a setting such as the users workplace.

Obtrusive method: An obtrusive observation takes place when the respondent knows
he/she is being observed.

Direct method: A direct observation takes place when the analyst actually observes
the subject or the system at work.

Structured and Unstructured method: In case of structured method, the observer looks
for and records a specific action. While in case of unstructured method the observer is
placed in a situation to observe whatever might be pertinent at that time.

Interviews and Questionnaires:

Interviews:
The interview is the face-to-face interpersonal meeting designed to identify relations and
capture information as it exists. It is flexible tool, offering a better opportunity than the
questionnaire to evaluate the validity of the information gathered.

This tool is used because it is a superior technique for capturing information as it exists and it
is also an exploratory device to identify or verify information.

Guidelines for interviews:

Who will be interviewed?

In what order will they be interviewed?

What specific questions will be asked in each interview?

Besides these, individual, group discussions can also be conducted, which can lead to
some frank expression of opinions and ideas.
During interviews it should be kept in mind that there is a proper coordination between
the interviewer and the interviewee so that the purpose of the interviews id fruitfully
fulfilled.

Questionnaires:
The questionnaire is a self-administrated tool that is more economical and requires less skill
to administer than the other methods. It examines a large number of respondents at the same
time, provides standardized wording and instructions, and places less pressure on subjects for
immediate responses.

SYSTEM DESIGN
DFDS
0 Level DFD

Up/down airline info

Passenger
Airline
Fill cancelation form
reserve/cancel info
Reservation
Fill reservation form
Passenger info

Admin

Ticket info
Waiting ticket info

1 Level DFD

Reservation
storage file

process
Passenger

Ticket
generation
process

Report to
admin
Enquiry

ER DIAGRAM

ticketno

gateno

Passenger
s
marshals

Gates

seat_assign

travels_on

has_seat

depart_ti
me

ddate

Seats

flights

dtime

flightno

SCREEN LAYOUT AND CODING

OUTPUT

seatno

CODING

OUTPUT

CODING

OUTPUT

CODING

OUTPUT

CODING

OUTPUT

CODING

OUTPUT

CODING

OUTPUT

CODING

TESTING STRATEGIES

A Strategy for software testing integrates software test case design methods into a wellplanned series of steps that result in the successful construction of software. The strategy
provides a read map that describes the steps to be conducted as part of testing. When these
steps are planned and then undertaken, and how much effort, time, and resources will be
required. Software is tested to uncover errors that were made inadvertently as it was designed
and constructed.
Testing is a set of activities that can be planned in advance and conducted systematically. For
this reason a template for software testing- a set of steps into which we can place specific test
case design techniques and testing methods- should be defined for the software process.
A number of software testing strategies have been proposed in the literature. All provide the
software developer with a template for testing and all have the following generic
characteristics:

To perform effective testing, a software team should conduct effective formal technical
reviews. By doing this, many errors will be eliminated before testing commences.
Testing begins at the component level and works outward toward the integration of
the entire computer-based system.
Different testing techniques are appropriate at different points in time.
The developer of the software and an independent test group conducts testing.
Testing and debugging are different activities, but debugging must be accommodated
in any testing strategy.

A testing strategy that is chosen by most software teams fall between the two extremes. It
takes an incremental view of testing. Beginning with the testing of individual program units,
moving to tests designed to facilitate the integration of the units and culminating with test
that exercise the constructed system. Ease of these classes of tests is described in the sections
that follow.

Unit testing

Unit testing focuses verification efforts on the smallest unit of software design-the software
component or module. Using the component-level design description as a guide, important
control paths as tested to uncover errors within the boundary of guide; important control
paths are tested to uncover error within the boundary of the module. The relative complexity
of tests and the errors those tests uncover is limited by the constrained scope established for
unit testing. The unit test focuses on the internal processing logic and data structure within
the boundaries of a component. This type of testing can be conducted in parallel for multiple
components.
Unit testing is simplified when a component with high cohesion is designed. When only one
function is addressed by a component, the number of test cases is reduced and errors can be
more easily predicted and uncover.

Integration testing
Integration testing is a systematic technique for constructing the software architecture while
at the same conducting tests to uncover errors associated with interfacing. The objective is to
take unit tested components and build a program structure that has been dictated by design.

Top-down integration: - Top down integration testing is an incremental approach to

construction of the software architecture. Modules are integrated by moving
downward through the control hierarchy, beginning with the main control module
(main program). Modules subordinate to the main control module are incorporated
into the structure in either a depth-first or breadth-first manner.

Bottom-up integration: -Bottom-up approach, as its name implies, begins

construction and testing with atomic module. Because components are integratedfrom
the bottom up, processing required for components subordinate to a given level is
always available and the need for stubs is eliminated.

SYSTEM MAINTENANCE

Maintenance phase on the focuses on changes that is associated with error correction,
adoption required as the softwares environment evolves and changes due to enhancement
brought about by changing customer requirements. Change will occur because errors have
been encounter or because the customer requires the functional, or the performance
enhancement.
Software maintenance replies each of the preceding phases to an existing phase rather than a
few one.

Corrective maintenance
Adaptive maintenance
Perfective maintenance
Preventive maintenance

Corrective maintenance
Even with the best quality assurance activities, it is likely that the customer will uncover the
defects in the software. Corrective maintenance changes the software to corrupt the defects.
After the customer uses the system, he can detect the errors in the system. These changes can
be easily accommodated in the system because it is well developed.

Adaptive maintenance
Over time, the original environment for which the software was developed is likely to change
adaptive maintenance results in modifications to the software to accommodate changes to its
external to its external environment.
As the external environment changing in the future, these changes can also be
accommodated. This system can run under any platform. The changes in the rule of
organization or in the government policies can also be accommodated.

Perfective maintenance
As software is used, the customer or user will recognize additional function that will provide
benefit. Perfective maintenance extends the software beyond its original functional
requirements.
The required functional also added to the system. This additional function enhance the system
functional and system becomes user friendlier.

Preventive maintenance

Computer software deteriorates due to change and because of this preventive maintenance
often called software Re-engineering, must be conducted to enable the serve the needs of its
end users. In essence, preventive maintenance makes changes to computer programs, so that
they can be more easily corrected, adapted and enhanced.
As changes are made, It is likely that some new defects will be introduced, causing the
failure. Before the failure is corrected another change is requested causing another failure.
Slowly, the minimum failure rate begins to rise and software is destroying due to change.
Every software indicates error in design is in process through the design was translated into
machine executable code. Therefore, software maintenance or system maintenance involves
more complexity than hardware maintenance. In the global sense, software Re-engineering is
often considered as part of business process of Re-engineering.

FUTURE SCOPE OF APPLICATION

1.
2.
3.
4.

Release Hindi version of the website.

Add facilities for international tourists.
Add facilities for pilgrims.
Provide facilities of 30 min call back on a miss call from registered
customers.
5. Add an additional feature for customer feedback.

BIBLIOGRAPHY

WEBSITE

http://www.w3schools.com/
http://indianairforce.nic.in/
http://careerairforce.nic.in/auth/candidate/new_candidate.asp
https://www.youtube.com/watch?v=8zXo_V6UQA0