ITC-508 Airline Information System Project

The Airline Information System project for ITC-508 outlines the development of a comprehensive information system for XYZ, an Australian airline. It includes detailed non-functional requirements, use cases using the Event Decomposition Technique, and various UML diagrams such as class and ER diagrams. The project emphasizes the importance of usability, reliability, performance, and supportability in the system design, ensuring a user-friendly experience for both customers and staff.

Airline Information System
August 14
2017
XYZ is an Australia based airline company that provides its customers
with the airline services and solutions depicted by Maha and Submitted
to dear instructor HEIYANTHUDUWAGE.
ITC-508 Object
Modeling

Airline Information System
Table of Contents
Introduction.................................................................................................................................................3
FURPS (Non-Functional Requirements).....................................................................................................3
Use Cases – Event Decomposition Technique.............................................................................................4
Flight Reservation System.......................................................................................................................4
Travel Service Reservation System.........................................................................................................5
Human Resource Management System...................................................................................................7
Accounting and Finance System/ Sales & Marketing System.................................................................8
UML Class Diagram for the Overall System.............................................................................................10
Application Component Diagram for the Overall System.........................................................................11
ER Diagram for the Overall System..........................................................................................................12
References.................................................................................................................................................13
2 | P a g e

Airline Information System
Introduction
XYZ is an Australia based airline company that provides its customers with the airline services
and solutions. With the expansion of business and enhancement of the customer base, it has
become necessary for the organization to develop and deploy a new information system. The
primary components of the new information system for XYZ Company will include flight
reservation, travel service reservation, human resource management, accounting and finance
along with sales & marketing systems. The document covers the information on the non-
functional system requirements along with the description of the use cases. The technique that
has been used to write down the use cases for the system is the Event Decomposition Technique.
Q1: FURPS (Non-Functional Requirements)
According to FURPS, the system shall include the functional requirements in the form of
functionalities along with the non-functional requirements as usability, reliability, supportability
and performance. These are the system qualities that must be included in the system to make
sure that the overall behavior of the system is enhanced.
1. Functionality:
 Ability to make sure that ordinary customers are allowed to pay through cash or card
and regular customers are allowed to pay through flybys points or credit card. A
surcharge of 1.5% shall be applicable in both the cases (Eeles, 2014).
 Ability to allow the customers to book flights using the option of flexible dates.
 Ability to allow the customers to perform the non-flight operations such as hotel
accommodation, leisure packages, travel insurance, car rental and pick and drop
service from the airports.
 Ability to allow the customers to perform benefit administration, payroll services,
recruitment and training along with performance analysis and review.
 Ability to allow the system to handle financial transactions for the company.
3 | P a g e

Airline Information System
 Ability to extract sales and marketing reports from the system by providing the users
with the ability to preview the report and apply the filters to include only the desired
attributes in the report.
2. Usability:
 The sub-systems present in the airline information system must be easy to use.
 The system shall allow the ordinary and regular customers to conveniently use the
features in a self-explanatory manner.
 The customers must easily remember the features that are present in the system.
 The system must allow the user to extract reports associated with sales and
marketing sectors and others in the desired format.
 The level of customer satisfaction received from the system must be high by
providing them with the ability to understand the system features and the flow from
one functional area to the other in the system.
3. Reliability:
 The system must provide valid details of the flights and their availability as per the
search filters entered (Khosravi, 2004).
 The system must provide valid information regarding the non-flight operations such
as correct and updated results of the available hotels or the transportation details.
 The reports that are retrieved from the system must be as per the latest updates.
 The accounting information present in the system must be handled with the ability to
ensure that the reliability is maintained. The financial transactions done using the
system shall be displayed as per the latest results in the database.
 The system must bring forward the adequate response to the human-resource
management sub-system in terms of the validity and authenticity of the information.
4. Performance:
 The response time to access the system functionalities shall be less to make sure that
the users experience enhanced level of the system performance.
 The system shall have minimal downtime in case of a security occurrence so that
users may have undisrupted continuity of the services.
4 | P a g e

Airline Information System
 The throughput time shall be low to make sure that the users experience enhanced
level of the system performance.
 The information present in the system must be kept safe and secure to avoid any of
the security risks and concerns.
 The users must have enhanced user experience from the system in terms of
navigation and flow.
5. Supportability:
 The system shall be scaled up as per the change in the requirements such as
increased network traffic (Haque, 2012).
 The system shall be scaled down as per the change in the requirements such as
decreased network traffic.
 The system shall allow the users to access it on web and mobile platforms so that
they may have the required ease of usage.
 The system shall make sure that the users are able to access the system from any
location at any time in a remote manner.
 The database that is synced with the system must be flexible in terms of the storage
requirements. The database must allow the users to perform the operations such as
storage, addition, deletion and modification of the records as per the privileges
without any disruptions.
Q2: Use Cases – Event Decomposition Technique
Event Event
Type
Trigger Sourc
e
Activity/Use
Case
System
Response/
Output
Destinati
on
Search for
flights
State User
access the
system
Custo
mer
 Open the
