Horizon Air Information System

By: Brian Grossman

OMIS 106
Professor Zimbra

For my project I would like to create an information system for Horizon Air to help support their operations as a regional
airline based in Seattle, Washington. Airlines today have a huge need for information systems due to the high volume of
customers flying and the need to store and access mass amounts of information. Horizon Air serves 52 cities in the United States,
Canada, and Mexico.
My proposed information system will cover the entire booking flight process, check in process, and post flight procedure
process. These processes are temporally joined because they are done sequentially in time. The first major process is booking the
flight. This process begins with customers logging into to our website online. If they are existing customers and have already
made an account, they simply just have to input their login credentials. New customers must input all of their key information so
the system can store it for future reference. The next step is that the customers must be approved before they start selecting
flights. Customer information will be sent to the DHS and TSA to see if customer is on any no-fly lists. The DHS and TSA will
send their approvals and the passenger will be approved. The next step is for the customer to select their desired dates and
airports of travel. Flight information will be pulled from the flight data store and shown to the customer. The customer will than
select their desired flight. The next step is for the customer to select their desired seating on the flight. Seating information will
be retrieved from the seat data store and shown to the customer. The customer will than make their selection. Next, the system
will calculate pricing information based on the flight and seat information selections from the customer. The customer will than
select whether he or she will be paying with a credit card or with their miles. After the payment is processed the customer will be
issued an E-ticket which they will be expected to provide during day of check-in and an e-mail confirmation.
The next major business process is when the customer arrives at the airport to check-in. The system will first verify
customer information by having the customer provide their name. The system will then retrieve customer information from the
data store to verify customer. Next the system will accept luggage from the customer. The system will retrieve flight information
from the data store and issue a tag for each bag of luggage. The system will than properly allocate each bag of luggage to its
appropriate plane. Finally, the system will issue the customer their boarding pass.
The last business process I have is finalizing post flight procedures. The first step in this process is to update the
customers mileage account to reflect the number of miles gained from current flight. For this to happen, the system will retrieve
pricing information from the data store and update the customers mileage data store. The last step to this process is that the
system will issue a customer feedback survey to the customer exactly one week after the flight.

Requirements Definition
Functional Process Oriented
(Before Flight)

Book Flight
o New Customers
The system will accept new customer information
The system will store new customer information in the customer data store
o Existing Customers
The system will accept existing customer information
The system will retrieve customer information from the customer data store
The system will provide customer information to the customer for validation
The system will accept updates to existing customer information
The system will update existing customer information in the customer data store
o Approve passengers
The system will accept customer information from the customer for verification
The system will verify customer information for approval to fly
The system will send customer information to the DHS
The system will send customer information the TSA
The system will accept passenger approval from the DHS
The system will accept passenger approval from the TSA
The system will store approved passengers in the approved passenger data store
o Select Flights
The system will accept travel dates desired by the customer
The system will accept airports desired by the customer
The system will retrieve available flights from the flight data store
The system will provide available flights to the customer
The system will accept the flight selection by the customer

o Select Seats
The system will retrieve flight information from the flight data store
The system will retrieve seat availability information from the seat data store
The system will provide the available seat information to the customer
The system will accept seat selection from the customer
o Finalize Flight Booking
Calculate total
The system will retrieve flight information from the flight data store
The system will retrieve seat information from the seat data store
The system will generate a price for the plane ticket
The system will provide the price generated to the customer
The system will store pricing information in the pricing data store
Process payment
Dollars
The system will accept payment information from the customer
The system will verify the payment information through the credit card clearinghouse
The system will send payment information to the credit card clearinghouse
The system will accept payment approval from the credit card clearinghouse
Mileage program
The system will retrieve customer mileage information from the data store
The system will verify customer mileage payment information
The system will send customer mileage information to the manager
The system will send pricing information to the manager
The system will receive mileage payment approval from the manager
The system will update customer mileage data store info to reflect payment
Issue E-ticket
The system will accept payment approval
The system will issue an E-ticket to the customer
The system will send an e-mail confirmation to the customer

Finalize Booking
The system will update flight information in the flight data sore
The system will update seat information in the seat data sore
The system will update flight reservations in the flight reservation data sore
The system will notify DHS of flight reservation
o Maintain Flight/Seat Info
The system will retrieve flight information from the flight data store
The system will retrieve seat information from the seat data store
The system will provide flight and seat information to management
The system will accept flight information update from management
The system will accept seat information update from management
(Day of Flight)

