Web Application Project Report - Module Name, Semester 1, University

This report details the development of a web application, focusing on a flight booking system with both user and administrator functionalities. The user interface includes pages for viewing available flights, booking flights, managing a wish list, and viewing bookings. The administrator section allows for flight management, including adding, updating, and deleting flights, as well as viewing bookings. The application uses a basic MVC structure, with the database running on MySQL. Asynchronous programming is implemented using AJAX for features like flight searching and adding items to the wish list, enhancing the user experience. The report covers the different pages and functionalities, comparing the implementation with the initial requirements document.

COVER PAGE

Introduction
This report provides a detailed explanation of the web application and the features accomplished in
comparison to the requirements document.
Web application
The web application has been designed and developed to be used by two types of users;
 Normal user
 Administrator
Normal user
The normal user accesses the public part of the web application which is accessed by the public. This
part of the web application is where people interested in making bookings can view the available flights
and then make bookings or add the flights to a wish list and then perform bookings from the wish list.
This part of the web application has the following pages.
 Home page- this is the landing page of the web application and is the first page that visitors sees
when they first open the web application through a web browser. In term of functionalities, the
home page does not include many features

Figure 1: Home page
 Find flight page- This page contains details about different flights that are provided by the
company and their respective details. From this page, the user can search for a flight based on a
certain parameter. For example the user can search for all domestic or European flights by
selecting the search by type parameter. The search happens asynchronously meaning that
communication between the client and the server side happens in asynchronous cycles. This
means that no page reload happens when a user searches for a flight. Asynchronous
programming has been achieved by use of Ajax. The After searching and viewing details about
flights the user can book or add the flight to his or her wish list. Booking redirects the user to the
book flights page whereby if the user is logged in to their account then the booking happens
automatically and if not the user has to register to complete the booking. Add a flight to the
wish list happens asynchronously.

Figure 2: Find flights page
 Bookings page- this page is used by the user to show their bookings. The bookings are
structured and formatted in a tabular format.

Figure 3: Bookings page
 My wish list page- this page shows the wish list of the user in a tabular format. The user can
make a booking from this page.
Figure 4: Wish list page
Administrator
This part is accessed only by the administrator to manage flights and to view bookings. The
administrator section of the web application has the following pages.
 Login page- The login page is used by the administrator to login on order to access the admin
dashboard.

 Flights page- The flights page is used to manage flights. The user can view all the fights added to
the system and perform actions like updating or deleting the flight.
 Add flight page- This page is used by the administrator to add a new flight to the database.

 View bookings page- This page is used by the administrator to show all the booked flights by
various members.
Conclusion
The web application has been developed using basic MVC as not all the pages fully implement the MVC
style of development. The database runs on MySQL. Different pages implement different requirements
specified in the requirements document.