Final Report Airline Management System
Final Report Airline Management System
CHAPTER 1
INTRODUCTION
1.1.Objective
The main objective of this system is to keep records of the complete sales of
product.It supports sales management that helps to record and track materials
on the basis of both quantity and value.It improves cash flow,visibility,and
decision making.
1.2. Scope
Sales strategy is the key to drive the salesforce. It identifies the best
prospects, details the basic value proposition and defines the selling
process. The salesforce’s task is to transform the strategy into a workable
reality. Proper implementation of the sales strategy allows the company
to achieve the sales volume and customer satisfaction.
The report report reprensts different aspects about analysis of machine learning
approaches for text classification into context-based class labels called domains.
CHAPTER 1: INTRODUCTIONPage 1
Sales and Product Management System 2022
CHAPTER 1: INTRODUCTIONPage 2
Airline Reservation Management System 2021
CHAPTER 2
6 IDE/Workbench NetBeans
7 Database MySQL
The Existing system includes problems like lack of time consuming, accuracy,
high cost, security problems, etc. There are many problems in existing systems
like:
Accuracy,Storing
The Proposed system ensures the complete freedom for users, where user at
his own system can logon to this website and can book his ticket. Our
proposed system allows only registered users to book the tickets, view timings
and cancel their tickets. In this Proposal the entire work is done on online and
The machine will perform all calculations. Hence chances of error are nearer to
nil.
The passenger, reservation, cancellation list can be easily retrieved and any
required addition,
The machine will perform all calculations. Hence chances of error are nearer to
nil.
The passenger, reservation, cancellation list can be easily retrieved and any
required addition,
This project represents the initial version of the Airline Booking system. All
requirements listed herein describe a self-contained system. At a high level, this
project will allow a user to book flights, check flights, do account maintenance,
and query flight information. The goal is to allow customers greater and easier
access to the airline’s booking system, twenty-four hours a day.
2.2.1 Login
2.2.2 Enrollment
Description: The user can use the Book Flights function to purchase
seats for an airplane flight. The system shall present the user with
information on all current flights. The user may then select a pair
(departure and return) of flights on which to purchase seats. The user can
indicate the number of seats and placement of such. Finally, the system
shall guide the user completely through the checkout process.
Rationale: The heart of the business is selling seats on flights. This
section
provides the primary source of system transactions.
Description: The user can use the Reserve Seat function to reserve seats
for an airplane flight. The seats to be reserved are initially found through
the user’s previous bookings. These bookings were previously completed
through the Book Flight function (SEE 2.2.3). The system shall display
available seats for the departing and returning flights booked by the user.
The user selects seats from each flight, where the number of selected
seats from each flight is the number that the user booked on that
particular flight. Once the flight seats are selected, the user confirms the
seat selection.
Rationale: Customers prefer to know where their seats are located.
Further, they prefer to pick out particular seats – closer to the front,
window seat, aisle seat, etc. From that point, the seats are removed from
available/unreserved seats and the user’s booking is linked to those
particular seats. If the user fails to reserve a seat prior to flight takeoff,
the user is randomly assigned a seat from available seats 30 minutes prior
to initial takeoff time. This function is offered immediately after booking
the user can wait and use the function to book seats any time after up
until 30 minutes prior their flight.
Description: This section shall allow the user – whether enrolled or not –
to view flight information that matches input criteria. The user will
provide:
1. A flight number and Date
OR
2. Departing/Arriving Cities and Date.
The system will display matching flight information including the
Description: This section of the system shall allow a user to query flight
schedules
based upon simple input criteria. The user will provide departure and
arrival cities, and a departure/return date. If any flights match the
criteria, the system will display the following information:
● Flight Number
● Departing City & Date/Time
● Arriving City & Date/Time
● Number of Available Seats
The system shall define a “matching” flight as one that uses the
departure/arrival cities at a flight time greater or equal to the time
provided by the user. Otherwise, the system shall alert the user that no
matching flights can be found.
2.2.7 My Account
Description: This section gives the user the power to view, save, edit or
delete the information stored in his/her account. The user can check
his/her accumulated points, look at the status of a flight that was booked,
cancel a flight that was already booked (optional) and change his/her
address, phone number, email or password. This feature is not available
for non-registered user.
Rationale: A customer’s information changes from time to time. Giving
the users a way to modify their account information allows the business
to have current & updated information.
2.2.8 Logout
Description: The Logout section provides a way for the user to securely
log out of the system. This process will save all user operations when
he/she
exits the system. If a user wishes to continue accessing the website,
he/she must log-in again to access user features.
Rationale: Customers often use shared computers. Providing a way to
clear state and log-out gives our customers confidence that nobody else
will use
their flight-booking session.
The main actors in the system are (1) the user, (2) a flight and (3) a Flight Seat.
The user will select a flight and book seats on the flight. They will then reserve
specific seats on that flight. Brief descriptions of these classes follow:
● User
o Has properties like Name, Address, Age
o Associated with Flight Miles accumulated and Credit Card
information.
● Flight
o Has properties like Departing/Arriving City, Departure/Arrival
dates and times, Miles, and an identifying Flight Number.
● Flight Seat
o Has properties of identifying seat number, reserved and flight
number
o Associated to Flight-by-flight number
Our user may be associated with multiple flights, and many users may be
associated with any particular flight. Thus, a many-to-many relationship exists
through the act of booking flights.
Flights are associated to many Flight Seats. Each Flight Seat is only attached to
one Flight. So, this is a one-to-many relationship
3.System Features
Software Requirements:
IDE/Workbench : NetBeans.
Database : MySQL.
Hardware Requirements:
RAM : 1 GB or above.
3.1.1 Login
In most case, the frequent flight number is convenient for both the user
and system performance. The user easily memorizes his or her flight
numbers but not a dull string. For the system, when provided the flight
number, flight information will be delivered at the same time. Therefore,
such operation reduces the second query chance.
Theoretically, more than one record can retrieve by user’s frequent flight
number and password. Two or more users may have chosen the same
password and same flight number. The way to break a tie is that system
will go further to ask user’s
email confirmation to identify.
Use Case:
CHAPTER3: REQUIREMENT ANALYSIS AND SPECIFICATIONPAGE 13
Airline Reservation Management System 2021
3.1.2 Enrollment
The system checks if all required data are provided and then will prompt
the user to enter additional information, if required. After all required
information is provided, the system auto-generates a unique frequent
Inputs: Required: First name, last name, email address and frequent
flyer number
Optional: phone number, credit card information and mailing
address.
Source: All data except the frequent flyer number are inputs from the
user. The frequent flyer number is from the system store.
Outputs: Frequent Flyer Number
Destination: The changes are committed on the completion of the
“enrollment” function to account information. All information
also displays to the user via the screen.
Pre-Conditions: The user must not have an existing account with the website.
Post-Conditions: A user account is created and the user is able to access all
functionalities provided by the function “My Account” (refer
to 3.1.7)
Side-Effects: None
Stimulus-Response:
account.
Description and Priority: The user can use the Book Flights function to
purchase seats for an airplane flight. The system shall present the user
with information on all current flights. The user may then select a pair
(departure and return) of flights on which to purchase seats. The user can
indicate the number of seats and placement of such. Finally, the system
shall guide the user completely through the checkout process.
Stimulus/Response:
4. The user confirms the seat 5. Once confirmed, the seats are
selections on the screen. removed from available seats
and are applied to the user
account. The user is shown a
final confirmation screen which
displays selected seats and
account information.
Activity Diagram:
Description and Priority: The user can use the Reserve Seat function to
reserve seats for an airplane flight. The seats to be reserved are initially
found through the user’s previous bookings. These bookings were
previously completed through the Book Flight function (SEE 2.2.3).
The system shall display available seats for the departing and returning
flights booked by the user. The user selects seats from each flight, where
the number of selected seats from each flight is the number that the user
booked on that particular flight. Once the flight seats are selected, the
user confirms the seat selection.
Stimulus/Response:
Description & Priority: This section shall allow the user – whether
enrolled or not – to view flight information that matches input criteria.
The user will provide:
1. A flight number and Date
Description & Priority: This section of the system shall allow a user to
query flight schedules based upon simple input criteria. The user will
provide departure and arrival cities, and a departure/return date. If any
flights match the criteria, the system will display the following
information:
Activity Diagram:
3.1.7 My Account
Description & Priority: This section gives the user the power to view,
save, edit or delete the information stored in his/her account. The user
can check his/her accumulated points, look at the status of a flight that
was booked, cancel a flight that was already booked (optional) and
change his/her address, phone number, email or password. This feature is
not available for non-registered user.
Inputs: Account changes, if any, made by the user. Account changes include
updates on first name, last name, email address, mailing address, password or
phone numbers.
Source: All data are inputs from user.
Output: None.
CHAPTER3: REQUIREMENT ANALYSIS AND SPECIFICATIONPAGE 24
Airline Reservation Management System 2021
Destination: The changes are committed on completion of the My Account
function to account information.
Pre-Conditions: The user must have an account with the website and must be
logged in prior to access his/her account.
Post-Conditions: All changes submitted by the user are applied to the user
account on completion of the function.
Description & Priority: The Logout section provides a way for the user
to securely log out of the system. This process will save all user
operations when he/she exits the system. If a user wishes to continue
accessing the website, he/she must log-in again to access user features.
Inputs: None.
Source: N/A
Outputs: Notification that the user is logged out.
Destination: User is notified by display to screen.
Pre-Conditions: User is logged in to the system.
Post-Conditions: User is logged out of the system.
Side-Effects: The system clears the session state for the user once logout is
complete.
The airline website design shall allow deployment on both Windows and UNIX
(Linux) servers. The design should support Windows Server 2003, Linux 2.6.x,
V10 UNIX and later.
5.3.2 Robustness:
The system design shall include recovery scenarios allowing the ability to
restore a state no older than one business day old.
SOFTWARE DESIGN
Spiral Model:-
The spiral model is similar to the incremental model, with more emphasis
placed on risk analysis. The spiral model has four phases: Planning, Risk
Analysis, Engineering and Evaluation. A software project repeatedly passes
through these phases in iterations (called Spirals in this model). The baseline
spiral, starting in the planning phase, requirements is gathered and risk is
assessed. Each subsequent spiral builds on the baseline spiral. Requirements
are gathered during the planning phase. In the risk analysis phase, a process is
undertaken to identify risk and alternate solutions. A prototype is produced at
the end of the risk analysis phase. Software is produced in the engineering
phase, along with testing at the end of the phase. The evaluation phase allows
the customer to evaluate the output of the project to date before the project
continues to the next spiral.
ADMIN:
BACKEND DESIGN
5.1
CODE SAMPLE
6.1 Log In
package airline.management.system;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import java.sql.*;
TextField t1,t2;
Label l1,l2;
Button b2,b3,b4;
GridBagLayout gbl;
GridBagConstraints gbc;
Font f1,f2;
public Login(){
super("Login");
setBackground(Color.WHITE);
f1 = new Font("TimesRoman",Font.BOLD,20);
f2 = new Font("TimesRoman",Font.BOLD,15);
gbc=new GridBagConstraints();
setLayout(gbl);
l1 = new Label("Username");
l1.setFont(f1);
l2 = new Label("Password");
l2.setFont(f1);
t1 = new TextField(15);
t2 = new TextField(15);
t2.setEchoChar('*');
b2 = new Button("Reset");
b2.setFont(f2);
b3 = new Button("Submit");
b3.setFont(f2);
b4 = new Button("Close");
b4.setFont(f2);
gbc.gridx=0;
gbc.gridy=0;
add(l1);
gbc.gridx=2;
gbc.gridy=0;
gbl.setConstraints(t1,gbc);
add(t1);
gbc.gridx=0;
gbc.gridy=2;
gbl.setConstraints(l2,gbc);
add(l2);
gbc.gridx=2;
gbc.gridy=2;
gbl.setConstraints(t2,gbc);
add(t2);
gbc.gridx=0;
gbc.gridy=8;
gbl.setConstraints(b2,gbc);
add(b2);
gbc.gridx=2;
gbc.gridy=8;
add(b3);
gbc.gridx=4;
gbc.gridy=8;
gbl.setConstraints(b4,gbc);
add(b4);
b2.addActionListener(this);
b3.addActionListener(this);
b4.addActionListener(this);
setVisible(true);
setSize(400,250);
setLocation(400,200);
if(ae.getSource()==b2){
t1.setText("");
t2.setText("");
if(ae.getSource()==b4){
System.exit(0);
if(ae.getSource()==b3){
try{
String s1 = t1.getText();
String s2 = t2.getText();
ResultSet rs = c1.s.executeQuery(str);
if(rs.next()){
new Mainframe();
setVisible(false);
}else{
JOptionPane.showMessageDialog(null,"Invalid
Login");
setVisible(false);
}catch(Exception e){}
package airline.management.system;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
import javax.swing.*;
import net.proteanit.sql.DbUtils;
JTable table;
JLabel
ReservationDetails,Pnrno,Ticketid,Fcode,Jnydate,Jnytime,Source,De
stination,label,label1;
JButton Show;
new Journey_Details();
public Journey_Details(){
getContentPane().setBackground(Color.WHITE);
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
setLayout(null);
add(Source);
add(Destination);
add(Show);
setDefaultCloseOperation(JFrame.HIDE_ON_CLOSE);
ReservationDetails.setForeground(Color.BLUE);
add(ReservationDetails);
add(Pnrno);
add(Ticketid);
add(Fcode);
add(Jnydate);
add(Jnytime);
add(Source);
add(Destination);
add(comboBox);
add(comboBox_1);
add(table);
Show.addActionListener(new ActionListener(){
try{
ResultSet rs=c.s.executeQuery(str);
if(rs.next()){
table.setModel(DbUtils.resultSetToTableModel(rs));
}else{
JOptionPane.showMessageDialog(null,"No
Flights between Source and Destination");
}catch(Exception e){}
});
setSize(860,600);
setLocation(400,200);
setVisible(true);
6.3 Flight_information
package airline.management.system;
import net.proteanit.sql.DbUtils;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
import javax.swing.*;
new Flight_Info().setVisible(true);
public Flight_Info(){
getContentPane().setBackground(Color.WHITE);
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
setSize(860,523);
setLayout(null);
setVisible(true);
add(Fcode);
add(FlightDetails);
btnShow.addActionListener(new ActionListener() {
try {
ResultSet rs = c.s.executeQuery(str);
table.setModel(DbUtils.resultSetToTableModel(rs));
}catch(SQLException e){
e.printStackTrace();
});
add(btnShow);
table.setBackground(Color.WHITE);
pane.setBackground(Color.WHITE);
add(pane);
add(textField);
add(FlightCode);
add(FlightName);
add(Source);
add(Destination);
add(Capacity);
add(ClassCode);
add(ClassName);
setDefaultCloseOperation(JFrame.HIDE_ON_CLOSE);
setSize(900,650);
setVisible(true);
setLocation(400,200);
package airline.management.system;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import java.sql.*;
TextField t1,t2;
Label l1,l2;
Button b2,b3,b4;
GridBagLayout gbl;
GridBagConstraints gbc;
Font f1,f2;
super("Login");
setBackground(Color.WHITE);
f1 = new Font("TimesRoman",Font.BOLD,20);
f2 = new Font("TimesRoman",Font.BOLD,15);
gbl=new GridBagLayout();
gbc=new GridBagConstraints();
setLayout(gbl);
l1 = new Label("Username");
l1.setFont(f1);
l2 = new Label("Password");
l2.setFont(f1);
t1 = new TextField(15);
t2 = new TextField(15);
t2.setEchoChar('*');
b2 = new Button("Reset");
b2.setFont(f2);
b3 = new Button("Submit");
b4 = new Button("Close");
b4.setFont(f2);
gbc.gridx=0;
gbc.gridy=0;
gbl.setConstraints(l1,gbc);
add(l1);
gbc.gridx=2;
gbc.gridy=0;
gbl.setConstraints(t1,gbc);
add(t1);
gbc.gridx=0;
gbc.gridy=2;
gbl.setConstraints(l2,gbc);
add(l2);
gbc.gridx=2;
gbc.gridy=2;
gbl.setConstraints(t2,gbc);
add(t2);
gbc.gridy=8;
gbl.setConstraints(b2,gbc);
add(b2);
gbc.gridx=2;
gbc.gridy=8;
gbl.setConstraints(b3,gbc);
add(b3);
gbc.gridx=4;
gbc.gridy=8;
gbl.setConstraints(b4,gbc);
add(b4);
b2.addActionListener(this);
b3.addActionListener(this);
b4.addActionListener(this);
setVisible(true);
setSize(400,250);
setLocation(400,200);
t1.setText("");
t2.setText("");
if(ae.getSource()==b4){
System.exit(0);
if(ae.getSource()==b3){
try{
String s1 = t1.getText();
String s2 = t2.getText();
ResultSet rs = c1.s.executeQuery(str);
if(rs.next()){
new Mainframe();
setVisible(false);
}else{
JOptionPane.showMessageDialog(null,"Invalid
Login");
setVisible(false);
}catch(Exception e){}
new Login();
package airline.management.system;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
import javax.swing.*;
import net.proteanit.sql.DbUtils;
JTextField textField;
JTable table;
JLabel Sector;
new Payment_Details();
public Payment_Details(){
initialize();
setTitle("PAYMENT_DETAILS");
getContentPane().setBackground(Color.WHITE);
setSize(860,486);
setLayout(null);
add(Fcode);
add(textField);
add(table);
Show.setBackground(Color.BLACK);
Show.setForeground(Color.WHITE);
add(Show);
Sector.setForeground(Color.BLUE);
add(Sector);
add(FlightCode);
add(Capacity);
add(Classcode);
add(Classname);
label.setIcon(new
ImageIcon(ClassLoader.getSystemResource("airline/management/syste
m/icon/payment.png")));
add(label);
add(Cardno);
add(Phoneno);
Show.addActionListener(new ActionListener(){
try {
ResultSet rs = c.s.executeQuery(str);
table.setModel(DbUtils.resultSetToTableModel(rs));
}catch(SQLException e) {
e.printStackTrace();
});
setSize(960,590);
setLocation(400,200);
setVisible(true);
6.6 Cancellation
package airline.management.system;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
private JTextField
textField,textField_1,textField_2,textField_3,textField_4;
new Cancel();
public Cancel() {
initialize();
setTitle("CANCELLATION");
getContentPane().setBackground(Color.WHITE);
setLayout(null);
add(Cancellation);
ImageIcon i1 = new
ImageIcon(ClassLoader.getSystemResource("airline/management/syste
m/icon/cancel.png"));
add(NewLabel);
add(PassengerNo);
add(CancellationNo);
add(CancellationDate);
add(Ticketid);
add(Flightcode);
Cancel.setBackground(Color.BLACK);
Cancel.setForeground(Color.WHITE);
add(textField);
add(textField_1);
add(textField_2);
add(textField_3);
add(textField_4);
Cancel.addActionListener(new ActionListener(){
try{
c.s.executeUpdate(str);
JOptionPane.showMessageDialog(null,"Ticket
Canceled");
setVisible(false);
}catch (Exception e) {
e.printStackTrace();
});
setSize(860,500);
setVisible(true);
setLocation(400,200);
CHAPTER 7
SNAPSHOTS
TESTING
Unit Testing: in which each unit (basic component) of the software is tested to
verify that the detailed design for the unit has been correctly implemented.
System testing: in which the software is integrated to the overall product and
tested to show that all requirements are met.
Project
123
ID Mail sent to
Test case working successfully
Need xyz PM
Report
doc.
Username manager
Launched to
Test case working successfully
PM portal
Password Manager
CHAPTER 8 : TESTINGPage 72
Airline Reservation Management System 2021
Project e-farming
name
Project Xyz
description
Stored in Test case working successfully
Domain Java
the
Project type Internal database
Starting 25/02/2020
date
Ending 01/04/2020
date
Project
123
ID Mail sent to
Test case working successfully
Need xyz developer
Report
doc.
CHAPTER 8 : TESTINGPage 73
Airline Reservation Management System 2021
Table 8.1.6 : Positive Test Case of Project Manager Report
Email [email protected]
m
Stored in Test case worked
Mobile no. 9632587412 the successfully
database
Address BBSR
Developer Coder
Type
password 123456789
Profile Upload
Image
CHAPTER 8 : TESTINGPage 74
Airline Reservation Management System 2021
Project
123
ID Mail sent to
Test case working successfully
upload xyz PM
Report
doc.
Usernam Unable to
Admin
e Launch Test case failed
password Abcd admin portal
Last name
CHAPTER 8 : TESTINGPage 75
Airline Reservation Management System 2021
Email [email protected]
m
Stored in Test case worked
Mobile no. 9632587412 the successfully
database
Address BBSR
Developer Coder
Type
password 123456789
Profile Upload
Image
CHAPTER 8 : TESTINGPage 76
Airline Reservation Management System 2021
Launch admin
portal
Password 789
CHAPTER 8 : TESTINGPage 77
Airline Reservation Management System 2021
CHAPTER 8 : TESTINGPage 78
Airline Reservation Management System 2021
CHAPTER 9
9.1. Conclusion:
9.2.Future Scope
The Online Airline Reservation system is the next generation address book
which will provide these two basic services like portability, security. The future
scope includes expand the technologies like HTML and PHP we can also add
new technologies like HTML, php many more for improving the efficiency of
the software. The project will be useful for any schools and colleges with
slightly modification. Project is flexible i.e. any change /modification in
database may be performing easily. Also this project could be made web
enabled. Assumptions, if any None Assumptions: The user is familiar with basic
computer components and operations. Dependencies: The system should
work on all systems.
REFERENCES
The following references have been used by us, during all the phases of the
MSE project:
1) https://www.w3schools.com/
2) www.msdn.microsoft.com
3) Apache J Meter – http://jakarta.apche.org/jmeter/
4) http://mse.cis.ksu.edu/- For MSE Project Protfolio
5) IEEE Recommended Practice for Software RequirementsSpecifications –
IEEE Std 830-1998
REFERENCESPage 79
Airline Reservation Management System 2021
6) SLOC Metrics Tool for .NET framework 1.1
http://www.softpedia.com/get/Programming/Other-
ProgrammingFiles/SLOC-matrix.shtm
7) http://www.devartcles.com/c/b/SQL-Server/ - SQL server 2000 help
8) http://www.sitepoint.com/article/sql-server-2000-database - SQL server
2000 help
9) SQl Server 2000 download – http://www.microsoft.com/downloads/
10) http://www.c-sharpcorner.com/
REFERENCESPage 80