Head First

2. Methodology
In developing the system an orderly methodology was followed. In accordance with the stages of the Iterative Waterfall Model, the project was broken down into a series of steps. Once this was completed, parallel tasks were identified to reduce the development time and tasks were divided among group members.

2.1 Requirements and Analysis
2.1.1 General Requirements for the Whole System
Functional Requirement 1: Create User Accounts and Update User Account Info.
 Only the administrator access allows creating user accounts and tasks that are secure and not meant for other users.
 Each access level and its tasks are different. A staff member cannot access the management levels user interface. Each user will be assigned an access level according to his/her job level.
 In order to change any login details, etc, the users will have to contact the admin to get this done.

Functional Requirement 2: User Login
Before any user performs any tasks in the Air Kingdom system, they must enter their correct username and password that is assigned to them. The Air Kingdom system identifies its users by the username and password that is stored in the database. This also defines what the access levels of the user are.

Functional Requirement 3: Report Generation
Generating Reports is one of the most important parts of any system. Each user can generate and access reports according to their privilege levels. The types of reports

generated vary from section to section. The following are the reports that will be generated by the Air Kingdom system; they will be explained in detail in their respective modules.  Airline reservation report
 Local Tours Booking Report
 Tour Report
 Vehicle Management Report
 Financial Reports
 Airline Reservation/Cancellation Report
 Customer History Report

2.1.2 Airline Reservation Information Management System
Functional Requirement 3: Insert Reservation Details
Whenever a client (company) makes a ticket reservation, once this is confirmed, this information is entered into the system. This is a major requirement as this will replace the current manual system. These entries will be categorized in a well formatted manner to give a good interface for the users.

Functional Requirement 4: Update Reservation Details
It is normal for mistakes to happen when making data entries despite the several validation checks, in order to rectify this, an option is available to update the reservation details. However this cannot be used when postponing a ticket reservation date as there is a separate mechanism for this, where a penalty has to be applied.

Functional Requirement 5: Insert New Client
When a new company (client) is obtained by Air Kingdom, their information is recorded.
When they send their employees abroad, the new entry will be made in the system via the selected company. Therefore it is important to have this function to store the details of which company each individual belongs to.

Functional Requirement 6: Update New Client
This is a basic functionality that should be included wherever inserting new entries is involved. In the case where a client changes his address or contact details, etc, this can be easily done.

Functional Requirement 7: Monthly Booking Report
This reporting function allows us to get an overview of all the bookings happening on a monthly basis. This way the management can get an overview of which company (client) sends their employees abroad the most.

Functional Requirement 8: Invoice Printing
With this function we can print invoices to send to the clients in order to receive payment. Since the invoices will be automatically generated via the system, the chances of any calculation mistakes will be highly reduced.

2.1.3 Local Tour Booking System
Functional Requirement 9: Insert New Booking
This function is used when customers want to make a booking for local tours. A preexisting tour will be selected and the customers will be selected for the booking. This information will be vital to make sure a particular tour is not over-booked. Appropriate validations are included to make sure that a single customer is not included in a booking twice. Functional Requirement 10: Update Booking
In case, the numbers of people for a particular booking are changed, this can be updated here. People can be removed from a booking or added to a booking according to tour selected for that booking. A single booking can only be for one tour whereas one tour can have multiple bookings from distinct customers.

Functional Requirement 11: Delete Booking
When a customer decides that they do not want to travel, their booking will have to be cancelled. This will have open up more slots for the tour which the deleted booking was allocated to.

Functional Requirement 12: Ticket Printing
After a booking is confirmed and the payment is made, the customers will be handed over tickets which will be printed through the system. The customers will then have to

present these tickets to the vehicle driver before boarding the vehicle on the allocated tour day.

Functional Requirement 13: Monthly Booking Report
This report generating function will give an overview of the bookings being made in particular time duration. This will help the management analyze the peak and off-peak times for travel and hence influence pricing decisions.

2.1.4 Tour Management System
Functional Requirement 14: Insert New Tour Details
Every 2-3 months, new tours are created with careful planning. These are mostly on holidays, and the destinations not very far away as they are one-day trips. Therefore the location of the tour, the no. of maximum customers this tour can accommodate and date, etc are stored through this function.

