SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

SWE2003 - REQUIREMENTS ENGINEERING & MANAGEMENT

Digital Assignment - II
Slot: D1
P.LOKESH KUMAR
18MIS0194

SOFTWARE REQUIREMENTS SPECIFICATION [SRS]

FOR AUTOMATED AIR TRAFFIC CONTROL

TABLE OF CONTENTS

1: INTRODUCTION 2

 PURPOSE 3
 PRODUCT SCOPE 3
 DEFINITIONS,ACRONYMS AND ABBREVIATIONS 3
 REFERENCES 3
 OVERVIEW 3

2: OVERALL DESCRIPTION 4

 PRODUCT PERSPECTIVE 4
 PRODUCT FUNCTIONALITIES 4
 PREDICT CONFLICT 4
 RESOLVE CONFLICT 5
 UPDATE WEATHER 5
 RESOLVE BAD WEATHER CONFLICT 5
 LANDING AIRCRAFT 5
 AIRCRAFT TAKE-OFF 5
 MAINTAIN SAFE AMPLITUDE 6
 PROVIDE RUNWAY ASSIGNMENT 6
 DOCKING THE AIRCRAFT 6
 ADD NEW FLIGHT 6
 DELETE FLIGHT 6
 UPDATE FLIGHT 6
 CALCULATE TOTT 6
 EDIT DEPARTURE LOG 7
 EDIT ARRIVAL LOG 7
 USER CHARACTERISTICS 7
 DESIGN AND IMPLEMENTATION CONSTRAINTS 7
 ASSUMPTIONS AND DEPENDENCIES 8
 OPERATING ENVIRONMENT 8

Page 1 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

3: SPECIFIC REQUIREMENTS 8

 EXTERNAL INTERFACE REQUIREMENTS 8

 FUNCTIONAL REQUIREMENTS 9
 LOGICAL DATABASE REQUIREMENTS 10
 FLIGHT SCHEDULE 10
 PARKING 10
 COMMUNICATIONS 10
 RUNWAY RECORD 10
 GENERATING REPORTS 10
 MANAGING MESSAGES 10
 HANDLING WEATHER CHANGES 10
 ADMINISTRATIVE SOFTWARE REQUIREMENTS. 10
 LOGIN 10
 ACCESS CONTROL 11
 USER FRIENDLY 11
 REAL TIME/SYNCHRONIZED 11
 COMPATIBILITY ISSUE 11
 EDIT TASKS 11
 TASK LIST 11
 NON-FUNCTIONAL REQUIREMENTS 12
 PERFORMANCE REQUIREMENTS 12
 SAFETY AND SECURITY REQUIREMENTS 12
 SOFTWARE QUALITY ATTRIBUTES 12
o RELIABILITY 12
o SECURITY 12
o MAINTAINABILITY 12
o PORTABILITY 13
o SUPPORTABILITY 13

1. INTRODUCTION

 PURPOSE :

This document is intended to represent the software requirements

specification of the Automated Air Traffic Control System. The scope of
the document is to identify the requirements of the Automated Air Traffic
Control System. This document is the first version and additions are
expected in further versions.

Page 2 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

 PRODUCT SCOPE:

Automated Air Traffic Control System is aimed to provide software based

automation to the operations of the Air Traffic Controller (ATC) for
efficient and reliable services regarding the flow and control of the air
traffic in the vicinity of the airports. The goal is to minimize the human
participation in the operations of ATC so that the loss caused by human
negligence can be eliminated.

 DEFINITIONS, ACRONYMS AND ABBREVIATIONS :

1. Air Traffic Controller (ATC)

2. Arrival Departure manager (ADM)
3. System Coordination (SYSCO)
4. Minimum Safe Altitude Warning (MSAW):
5. Short Term Conflict Alert (STCA)
6. Area Penetration Warning (APW)
7. Controller Pilot Data Link Communications (CPDLC)
Controller Pilot Data Link Communications (CPDLC), also referred to as
Controller Pilot Data Link (CPDL), is a method by which air traffic
controllers can communicate with pilots over a data link system..
8. User Request Evaluation Tool (URET)
User Request Evaluation Tool or URET is a tool to help air traffic
controllers to detect and resolve potential conflicts between aircraft
and between aircraft and airspace. The goal of URET is to help air
traffic controllers to support a greater number of user-preferred flight
profiles, increase user flexibility, and increase system capacity

 REFERENCES

IEEE Recommended Practice for Software Requirements Specifications.

www.jsu.edu
www.slideshare.net
www.wikipedia.org

 OVERVIEW

This Document is intended for all those people who are involved with the
air traffic control.The stakeholders of this Software include the following: -

 Air Traffic controller (ATC)

 Pilot Arrival and Departure Manager
 System Administrator
 Software developers
 Project managers
 Software tester

Page 3 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