Check-in
o Verify customer information
The System will accept customer information from the customer
The System will accept E-ticket issued to the customer
o Check baggage
The system will accept desired luggage to be checked on to the flight from the customer
The system will retrieve flight information from the flight data store
The system will issue a tag for each bag of luggage that the customer has
The system will properly allocate luggage to its appropriate plane
o Issue boarding pass
The system will retrieve flight information from the flight data store
The system will retrieve seat information from the seat data store
The system will issue a boarding pass to customer

(After Flight)

Finalize post flight procedure

o Update mileage
The system will retrieve pricing information from the pricing data store
The system will update customer mileage information in the customer mileage data store
o Issue customer feedback survey
The system will send an e-mail containing the customer feedback survey to the customer one week after the flight
The system will retrieve customer information from the customer data store
The system will retrieve flight information from the flight data store
The system will retrieve seat information from the seat data store
The system will determine when to send the survey
The system will send out the e-mail containing the customer feedback survey
Functional Information Oriented

The system will contain Horizon Air flight information

The system will contain approved passenger information
The system will contain seat information
The system will contain flight reservation information
The system will contain customer information
The system will contain pricing information
The system will contain customer mileage information

Non-Functional Operational

The system will run on the Windows OS (XP or later)

The system will interface with the credit card clearinghouse
The system will interface with the DHS
The system will interface with the TSA
The system will interface with the e-mail system

Non-Functional Performance

The system will support more than 1,000 concurrent users

The system will be online and available 24/7
The system will be able to approve passengers in less than 2 minutes
The system will be able to verify payment information in less than 30 seconds
The system will be constantly updating the seating chart according to reservations

Non-Functional Security

Customer payment information will be encrypted in transmission to and from the credit card clearing house
Only Horizon Air staff will be able to update flight and seat info
Passenger information will only be given out to the DHS and TSA for approval

Non-Functional Cultural / Political

The system will adopt the United Airlines logo and color scheme
The system must run on HP servers (a Horizon Air partner firm)
The system will abide by any flight requirements set forth by the TSA

Use Case Name: Book Flight

Actor: Customer
Description: This use case describes how a customer books a flight with Horizon Air.
Trigger: A customer logs onto the Horizon Air website to book a flight.
Type: External
Preconditions
1. Horizon Air website is online and available
2. Horizon Air flight information system is online and available
3. Customer has made an account on the Horizon Air website
4. Credit card clearinghouse is online and available
Normal Course
1. Customer information
1.1 If new customer
1.1.1 New customer provides customer information
1.1.2 System creates customer record in customer data store
1.2 If existing customer
1.2.1 Existing customer provides customer name
1.2.2 System retrieves existing customer information data store
1.2.3 Existing customer information is presented to customer
1.2.4 Customer provides updated customer information
1.2.5 System updates customer record in data store
2. Approve passenger
2.1 The system will verify customer information for approval to fly
2.1.1 The system will send customer information to the DHS
2.1.2 The system will send customer information to the TSA
2.1.3 The system will receive passenger approval from the DHS
2.1.4 The system will receive passenger approval from the TSA
2.1.5 The system will store approved passengers in data store
3. Select flight

Information for Steps

I: customer information
O: customer record
I: customer name
I: customer information
O: customer information
I: customer information update
O: customer record update

O: customer information
O: customer information
I: DHS passenger approval
I: TSA passenger approval
I: approved passengers

3.1 System will accept desired travel itinerary from the customer
3.1.1 System will accept travel dates desired by the customer
3.1.2 System will accept airports desired to travel by the customer
3.2 System will retrieve available flights from the Horizon Air flight data store
3.3 System will provide available flights to the customer
3.4 Customer selects desired flight from available flights
4. Select seat
4.1 The system will retrieve flight information from the flight data store
4.2 The system will retrieve seat availability information form the seat data store
4.3 The system will provide available seats to the customer
4.4 Customer selects desired seat
5. Finalize flight booking
5.1 Calculate total
5.1.1 System will retrieve flight information from the flight data store
5.1.2 System will retrieve seat information from the seat data sore
5.1.3 System will calculate pricing information
5.1.4 System will provide pricing information to the customer
5.2 Process payment
5.2.1 If paying with cash/credit card
5.2.1.1 System will accept payment information from the customer
5.2.1.2 System will verify payment information
5.2.1.2.1 System send payments information to CC clearinghouse
5.2.1.2.2 System receives payment approval
5.2.2 If paying with miles
5.2.2.1 System will retrieve customer mileage information from the
data store
5.2.2.2 System will retrieve pricing information from data store
5.2.2.2 System will verify customer mileage information
5.2.2.2.1 System will send customer mileage info to manager
5.2.2.2.2 System will send pricing information to the manager
5.2.2.2.3 The system will receive customer mileage payment

