Airline Information System For Holiday Inc

ISYS324 Faculty Of Law And Business Analysis

Identification of stakeholders

The aim and objective of the project is to develop a new airline information system for Holiday Inc. which will support their daily activities. The proposed information system for Holiday Inc. will include several modules such as human resource management, travel services such as hotel booking and car hire, airline reservation, marketing and sales, and finance and accounting. The new airline information system should offer flight booking and reservation management services. It should distinguish the two type of users, that is, ordinary clients who infrequently use the system and regular flyer who regularly use the system. Flight reservation system should provide many alternatives with cost effective options when ordinary clients choose the option of flexible with dates while looking for negotiable flights. Besides, the flight reservation system should have the ability to add, maintain, display and deduct the history of regular flier points and offer a satisfying travel convenience and experience.

In addition, a travel service reservation system is required by Holiday Inc. to provide regular flyer and ordinary clients other non-flight amenities such as packages, hotel, travel activities, car hire, and travel insurance. The system should create extra sources of income and at the same time offer an excellent travel experience to clients. Additionally, the system should allow clients the order by removing or adding non-flight amenities. Holiday Inc. also need an HRM system to offer functions connected to various functions of human resource such as payroll, performance analysis, benefits administration, training and recruiting and review into a single package (McGuigan, 2015). A sales and marketing system are also needed to create revenue by looking for customers and making sales (Shannon, 2012).

An airline information system for Holiday Inc. will be designed and implemented. A well-designed database will support the system, allowing all available information of airline to be connected together and be accessed with ease via one point. The airline information system will offer a friendly user interface between airline employees and customers (Rouse, 2015). The system will also support personal information of the user and regular registration.

Figure 1: Context Diagram

The airline information system is majorly concentrated on two types of audiences: the end-user or the customer and the system administrator (Borodescu, 2013). Some of the main functions of the system can be grouped under the two groups; the user and the administrator.

End-user/Customer activities

Figure 1: use case diagram of the Customer

Production of plans for Quality assurance testing

The use case diagram above shows all the activities or functions that a customer or user can carry out on the system. The activities are comprehensively discussed below:

Home page: the system user homepage can be accessed by the user. The user logs into the system and search for information pertaining flights, motels and packages.

Login and register: the system offers a client registration information page, where the user can key in his or her information and register. Besides, he or she can generate a password and username. In addition, the user can change the registration details in case of a change of information such as email address (Chaffee, 2012).

Booking flights: the client can look for flights available and book a seat on the flight by buying a ticket.

Book motels: the system will provide different deals for booking motels.

Book packages: the functionality resembles that of booking a motel, except that the client can search for different touring packages available at the destination of the person (Holiday, 2014).

Contact the company: the client can call the firm if he or she has questions or concerns connected the bookings he has made.

Booking instructions: the system offers guidelines to the clients on how to make a motel or airline ticket reservations along with the various packages.

Login/logout: the administrator logins to the system to make some adjustments by deleting, adding or modifying the information of the system database. After making the required adjustments, he or she has to logout the system to avoid data misuse (Crosby, 2017).

Add/modify client’s details: many clients will register into the system daily and others will unsubscribe from the system. Only the administrator is allowed to change the database in an appropriate way.

Add/modify flight details: the administrator is only person who has the permission to delete, add or modify details of the flight. At times, customer can cancel flights for various reasons.

Add/modify details of a motel: the administrator delete, add and modify details connected to various motels. The information includes rooms available and the prices of the motel, among others.

Reservations Cancellation: at times a client may cancel a reservation. As such, the administrator manages such unique cases and sends an email confirmation to the client after deleting the particular transaction (Django Software Foundation, 2013).

Email confirmations: when a client cancels or make a reservation, it is the responsibility of the administrator to send emails to the client to confirm the transaction.

Specification of Requirements

Figure 2: use case diagram of the administrator

ER Diagram