system
 Enter
specific
dates and
travel
 System
shall be
displayed
 Entered
informatio
n is
Search
results
5 | P a g e

Airline Information System
destinatio
n or check
the
flexible
option
 Click on
search
button
visible
 Available
flights
shall be
displayed
Booking of
the flights
Extern
al
Payment
Initiation
Custo
mer
 Open the
system
 Search for
the flights
 Book the
flights
using
applicable
payment
mode
(Malan,
2001)
 System
shall be
displayed
 The
flights are
listed and
displayed
 Booking
confirmati
on is
displayed
Confirme
d
Bookings
Hotel
Accommod
ation and
Transport
Service
State Hotel/
transport
search
Custo
mer
 Open the
system
 Enter the
travel
destinatio
n for hotel
bookings
or
arrangeme
nt of
 System
shall be
displayed
 Available
hotel/trans
port
options
are
displayed
 Confirmat
Confirma
tion of
booking
6 | P a g e

Airline Information System
transportat
ion
 Book the
hotels/tran
sportation
service
through
applicable
mode of
payment
ion of the
bookings
is
displayed
Travel
Insurance
State Insurance
Search
Custo
mer
 Open the
system
 Search for
the
hotels/tran
sportation
services
and look
for travel
insurance
options
 Select and
apply the
applicable
option
 System
shall be
displayed
 Available
travel
insurance
options
are
displayed
 Travel
insurance
are
applied
Confirma
tion of
insurance
applied
Employee
Manageme
nt
State Search for
an
employee
and its
details
Syste
m
 Open the
system
 Enter
employee
id
 Execute
 System
shall be
displayed
 Employee
details
shall be
Managed
employee
informati
on
7 | P a g e

Airline Information System
employee
manageme
nt activity
displayed
 Employee
related
activity
shall be
executed
Recruitmen
t and
Training
State Joining of
an
employee
Syste
m
 Open the
system
 Access the
recruitmen
t and
training
option
(Wirfs-
Brock,
2001)
 Plan/
organize
 System
shall be
displayed
 Option
shall be
displayed
 Results
shall be
displayed
Managed
employee
informati
on
Information
Organizatio
n &
Manageme
nt
State Financial
transaction
Syste
m,
Custo
mer
 Open the
system
 Enter
customer
details
 Execute
financial
transactio
n or
activity
 System
shall be
displayed
 Customer
details
shall be
displayed
 The
results
shall be
displayed
Managed
financial
informati
on
Report
Generation
Tempo
ral
Selection
of the
Custo
mer
 Open the
system
 The
system
Finance
related
8 | P a g e

Airline Information System
reporting
filters
 Select the
report to
be
extracted
 Apply
filters and
extract
shall be
displayed
 The
selected
report
shall be
displayed
as
preview
 The report
shall be
generated
reports
9 | P a g e

Airline Information System
Q3: UML Class Diagram for the Overall System Note for changes: You Need to identify
the generalizations in the diagram and you have to show the aggregations within this
diagram be precise. Fix this diagram.
Generalization exists between Customer and Ordinary/Regular customer.
Booking – It is an aggregation between FLIGHT and CUSTOMER.
10 | P a g e

Airline Information System
Application Component Diagram for the Overall System Note for Changes: You have to
add more components in it, find those components from the case study and add in to the
diagram!
11 | P a g e

Airline Information System
12 | P a g e

Airline Information System
ER Diagram for the Overall System
Note for Changes: Please you don’t need to show these in ovals separately so put these words in the
boxes under the headings for example the box I have made then connect it with other boxes. According
to my instructor those ovals are confusing, so do it with rest of the boxes and remove those ovals
13 | P a g e

Airline Information System
14 | P a g e

Airline Information System
References
Eeles, P. (2014). Non-Functional Requirements. Retrieved 12 August 2017, from
http://www.architecting.co.uk/presentations/NFRs.pdf
Haque, F. (2012). Software Reliability Evaluation: A Survey Based. Retrieved 12 August 2017,
from http://ijarcet.org/wp-content/uploads/IJARCET-VOL-1-ISSUE-1-24-29.pdf
Jacobson, I. (2011). Use Case 2.0 The Guide to Succeeding with Use Cases. Retrieved 12 August
2017, from https://www.ivarjacobson.com/sites/default/files/field_iji_file/article/use-
case_2_0_jan11.pdf
Khosravi, K. (2004). A Quality Model for Design Patterns. Retrieved 12 August 2017, from
http://www.ptidej.net/publications/documents/Research+report+Quality+Models+Septembe
r04.doc.pdf
Malan, R. (2001). Functional Requirements and Use Cases. Retrieved 12 August 2017, from
http://www.bredemeyer.com/pdf_files/functreq.pdf
Wirfs-Brock, R. (2001). The Art of Writing Use Cases. Retrieved 12 August 2017, from
http://www.wirfs-brock.com/PDFs/Art_of_Writing_Use_Cases.pdf
15 | P a g e