Airline Management

System

1. INTRODUCTION
1.1 About the System
The Miles Acquisition System helps Airlines serve their fliers by
following a tailored version of the organizations standard process called The
Frequent Flyer Program. The goal of the MAS is to ensure that fliers login,
view and manage their acquired miles through a beautiful, user friendly frontend. This document records the transactions of the user like all the details of
his acquired miles in their airlines. Through this application, the Airlines can
automate the process of updating the various details associated with its
scheme for frequent fliers; thus, avoiding manual or telephonic overhead
involved in providing information and book keeping.
The user, by entering his unique user id and password, can login to his
account and avail the online services like checking the no. of miles acquired,
and the various benefits entitled to him for it. The airlines, on the other hand,
can make its announcements on new schemes to be introduced. This kind of
application over the internet enhances the chances of attracting new fliers as
well as retaining the old ones.
1.2 EXISTING SYSTEM:
The following are the features of an Existing System

The transactions are maintained manually.

There is no separate user to interact with the database.

Not very user friendly interface.

1.3 Need For Proposed System:

In existing system it is difficult to improve predictability, efficiency and
control of the entire Flier Transactions for Frequent Fliers. To overcome all
these, MAS has been developed. Since it is difficult to manually interact with

the records (files), our MAS has provided an interface to the database so that
an administrator can interact with the database and maintain the records
permanently. Administrator provides few services like My Miles, Spend Miles,
Earn Miles and Exchange Miles and some more facilities like Updating
Information. Some general services like change password and update profile
are also provided to users. Only authorized users are capable of modifying
details in their account and thereby providing security to all users.

1. System Analysis Concentration:

Before planning a replacing for a new system it is essential to have through
knowledge about the existing system along with estimation of how lost
computes can be used to make its operations more effective.
System analysis is the process of collecting and interpreting facts, disposing
problem and use the information about the existing system, which is also
called as system study.
System analysis is about understanding situation but not solving the problem.
System analysis is performed to determine whether a not it is feasible to
design and information system laved on the policies and plans of an
organization. To determine the user requirements and to eliminate the
weakness of the present system a few general requirements are concerned.
GENERAL REQUIREMENTS:
The new system should be cost effective
To improve productivity and service and services.
To enhance user interface.
To improve information presentation and durability.
To upgrade systems reliability, availability and flexibility.
To address human factors for better and uses acceptance.

SOFTWARE REQUIREMENT SPECIFICATION

REQUIREMENT SPECIFICATION:
The application Clinical Care System interface is designed to serve as the
common user interface between the banks.

INTRODUCTION
Purpose: The main purpose for preparing this document is to give a general
insight into the analysis and requirements of the existing system or situation
and for determining the operating characteristics of the system.
Scope: This Document plays a vital role in the development life cycle (SDLC)
as it describes the complete requirement of the system. It is meant for use by
the developers and will be the basic during testing phase. Any changes made
to the requirements in the future will have to go through formal change
approval process.

Developers Responsibilities Overview:

The developer is responsible for:
1)

Developing the system, which meets the SRS and solving all the
requirements of the system?

2)

Demonstrating the system and installing the system at client's

location after the acceptance testing is successful.

3)

Submitting the required user manual describing the system

interfaces to work on it and also the documents of the system.

4)

Conducting any user training that might be needed for using the
system.

5)

Maintaining the system for a period of one year after installation.

Functional Requirements is the specification of the function that the system

must support. Where as non-functional requirements are the constraint on
the operation of the system that is not related directly to function of system.
Functional Requirements:
Inputs: The major inputs for the Clinic Care System Interface are the user
name and passwords of the Admin, Doctor, etc...
Output: The outputs are the accessing the required data of the Doctors and
Patient.

Performance Requirements:
Performance is measured in terms of ease of use of user interface.

Required Hardware

Pentium IV Processor.
256 MB RAM.
40GB Hard Disk space.
Ethernet card with an Internet and Internet zone.

Required Software
Server Side:

Microsoft Windows 2000 Prof

Internet explorer 5.0 or above or Netscape navigator.
Asp. Net.
SQLSERVER2000.
IIS SERVER.
TCP/IP Protocol suite.

Client Side:
Any Web Browser on any Windows operating system.

Homepage for Admin