0% found this document useful (0 votes)
475 views9 pages

Case Study: Departure Control System: CH Narasimhan

The document describes a departure control system (DCS) case study. The DCS is intended to help airlines manage flight departures efficiently. It allows for self check-in, check-in at counters, and web check-in. The system needs to integrate with reservation, airport, and payment systems. It must also be scalable, secure, and support multiple payment options. The DCS architecture includes modules for check-in, boarding, loyalty programs, and notifications. Key requirements are usability, interoperability, performance, and security.

Uploaded by

sailaja scube
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
475 views9 pages

Case Study: Departure Control System: CH Narasimhan

The document describes a departure control system (DCS) case study. The DCS is intended to help airlines manage flight departures efficiently. It allows for self check-in, check-in at counters, and web check-in. The system needs to integrate with reservation, airport, and payment systems. It must also be scalable, secure, and support multiple payment options. The DCS architecture includes modules for check-in, boarding, loyalty programs, and notifications. Key requirements are usability, interoperability, performance, and security.

Uploaded by

sailaja scube
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 9

CASE STUDY: DEPARTURE

CONTROL SYSTEM
CH NARASIMHAN
BUSINESS GOAL
• To build a scalable system which would help the airlines to manage the flight departures in an
efficient manner.
USERS OF THE DCS

• Self-check-in passengers
• Check-in staff
• Boarding-gate staff
• Ground operations Officer
ARCHITECTURALLY SIGNIFICANT REQUIREMENTS

• System should enable the users to do a self check-in, web check-in apart from the counter check-in
: Usability
• System should be able to get data from other systems such as the Reservation System :
Interoperability
• DCS should be able to export data to systems such as Airport System, and Reservation System :
Interoperability
• Should be able to support multiple modes of payments : Usability
• Should be scalable, and must cater to large volume of passengers : Performance
• System should be secured and ensure that the No – fly list is not tampered in the transit : Security
UTILITY TREE
S.No Architecturally Significant Quality Attribute Business Impact on Tactic
Requirement Value Architecture
1 Capability to do self-check in, Usability High High Expose APIs for the DCS to
counter based, and web check-in accept checkins.
2 Multiple modes of payment Interoperability High Medium Payment gateway
integrations
3 Get data from other systems Interoperability High High Design an API first
approach when sending
and receiving data
4 Cater the large volume of Performance High High Use a high reliability
passengers system such as Salesforce
CRM
5 Ensure that all the communications Security High Medium Ensure that all the
are secure communication is done via
HTTPS, and encrypt data if
needed.
MODULE VIEW
User Interface
Module

Loyalty
module

Payment
Reservation Check-in Boarding module
System Module Module

Ground
Travel Security Admin Module User
Operations
Admin Notifications
module
COMPONENT AND CONNECTOR VIEW

Airport
Kiosk Web App
Counter
REST REST SOAP
API layer

REST API via Payment Gateways


Reservation HTTPS
System Check in
Get passenger list
module
Apex methods calls SMS Gateways, Ex:
Get Fly, No - Fly list
TSA Twilio API
REST API via Boarding module
HTTPS

Salesforce
CLOSE FLIGHT BOOKING COMPONENTS
1. Initiate Close Booking via API

Reservation System
Admin Module
2. Close Booking Success

3. Sends message to other modules


such as Boarding

Boarding Module
DATA EXPORT UPON FLIGHT TAKE OFF
3. Send
passenger list 4* Reservation
1. Send Flight take
Ground off message
– ( JSON )
System
Operations Admin Module
Module
API
2. Method call
Layer
to get
passenger list 4*
Airport System

Boarding Module

4  REST call to send data

You might also like