2. OVERALL DESCRIPTION

 PRODUCT PERSPECTIVE

The main goal of this software development project is to develop a user-

friendly mechanism that manages the air traffic flow around the airports
to enhance safety and efficiency of the air traffic. The need for automation
of the air traffic controller was sensed due to various catastrophes faced
due to human negligence. The system should be stable so as to ensure
smooth communication between the pilot and the control room operator.
In case of emergencies there must be some emergency protocol in the
system that would retain the communication between the pilot and the
control room operator. A backup system should be present for this
purpose. Cross communication between the crisis management team and
the other departments is highly critical to facilitate quicker response and
information exchange, minimizing property damage and loss of life. This is
a new self-contained product which is to be developed for the Pakistani
Civil Aviation in order to provide some level of automation to the Air
Traffic Control.

 PRODUCT FUNCTIONALITY

For our Automated Air Traffic Control system software we need to

validate the user before any interaction with the software takes place. The
users we are considering here include the air traffic controller,
Arrival/Departure Admin. The log in process may be done whenever the
related user tries to access the software. User needs to provide the log-in
ID and a password for this process. The system should provide the ATC
with necessary functions associated to his/her day to day operations. This
includes separating aircrafts to prevent collisions, to organize and
expedite the flow of traffic, and to provide information and other support
for pilots when able.

 PREDICT CONFLICT

The control room operator may check the URET system for potential
conflicts. For this ATC may first select the check conflict->predict
conflict. Then he/she is prompted for ID’s of the concerned aircrafts.
The ATC may select from the list of ID’s in the database. The system
computes the distance between the two aircrafts and issues an
alarm signal on unsafe configuration of the airspace.

Page 4 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

 RESOLVE CONFLICT

URET issues an alarm signal to the ATC for potential conflict. The
system would give several options to the ATC for the resolution of
the conflict from which some are listed here: -
 altitude amendments
 horizontal route amendment
 speed changes

 UPDATE WEATHER

The ATC in the control tower would send a query to the Met.
Department to give an update of present weather conditions and
the next 48 hour forecast of weather at the airport and local area.

 RESOLVE BAD WEATHER CONFLICT

If the ATC detects bad weather conditions in the airspace, he must

inform the incoming air traffic about the weather condition to avoid
any undesirable mishap. For this our software would have a feature
that would help us to give a bad weather warning to all the
approaching aircrafts to wait before the weather clears out. Based
on the current position of the aircrafts and the radius of the bad
weather airspace we would inform the aircraft to execute one of the
following:

 Maneuver in the airspace having clear weather conditions until

weather at destination airport is clear.

 Make a landing to a nearby airport where weather conditions

are good enough.

 LANDING AIRCRAFT

When an airplane is about to approach the airport, the pilot send a

clear-to land query to the ATC. The ATC check whether some other
airplane is landing on the same time. If yes the ATC send a ‘NO’
message to the pilot. The airplane would then maneuver for about
the 30mins until the runway is clear. If the ATC send a ‘YES’
message, the airplane is allowed to land on the runway

 AIRCRAFT TAKE-OFF

When an airplane is about to take-off from the airport, the pilot

send a clear-to takeoff query to the ATC. The ATC check whether
some other airplane is taking off on the same time. If yes the ATC
send a ‘NO’ message to the pilot. The airplane would then wait until

Page 5 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

the runway is clear. If the ATC send a ‘YES’ message, the airplane is
allowed to takeoff from the runway.

 MAINTAIN SAFE AMPLITUDE

The Pilot would be provided with an interface in his cockpit that

would show the minimum safe amplitude from ground. The cockpit
would be equipped with a GPS database of the terrain to provide
terrain warnings. If the height goes below the safe level the ATC
would inform the pilot to set its height to a safe level.

 PROVIDE RUNWAY ASSIGNMENT

The ATC would assign a sequence no. to an aircraft which is ready

for departure with the help of the AATC software. The ATC would
open the Departure interface of the software system. He would
select assign runway option. The software would then prompt for
necessary details related to the aircraft and automatically generate
a sequence number. This sequence number would then be assigned
to the concerned aircraft.

 DOCKING THE AIRCRAFT

Our software has provided us with and interface that shows

reserved and free parking slots at the Docking terminal. Whenever
the aircraft is landed on an airport, the next task the ATC should
perform is to assign the Docking slot to the aircraft depending on
the size of the aircraft.

 ADD NEW FLIGHT

In order to add a new flight in the flight database the AATC must
provide a functionality to take necessary information related to the
aircraft. And make a new object in the database.

 DELETE FLIGHT

In order to delete a flight in the flight database the user must search
a flight with its flight number. On successful hit, the user can
choose between update/delete. On choosing delete option the
AATC system would delete the concerned flight from the database.

 UPDATE FLIGHT

In order to update a flight in the flight database the user must

