Stakeholder Analysis and Quality Testing for Airline Information System

Introduction
This report is prepared for the case of Holiday Inc Airline Information System which has been
developed to manage passenger reservations. It is an online application which can be used by
passengers to view flight schedules, destination details, pricing, perform checks, access discounts,
and submit queries if they have any. The information system also takes care of some of the most
critical functions of the organization besides reservations such as human resource management,
sales, marketing, accounting, service reservation, and finance.
For managing human resource through the information system, the company has a database that
stores information on compensation, person, insurance, profit share, working hours, salaries, tax
deductions, and so on. This allows company to also keep track of employee performance which
helps in appraisal. Accounting and finance system produces reports on incomes, billing, assets,
outstanding, and expenses to assist management in decision making. The information is linked
across departments to create a seamless flow of information. The system also serves customers
through other assisting services information such as car hire, travel insurance, hotel booking, and
travel packages.
This report analysis the case to understand its stakeholders, quality requirements and impacts of
change that result from the implementation of the system. It identifies stakeholders and analyses
their objectives and requirements. The report also presents a plan for quality testing of the new
software and a plan for managing change in the organization (BIS, 2010).
Stakeholder analysis – objectives and business
requirements
Stakeholder analysis involves identification of stakeholders, assessment of their objectives and
needs specific to a project or a system, understanding of the impact of project on them, and the
influence they could have on the project. It is important that stakeholders are satisfied with the
developed solution and thus, this analysis is an important step in business analysis.
The key stakeholders of the airline information system are customers, airline staff, sponsor, system
developers, vendors, project manager, domain expert, and governing bodies. For each of these
stakeholders, their characteristics can be identified related to their authority, interest in project,
role, attitude towards project, and decision making (Jainendrakumar, 2016).
Stakeholder Level of
Influence
Interest Roles &
Responsibilities
Objectives and
needs
Decision
making
Project
sponsor
High High Assess
business case
and approve
funds
The
information
system should
deliver good
ROI. The
The sponsor
decides on the
budget that is
assigned for
the

sponsor needs
to review the
project plan
for its viability
to approve
budget
development
of the airline
information
system (LIM,
et al., 2005)
Project
Manager
High High Initiate, plan,
execute,
monitor and
report project
progress
Know
everything
about the
project
essential for
planning,
monitoring
and progress
reporting
Project
manager takes
day to day
decision on
resource
assignment,
task
assignment,
and project
control
Vendors Moderate Moderate Supply systems
needed for
installation
Should have
clarity on
specifications
of systems
needed and
payment for
products and
services on
time
Vendor does
not have any
control over
specifications
Developers Low Moderate Develop the
information
system
Should have all
the
information
about
company
functions,
reports, and
project
requirements
and should be
given sufficient
time for
development
Developers
take day to
day decisions
about coding
and also on
testing
(Ponnappa,
2014)
Domain
Expert
Moderate Moderate Provide
insights on the
subject to the
team of
developers
Should know
the objectives
of the solution
and the project
requirements
Can decide on
the functions
to include in
the solution
that are
essential for
operations
+Staff Low Moderate Provide
support to
project team
when needed
Should be kept
informed as
well as
involved in
requirement
gathering as
They can
provide inputs
during
requirement
gathering
(PMI, 2013)

they would be
using the
system at the
end
Governing
bodies
Moderate Moderate Permits and
approvals for
regulatory
concerns
Should have all
necessary
formalities of
documentation
provided
Regulatory
decisions
Customers High Moderate Provide inputs
for
development
Should be kept
in mind while
planning
features for
the application
Decide on the
features that
would be
needed in the
information
system
Testers Low Low Perform
testing on the
developed
solution
Should have
clear
specifications
of
performance
requirements
and testing
They perform
tests as per
the
requirements
documented
and based on
the results
decide if the
solution is
good to go live
or need
alterations
(Baguley,
2008)
A RACI matrix can be used for identifying roles of these stakeholders for the Airline information
system project which would help to identify if they are responsible or accountable for the project or
just need to be involved through consulting or information sharing. The responsibilities can be
defined along the whole project stages that include initiation, planning, execution, monitoring,
control and system testing (Beringer & Kock, 2013). The analysis of the stakeholders presented
above can help identify their roles and plot them in the matrix as follows:
Stakeholder Initiation Planning Execution Monitoring &
Control
Testing
Project
sponsor
RAC RA CI CI I
Project
Manager
RAC RAC RAC RAC CI
Vendors I CI I I CI
Developers I CI RAC CI CI
Domain Expert CI CI I I I
Staff I CI I I I
Governing
bodies
CI I I I I
Customers CI CI I I CI