M A D H U B E N & B H A N U B H A I P A T E L I N S T I T U T E O F TE C H N O L O G Y

(A C O N S T I T U E N T C O L L E G E O F CVM U N I V E R S I T Y)
D E P A R T M E N T O F IN F O R M A T I O N TE C H N O L O G Y
102045602 – S OF TWA RE E N G I N E E RI N G

Practical – 1
Airport Management System

Definition:
An airport management system is a specialized digital platform that automates
and streamlines the main airport operations including passenger processing,
baggage tagging and handling, arrival/departure operations, departure control
systems, information distribution, and air traffic control (ATC).

Problem Statement:
The Airport Management System aims to achieve these objectives through the
development of a comprehensive software solution that integrates various
airport functions, automates processes, and provides real-time data analytics
to support decision-making. This system will ultimately contribute to the
efficient, safe, and passenger-friendly operation of the airport.

Problem Definition:
The problem that AMS systems are designed to solve is the complexity of
airport operations. Airports are complex systems with many different
stakeholders, including airlines, passengers, ground handlers, security
agencies, and government agencies. AMS systems help to coordinate the
activities of all of these stakeholders to ensure that flights operate on time and
that passengers have a safe and positive travel experience.

Features:
1. Passenger Management
2. Flight Management
3. Aircraft and Gate Management
4. Passenger Services
5. Security Management
6. Air traffic control
7. Baggage management

Features in Detail:

1. Passenger Management :
 Passenger check-in and boarding management.
 Ticket booking and reservation system.

1 Enrolment Number: 12102040701111

 M A D H U B E N & B H A N U B H A I P A T E L I N S T I T U T E O F TE C H N O L O G Y
(A C O N S T I T U E N T C O L L E G E O F CVM U N I V E R S I T Y)
D E P A R T M E N T O F IN F O R M A T I O N TE C H N O L O G Y
102045602 – S OF TWA RE E N G I N E E RI N G

 Passenger profiling and security screening.

 Baggage handling and tracking.

2. Flight Management:
 Flight scheduling and management.
 Real-time flight tracking and status updates.
 Automated gate allocation and assignment.
 Delay and cancellation management.

3. Aircraft and Gate Management:

 Gate and terminal management.
 Aircraft parking and allocation.
 Fuel and maintenance scheduling.
 Aircraft maintenance tracking.

4. Passenger Services:
 Flight information displays.
 Self-service and mobile check-in.
 Lounge and amenities management.
 Provide all lounges for comfortable journey.

5. Security Management:
 Security checkpoint management.
 Passenger and baggage screening.
 Access control and employee management.
 Baggage tagging and weighting for secure travel.

6. Air traffic control:

 Provide flight arrivals and departure data to passengers.
 Provide gate and terminal to aircraft.
 Provide other facility to management of airport.

7. Baggage management:
 Baggage Handling and tagging.
 Baggage weighting.

2 Enrolment Number: 12102040701111

 M A D H U B E N & B H A N U B H A I P A T E L I N S T I T U T E O F TE C H N O L O G Y
(A C O N S T I T U E N T C O L L E G E O F CVM U N I V E R S I T Y)
D E P A R T M E N T O F IN F O R M A T I O N TE C H N O L O G Y
102045602 – S OF TWA RE E N G I N E E RI N G

 Waterfall Model:

1. Requirements Phase:
 In this phase, gather detailed requirements for the Airport Management
System. This includes understanding the specific needs of the airport,
regulatory requirements, and user expectations.
 Identify stakeholders and conduct interviews and surveys to gather
requirements.
 Document the requirements in detail, including functional and non-
functional requirements..
2. Design Phase:
 Once the requirements are well-understood, proceed to design the
system. This includes defining the architecture, data models, and user
interfaces.
 Create detailed design documents specifying how different components
of the AMS will work together.
 Plan the database schema and data flows.
3. Implementation Phase:
 Once the requirements are well-understood, proceed to design the
system. This includes defining the architecture, data models, and user
interfaces.
 Create detailed design documents specifying how different components
of the AMS will work together.
 Plan the database schema and data flows.
4. Testing Phase:
 Perform comprehensive testing to ensure that the developed system
meets the specified requirements.
 Types of testing may include unit testing, integration testing, system
testing, and user acceptance testing (UAT).
 Identify and fix defects and issues that are discovered during testing.
5. Deployment Phase:
 Perform comprehensive testing to ensure that the developed system
meets the specified requirements.
 Types of testing may include unit testing, integration testing, system
testing, and user acceptance testing (UAT).
 Identify and fix defects and issues that are discovered during testing.
6. Maintenance Phase:
 Perform comprehensive testing to ensure that the developed system
meets the specified requirements and feedback through updates.

3 Enrolment Number: 12102040701111

 M A D H U B E N & B H A N U B H A I P A T E L I N S T I T U T E O F TE C H N O L O G Y