search a flight with its flight number. On successful hit, the user can

Page 6 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

choose between update/delete. On choosing update option the

AATC system would update the concerned flight from the database.

 EDIT DEPARTURE LOG

The ADM can add a new entry in the departure log, update it if
there is any change in plans of the flight and delete it. The
Departure manager has the authority to make changes in the
departure log. Others can only view it.

 EDIT ARRIVAL LOG

The ADM can add a new entry in the arrival log, update it if there is
any change in plans of the flight and delete it. The ADM has the
authority to make changes in the Arrival log.

 USER CHARACTERISTICS

We have identified most of the users of this system in the introduction of

this document. The users that would use the system most frequently are: -
1. The Air Traffic Controller – The ATC is the most frequent user of this
system.

2. The Arrival and departure manager – Less frequent than the ATC. His
output would be the input required by the ATC.
Other users may include the flight administrator, the system
administrator, system analyst, software tester etc.

 DESIGN AND IMPLEMENTATION CONSTRAINTS

Design requirements and constraints respectively stand for non-

functional requirements the final product should meet and restrictions the
designer is faced with. The design requirements and constraints result
from confronting and balancing the needs and vision of all stakeholders –
users, marketing department, product and project managers, developers.
They are summarized in the design brief, which forms the input for the
design phase and the basis for subsequent test or evaluation phases.
While the sources are varied, design constraints typically originate from
one of three sources:
 Restriction of design options
 Conditions imposed on the development process
 Regulations and imposed standards

Page 7 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

 ASSUMPTIONS AND DEPENDENCIES

 The software will run on computer machines. It is assumed that all the
users have basic knowledge of computer. This will help them to easily
understand the hierarchy of software.  It is assumed that all the users
have well knowledge of ATC field. They need to understand the different
reading received from different of the whole ATC system.
 It is assumed that the different sensors which are installed at different
places are working well and give accurate reading enough, which is
necessary in ATC.
 It is assumed that the software is running on hardware of minimum
specifications Pentium IV technology.
 Software is made automated. So, it is assumed that if there any
emergency then the controller is able to operate it manually.

 OPERATING ENVIRONMENT

The software would function in the air traffic control department and the
functional wing of the PCAA where arrival and departure of the flights are
managed. The hardware required for this software would be a number of
servers which would manage the databases and the load of the users that
are logged in at that time and the terminals associated to each air traffic
controller. The server would have a UNIX-based operating system and the
terminals would run on Linux 11.12. As our software is component based
software several other programs are also required to run on the machine.
The major sub-systems of the software include: -
1. Air traffic control
2. Arrival Departure
3. Flight

3. SPECIFIC REQUIREMENTS

 EXTERNAL INTERFACE REQUIREMENTS

o USER INTERFACES:
Instant messages being shared between the ATC and pilot.
o HARDWARE INTERFACES:
There are no special hardware interface requirements.
o SOFTWARE INTERFACES:

Web Server : WASCE, Windows series

Data Base Server : DB2,Windows series

Development End : J2EE, Java, Oracle, XML, DB2, OS

(WINDOWS XP), Web Server.

Page 8 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

o COMMUNICATION INTERFACE:
Firewall security is required for securing the server.

 FUNCTIONAL REQUIREMENTS

The following represents a detailed list of functional requirements for the

Automated Air Traffic Control System:
 All flights are in contact with our system.
 The System must follow the requirements set by CAA.
 The system gets regular updates from the Metrological
department.
 The system locates the current position of the aircraft. A GUI is
provided which gives the user a pictorial view of the aircraft’s
current position.
 A flight is only allowed to take off if the weather conditions are
suitable.
 A flight is only allowed to land if the weather conditions are
suitable.
 An emergency protocol should be executed in case of problem.
 Calculates a planned departure flow with the goal to maintain an
optimal throughput at the runway, reduce queuing at holding
point and distribute the information to various stakeholders at the
airport
 Calculates a planned Arrival flow with the goal to maintain an
optimal throughput at the runway, reduce arrival queuing and
distribute the information to various stakeholders.
 Provides runway assignment and sequence number advisories to
terminal controllers to improve the arrival rate at congested
airports.
 System Coordination (SYSCO) to enable controller to negotiate
the release of flights from one sector to another.
 Minimum Safe Altitude Warning (MSAW): a tool that alerts the
controller if an aircraft appears to be flying too low to the ground
or will impact terrain based on its current altitude and heading.
 Providing conflict advisories up to 30 minutes in advance and have
a suite of assistance tools that assist in evaluating resolution
options and pilot requests.
 Allows digital messages to be sent between controllers and pilots,
avoiding the need to use radiotelephony. (CPDLC)
 Area Penetration Warning (APW) to inform a controller that a
flight will penetrate a restricted area.

Page 9 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

 LOGICAL DATABASE REQUIREMENTS