Figure 2: Holiday Inc. Entity Relationship Diagram

Data Dictionary

The data dictionary contains the logical properties of the data stores of the system including flight details, customer details, hotel details, reservation details, payment details, among others which helps in determining requirements of the database during design and development of the system. Data dictionary is useful in managing information in bigger system like the one required by Holiday Inc., communicate and provide a standard meaning for all the elements of the system, documentation of system features, identify omissions and errors in the system, and facilitate system evaluation to identify any changes needed (GazetteLive, 2011). The following tables represent data dictionary for various activities and events that will be carried out by the system:

Name of the field	Explanation	Type of data	Size	Constraints
Company_id	company identifying number	int	20	PRIMARY KEY
company_details	Company information	Varchar	200	NOT NULL

Flight details

Name of the field	Explanation	Type of data	Size	Constraints
Airline_id	Flight identifying number	int	20	PRIMARY KEY
Airline_details	Name of the flight	Varchar	200	NOT NULL

Customer details

Name of the field	Explanation	Type of data	Size	Constraints
Customer_id	Unique identification number	int	20	PRIMARY KEY
customer_details	Name	Varchar	200	NOT NULL
Address_details	Address information	Varchar	200	NOT NULL

Booking details

Name of the field	Explanation	Type of data	Size	Constraints
Booking_id	Flight identifying number	int	20	PRIMARY KEY
Customer_id	Name of the flight	int	20	FOREIGN KEY
Status_code	Booking status	int	20	FOREIGN KEY
Company_id	Holiday Inc	int	20	FOREIGN KEY
Date_of_booking	The date when the customer made the booking	int	20	NOT NULL
Booking_details	Booking information	int	20	NOT NULL

Payment details

Name of the field	Explanation	Type of data	Size	Constraints
Payment_id	Payment number	int	20	PRIMARY KEY
Booking_id	Booking identification number	int	20	FOREIGN KEY
booking_details	Name of the flight	Varchar	200	NOT NULL

Booking status

Name of the field	Explanation	Type of data	Size	Constraints
Status_code	Unique code	int	20	PRIMARY KEY
Status_description	Details of the reservation	Varchar	200	NOT NULL

The following are the non-functional requirements:

The system should ne user friendly and enable the users to easily interact and navigate through the system.

The system should be available 24/7 for customers to make their bookings are reservations (Encyclopedia Britannica, 2015).

The system should be secured to ensure that customer and business information is secured.

The system should be flexible enough and allow the company to add more features and functionalities in the future.

The system should be able to offer high performance to users and process their request using the shortest time.

Holiday Inc. is an airline company based in Australia and has grown gradually overtime and want to improve the current information system to add more features and support their daily operations. Have an integrated system like the one proposed by the business that includes travel service reservation, finance and accounting, flight reservation, marketing and sales, and human resource management. This will enable the customers to have a “one-stop-shop” system for all their travel needs (Atkinson, 2015).  Centralizing the reservation information system offers an effective mechanism that will remove the mistakes that customers often make during the booking process. Additionally, customers will be able to track their booking details and status. By giving the customers extra services like car hire and hotel reservation they will be able to be more loyal to Holiday Inc. The system will enable the company to generate more revenue and reduce operational costs because most process will be automated (Johanson, 2014). Moreover, the finance and accounting module will help in managing company revenue both income and expenses and can be able generate the various finance reports such as expenditure reports, profits reports and many others. The Human resource module will facilitate easy recruitment, training, payroll management, and easy management of employees (Rouse, 2015). The sales and marketing module will help the company to learn about their customers and their preferences and focus on them. This will lead to increase in sales.

Specification of acceptance criteria

System acceptance by users is very important, therefore, several test criteria need to be performed in order to check all the user requirements have been met (Kaplan-Moss, Holovaty, 2017). The following acceptance tests need to be done:

Unit/ module testing is carried out to ensure that ever module of the system is working properly and gives desired results.