I: travel date information

I: airport travel information
I: available flight information
O: available flight information
I: flight selection
I: flight information
I: seat availability information
O: seat availability information
I: seat selection

I:flight information
I: seat information
O:pricing information

I: payment information
O: payment information
I: payment approval
I: customer mileage information
I: pricing information
O:customer mileage information
O: pricing information

approval from the manager

5.2.2.2.4 System will update customer mileage data sore
5.3 Issue E-ticket
5.3.1 The system will accept payment approval
5.3.2 The system will issue customer an E-ticket
5.3.3 The system will send an e-mail confirmation to the customer
6. Maintain flight/seat info
6.1 System will retrieve flight information from the flight data store
6.2 System will retrieve seat information from the seat data sore
6.3 System will provide flight and seat info to management
6.4 System will update flight information based on management updates
6.5 System will update seat information based on management updates

I:mileage payment approval

O: customer mileage information update
I: payment approval
O: E-ticket
O: e-mail confirmation
I: flight information
I: seat information
O: flight and seat info
O: flight information update
O: seat information update

Postconditions
1. New customer information is stored in the customer data store
2. Existing customer information is updated in the customer data store
4.Customer mileage data store was updated in the customer mileage data store if customer chose to pay with miles
5. Customer will be provided with an E-ticket and e-mail confirmation
6. Flight information was updated in the flight data store
7. Seat information was updated in the seat data store
8. Flight Reservation information was updated in the flight reservations data store
Inputs
Customer information
Customer name
Customer information
Customer information update
Customer information
DHS passenger approval
TSA passenger approval

Source
Customer
Customer
Customer data store
Customer
Customer
DHS
TSA

Outputs
Customer record
Customer information
Customer record update
Customer information
Customer information
Available flight information
Available seat information

Destination
Customer data store
Customer
Customer data store
DHS
TSA
Customer

Approved passengers
Travel date information
Airport travel information
Available flight information
Flight selection
Flight information
Available seat information
Seat selection
Flight information
Seat information
Payment information
Payment approval
Customer mileage information
Pricing information
Mileage payment approval
Flight information
Seat information

Approved passenger data store

Customer
Customer
Horizon Air flight data store
Customer
Flight data store
Seat data store
Customer
Flight data sore
Seat data store
Customer
CC clearinghouse
Customer mileage data store
Pricing data store
Manager
Flight data store
Seat data store

Pricing information
Payment information
Customer mileage info
Pricing information
Customer mileage info update
E-ticket
E-mail confirmation
Flight information
Seat information
Flight information update
Seat information update

Customer
Customer
CC clearinghouse
Manager
Manager
Customer mileage data store
Customer
Customer
Manager
Manager
Manager
Manager

Use Case Name: Check-in

Actor: Customer
Description: This use case describes how a customer checks in with Horizon Air on the day of the flight.
Trigger: The customer has arrived at the airport and is ready to check in
Type: External
Preconditions
1. Horizon Air information system is online and available
2. Customer has already booked flight and has received an E-ticket
3. Customer has arrived on designated date of travel
4. Airport is open
5. Flight is not delayed and expected to take off according to schedule
Normal Course
1. Verify customer information
1.1 The system will accept customer name from the customer
1.2 The system will retrieve customer information from the customer data store
1.2 The system will accept E-ticket from the customer
2. Check baggage
2.1 The system will accept luggage desired to be checked from the customer
2.2 The system will retrieve flight information from the flight data store
2.3 The system will issue a tag for each bag of luggage
2.4 The system will send luggage to its appropriate flight
3. Issue boarding pass
3.1 The system will retrieve flight information from the flight data store
3.2 The system will retrieve seat information from the seat data store
3.3 The system will issue a boarding pass to the customer
Postconditions
1. The system will issue a boarding pass to the customer

Information for Steps

I: customer name
I: customer information
I:E-ticket
I: luggage
I: flight information
O:luggage
I: flight information
I: seat information
O: boarding pass

Inputs
Customer name
Customer information
E-ticket
Luggage
Flight information
Seat information

Source
Customer
Customer data store
Customer
Customer
Flight data store
Seat data store

Outputs
Luggage
Boarding pass

Destination
Plane
Customer

User Interface

Management User Interface