All the communications between aircraft and tower must be recorded and
standardized and for this reason we need a database for our system. Here
two databases will be used and will be maintained separately. They may
interact with one another, but their usage and effect will be separate.
 FLIGHT SCHEDULE:
Maintain flight schedule using the database. Must also manage list
of all aircrafts that are expected to land and take of in near future
separately.

 PARKING:
Managing parking at airport using this system.

 COMMUNICATIONS:
Keeping record of all the communication done by the ground and
also specify time and aircraft at and with which communication
was performed.

 RUNWAY RECORD:
Keep record of runway history that is it was provided to which
plane at a certain time, it will also keep record of officers on duty for
security purpose that will enable it to interact with officer whose
duty is at specific time and thus ensuring security.

 GENERATING REPORTS :
It will also enable privileged stake holders such as chief manager
and director to print a report of performed and queued operations
on ground, category wise.

 MANAGING MESSAGES:
It will also be generating messages using different systems to
airports for which a flight is departed upon departure of a flight.

 HANDLING WEATHER CHANGES :

If a certain and unexpected change occurs in climate then it will be
performing all operations then it must send an alarm or special
message signal to all related planes that will be in system for that
time .
 ADMINISTRATIVE SOFTWARE REQUIREMENTS:

 LOGIN :
Anyone to work on the system or interact with the system must
login first with a username and password and also a thumb
impression for complete security in a very delicate environment. All
the activities he or she performs during the login period must be
recorded in data base for future record.

Page 10 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

 ACCESS CONTROL:

Access controls to data base must be defined that is everyone must

not be allowed to access every part of the system and if anyone tries
to access restricted section a signal or alarm must be generated to
higher authorities.

 USER FRIENDLY:

It must be user friendly interfaces for the people to be using this

system might lack software related skills for example database
handling etc. so the software must be of such level that anyone
after 1 or 2 hours of training must be able to use it within restricted
access.

 REAL TIME/SYNCHRONIZED:

The software must be real time and synchronized for a station that
is anyone must not be able to turn it off and all stakeholders
accessing it at a certain time on one station must see same
information and if any command or change is ordered to system,
this change must be notified to all users online at that time without
any delay. So that contradictory orders are not given to the system
or same order is not repeated.

 COMPATIBILITY ISSUE:

The software must be developed or coded in language that is

compatible with the instruments and computers in the Air Traffic
Control Tower. It doesn’t matter that it is compatible with all
platforms or not, it must be compatible with desired machines for
which it is being developed.

 EDIT TASKS :

It should give an option of editing and rescheduling shifts head and

appointing new people for special shifts and creating special tasks
assignments for different employees.

 TASK LIST:

Software must contain a Tab of task list which contain number of

tasks that are pending for a user and must give a notification to the
user showing his number of pending tasks every time he login. Also,
when a user log off at end of duty system must prompt if any of his

Page 11 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

tasks were incomplete and show a success percentage giving how

many of his tasks are successfully completed during current session.

 NON-FUNCTIONAL REQUIREMENTS

 PERFORMANCE REQUIREMENTS:

The software should have good performance. In order to ensure

good performance of the AATC software the hardware must be
compatible with all the sub systems of the software. The system
should be designed and implemented as such that it could handle
errors and exceptions efficiently. In case of system failure, there
must be a backup system to resume the operations without much
time overhead as for the AATC system time is a major constraint.

 SAFETY AND SECURITY REQUIREMENTS

The software should be secure. It should only be used by the

authorized user. It should also be security attack proof. Any third
party application or something like virus should not affect the
software performance. There should be login for different
employees. The software should keep track of the user login time,
activities on software and logout time. Nobody can access the
software without authentication.

 SOFTWARE QUALITY ATTRIBUTES:

1) RELIABILITY: The software should be reliable. It should be

accurate enough to ensure that all the reading are precise.

2) SECURITY: The software should be secure. It should only be used

by the authorized user. It should also be security attack proof.
Any third party application or something like virus should not
affect the software performance. There should be login for
different employees. The software should keep track of the user
login time, activities on software and logout time. Nobody can
access the software without authentication.

3) MAINTAINABILITY: Unless the product customized or source

code is changed, any maintenance support shall be provided by
parent organization. Backing up of the database is not required.

Page 12 of 13
SRS FOR AUTOMATED AIR TRAFFIC CONTROL SYSTEM

4) PORTABILITY: The software should be portable from hardware

to hardware, so that if there is a hardware upgrade so we won’t
need to start the whole software from scratch.

5) SUPPORTABILITY: The system should be supportive. It should be

supported to maximum number of operating systems like and
different distributions of the operating systems. As we know,
this is very important that the software should be supportive to
operating system, there is also important that it should also
support the hardware, so that it may able to give the
performance.

Page 13 of 13