Integration testing is performed to check if all the modules are working and collaborating together correctly

Recovery testing is done to check on the ability of the system to recover from errors (Ross, 2013)

Security testing is very essential to check for the security abilities of the system to protect company and customer information from internal and external threats.

Acceptance testing is done after all the other tests have been carried out where users interact with the system to check if the system meets all the requirements set out (Mozilla Developer Network, 2015).

Conclusion

By implementing an integrated system like the one proposed by Holiday Inc., the company will gain several advantages including cost effectiveness, easy management of resources, improved performance among other benefits. Also, will enable the customers to have a “one-stop-shop” system for all their travel needs.  Centralizing the reservation information system offers an effective mechanism that will remove the mistakes that customers often make during the booking process. However, system acceptance by users is very important, therefore, several test criteria need to be performed in order to check all the user requirements have been met.

Atkinson, B. (2015). How does online check in work? Available: https://www.travelsupermarket.com/blog/how-does-online-check-in-work/. Accessed: 18th October, 2018.

Borodescu, C. (2013). Web Sites vs Web Apps: What The Experts Think. Available: https://www.visionmobile.com/blog/2013/07/web-sites-vs-web-apps-what-the-experts-think/. Accessed: 18th October, 2018.

Chaffee, A. (2012). What is a web application? Available: https://www.jguru.com/faq/view.jsp?EID=129328/. Accessed: 18th October, 2018.

Crosby, T. (2017). How Airline E-Tickets Work. Available: https://adventure.howstuffworks.com/destinations/travel-guide/tips/how-airline-e-tickets-work.htm/. Accessed: 18th October, 2018.

Django Software Foundation. (2013). Django Documentation, FAQ: General. Available: https://docs.djangoproject.com/en/1.8/faq/general/. Accessed: 18th October, 2018.

Encyclopedia Britannica Online. (2015). Website. Available: https://www.britannica.com/topic/Web-site/. Accessed: 18th October, 2018.

Encyclopedia Britannica. (2015). HTML. Available: https://www.britannica.com/technology/HTML/. Accessed: 18th October, 2018.

GazetteLive. (2011). The benefits of booking flights online. Available: https://www.gazettelive.co.uk/news/local-news/benefits-booking-flights-online-3693877/. Accessed: 18th October, 2018.

Holiday, L. (2014). Web design vs web development: what’s the difference? Available: https://www.skilledup.com/articles/web-design-vs-web-development-whats-difference/. Accessed: 18th October, 2018.  

Johanson, M. (2014). How The Airline Industry Has Evolved In 100 Years of Commercial Air Travel, Available: https://www.ibtimes.com/how-airline-industry-has-evolved-100-years-commercial-air-travel-1524238 Accessed: 18th October, 2018.

Kaplan-Moss, J., Holovaty, A. (2017). The Definitive Guide to Django. New York. Apress.

McGuigan, B. (2015). What is web design? Available: www.wisegeek.org/what-is-web-design.htm/. Accessed: 18th October, 2018.

Mozilla Developer Network. (2015). Available : https://developer.mozilla.org/en-US/Learn/Getting_started_with_the_web/JavaScript_basics/. Accessed: 18th October, 2018.

Ross, G. (2013). Airline Reservation Systems History 101. Available: https://www.cbtravel.com/blog/2013/11/airline-reservation-systems-history-101/. Accessed: 18th October, 2018.

Rouse, M. (2015). e-commerce (electronic commerce or EC) definition, Available: https://searchcio.techtarget.com/definition/e-commerce/. Accessed: 18th October, 2018.

Rouse, M. (2015). Website definition. Available: https://searchsoa.techtarget.com/definition/Web-site/. Accessed: 18th October, 2018.

Shannon, R. (2012). What is HTML? Available: https://www.yourhtmlsource.com/starthere/whatishtml.html/. Accessed: 18th October, 2018.