Functional Requirement 15: Update Tour
If there are certain changes that take place after the tour has been created, this can be done through this function. Sometimes, due to weather conditions the dates might need to change or the destination too might change according to customer requirements who want a custom tour created for them. This function helps to fulfill those requirements.

Functional Requirement 16: Delete Tour
In the case where a tour has to be cancelled for some reason, this can be done through this. In order to make the functionality better, only tours that have zero bookings allocated for it can be deleted. This will help to reduce any errors that might occur by the users of the system.

Functional Requirement 17: Insert Hotel
There are hotels that the client Air Kingdom, have partnered with who allow the tourists to stay at their hotels when on tour. Whenever, a new hotel has partnered with the client, the basic information regarding the hotel is stored here. Hence when allocating a hotel for a tour or when creating reports, there will be clear information as to which hotel a certain tour was allocated to.

Functional Requirement 18: Update/Delete Hotel
In some cases, the basic information held about the partnered hotels in the system database needs to change; this function will allow those changes to take place. Also if a hotel is no longer partnered with Air Kingdom, they can be deleted through this function. Functional Requirement 19: Tour Report
This reporting function will allow creating a basic report of the tours that were created in a certain time period. This will allow the management to see which months have the most tours and hence more resources can be hired during that time.

2.1.5 Vehicle Management System
Functional Requirement 20: Adding Vehicles
When Air Kingdom acquires a new vehicle, information regarding the vehicle has to be stored in the system. Most importantly, the vehicle Registration number, etc. It is after a vehicle is added, that it can be allocated for tours. Therefore this function is a must for the system.

Functional Requirement 21: Updating Vehicle Details
Sometimes there may be a requirement for the details of a particular vehicle to be updated. Instances such as, when a vehicle is repainted or the driver of the vehicle is changed, then those changes will have to be made through this function. However, the registration no. of a vehicle cannot be changed as it is a permanent record that a vehicle has. Functional Requirement 22: Deleting Vehicles
When a vehicle is no longer is a running state it may have to be removed from the system. Details such as the price it was sold at, and the person it was sold to will have to be recorded for future purposes. Hence the deleted vehicle is not completely removed from the database; it is only moved to a different section.

Functional Requirement 23: Changing Vehicle Status
The main use of this function is to allocate the existing vehicles for a tour or for maintenance, as required. This function is very important as the state of the vehicle is managed through this. Vehicles can either be assigned for a tour or for maintenance.
The important validation rule here is that, only vehicles that have not been allocated for a tour or maintenance on a particular date can be assigned.

Functional Requirement 24: Vehicle Report
This report will give an overview of the status of vehicles at Air Kingdom. The user can select a particular date range, the desired vehicle and the output displayed will show information of the particular vehicle, whether it was sent for maintenance or if it was allocated for a tour.

2.1.6 Airline Reservation Cancellation/Postponement
Functional Requirement 25: Ticket Cancellation
In some situations, when a company confirms a booking of a ticket for their employees, they later happen to cancel the reservation due to some reason. In this case, the information in the system has to be changed. When a cancellation occurs the company is liable to pay a cancellation fee which is charged directly from the airline to Air
Kingdom. This penalty is charged to the company who has cancelled the ticket and this fee will be reflected when sending the invoices which are generated through the system. Functional Requirement 26: Ticket Postponement
Similarly, companies request for an airline ticket to be postponed due to some reason.
This action requires a small postponement fee to be paid as well. Hence, this function will be used when postponing a ticket and similarly the penalty fee will be reflected in the invoice generated through the system.

2.1.7 Customer Registration Management System
Functional Requirement 27: Add New Customer

Whenever a new customer wants to go on a local tour, his/her information needs to be stored in the system. Only after they are added to the system can they be allocated for a booking. Therefor this is an important function. Also, personal information of customers can be vital because, it can speed up the process of booking if they happen to return for another tour.

Functional Requirement 28: Update Customer Details
In situations where a returning customer has changed his residence, this function will let the user update his/her address or contact details or whatever is required to be changed. Therefore, we can be sure that the details are up-to-date and correct.

Functional Requirement 29: Customer History Report
This can be a useful reporting function, even though not used very frequently. If a situation arises, we can use this function to select a customer and view the history of tours he has visited. This can be vital information when considered from a security point of view.