(A C O N S T I T U E N T C O L L E G E O F CVM U N I V E R S I T Y)
D E P A R T M E N T O F IN F O R M A T I O N TE C H N O L O G Y
102045602 – S OF TWA RE E N G I N E E RI N G

Practical – 2
Aim: Define requirement Gathering and technical requirement
specification for the selected project (Airport Management System).
 Requirement Gathering:
The requirements gathering process for an airport management system
(AMS) is important to ensure that the system meets the needs of the
airport and its stakeholders. The requirements gathering process should
involve a variety of people, including airport staff, passengers, airlines,
and other stakeholders.
For a Airport Management System, the requirement gathering process
would involve:
1. Stakeholder Identification: The first step is to identify all of the
stakeholders who will be affected by the AMS. This may include
airport staff, passengers, ATC, ground baggage handlers, security
agencies, and government agencies.
2. Interviews and Surveys: Schedule interviews with key stakeholders
to understand their specific requirements and pain points. Ask open-
ended questions to gather valuable insights into their needs and
expectations. Take note of any regulatory requirements and industry
standards that must be adhered to.
3. Review Existing Documentation: Examine any existing
documentation, such as legacy systems, standard operating
procedures, and regulatory documents. This can help uncover
valuable information about current processes and requirements.
4. Functional Requirements: Document functional requirements,
specifying what the AMS should do. Include details about features
such as flight scheduling, passenger check-in, baggage handling,
security screening, and reporting.
5. Non-functional Requirements: Capture non-functional
requirements, which address qualities like performance, security,

4 Enrolment Number: 12102040701111

 M A D H U B E N & B H A N U B H A I P A T E L I N S T I T U T E O F TE C H N O L O G Y
(A C O N S T I T U E N T C O L L E G E O F CVM U N I V E R S I T Y)
D E P A R T M E N T O F IN F O R M A T I O N TE C H N O L O G Y
102045602 – S OF TWA RE E N G I N E E RI N G

scalability, and usability. Specify response times, data security

measures, and compliance with industry regulations.
6. Data Requirements: Define the data that the system will need to
store, manage, and retrieve. Describe data sources, data flows, and
data retention policies. Consider data privacy and compliance with
data protection laws.
7. Risk Assessment: Identify potential risks and challenges associated
with the development and deployment of the AMS. Develop risk
mitigation strategies to address these challenges.
8. Prototyping: Create prototypes or mockups of the user interface to
visualize and validate design concepts with stakeholders. Use
prototyping to gather feedback on the system's look and feel.
9. Prioritization: Prioritize requirements based on their importance,
urgency, and feasibility. Create a roadmap for development that
reflects these priorities.
10. Documentation: Document all gathered requirements in a clear,
organized manner. Ensure that the documentation is accessible to all
team members and stakeholders.
Create a roadmap for development that reflects these priorities.
Technical Requirement Specification:
A Technical Requirement Specification (TRS) is a document that
outlines the technical details and specifications of a system. It serves as
a blueprint for the development team and ensures that everyone
involved in the project understands how the system will be designed
and built.
For a Airport Management System, the TRS might include:
1. System Architecture: Describe the high-level architecture of the
system, including components, modules, and their interactions.
Specify whether the system will be web-based, desktop-based, or
mobile-based.
2. Database Design: Detail the database structure, including tables,
relationships, and data storage mechanisms. Specify how baggages,
passengers, ATC, and other relevant information will be stored.

5 Enrolment Number: 12102040701111

 M A D H U B E N & B H A N U B H A I P A T E L I N S T I T U T E O F TE C H N O L O G Y
(A C O N S T I T U E N T C O L L E G E O F CVM U N I V E R S I T Y)
D E P A R T M E N T O F IN F O R M A T I O N TE C H N O L O G Y
102045602 – S OF TWA RE E N G I N E E RI N G

3. User Roles and Permissions: Define different user roles (airport

authority, passenger, baggage handling ,ATC, Security, etc. ) and
their respective permissions within the system.
4. Functional Requirements: Provide a detailed breakdown of each
functional requirement gathered during the requirement gathering
phase. Specify how each requirement will be implemented and its
expected behavior.
5. Data Flow Diagrams: Use diagrams to illustrate how data will flow
within the system, from the point of entry to its final use.
6. Interfaces: Describe the user interfaces, including screens, forms,
and reports. Include details about the user experience, such as
navigation, input validation, and error handling.
7. Performance Requirements: Specify performance metrics such as
response times, concurrent user support, and data processing speed.
8. Security and Privacy: Define security measures to protect sensitive
data, including authentication, authorization, encryption, and data
access controls.
9. Integration Requirements: Detail any integration with external
systems (e.g., Air traffic control system) and APIs that need to be
developed or utilized.
10. Testing and Validation: Describe the testing procedures and criteria
that will be used to ensure the system meets the specified
requirements.
11. Deployment and Maintenance: Outline the deployment strategy,
including hardware and software requirements, installation process,
and plans for ongoing maintenance and updates.

6 Enrolment Number: 12102040701111