The document discusses the development of an electronic booking system for an airport shuttle company called Aerolink. Key points include: - The system needs to allow for remote booking through computers, tablets, and phones. - The current website uses Flash which doesn't work on Apple devices and needs a redesign. - Developers have created databases in phpMyAdmin and are hosting them remotely. - They chose a content management system so clients can modify content without a developer. - Integration of the booking system with the website proved challenging initially but issues were resolved.

1. Aerolink Booking System
Salar Wadi
Matt Stannett
Brandon Hutcheson
Leon Oud

2.  Web based booking system
 Can it work remotely
 It should be able to be accessed by computer,
tablet and phone.
 This would mean they could have reservation
agents working from their own homes.

3.  Aerolink: Airport shuttle company operating
from Hamilton to both the Auckland and
Hamilton Airports.
 The business is currently very low tech, no
electronic booking system (paper based
diary).

5.  Current website is amateurish
and contains a lot of Flash
 Doesn’t work on Apple products

6. A total website re-design
Professional
Mobile/tablet friendly
Developing an electronic booking system

12.  So far we have achieved the backend of the
databases being created in phpMyAdmin, this
is all hosted remotely on our server.
 We choose to use a content management
system so that the client will be able to
modify the content on their site without the
need of a web developer.

14. WP pages are dynamically generated by PHP
-> Can’t get to raw code or files on the server
Plugins for PHP etc have little in the way of
documentation or guides
PHP-Website integration works putting data
into the server but not pulling data from the
server. -- FIXED

15. WP plugs for PHP and database integration
-> Little documentation or success
HTML only page made in notepad hosted on
WP server to run PHP pulling from DB.
-> Didn’t work –FIXED
Now we are in the process of moving all files to
strictly HTML, CSS, PHP, JS rather than the WP-
mash up and hosting on a different server as a
contingency plan in-case we can’t get full DB
integration working. --FIXED

16. On WordPress (able to edit):
Home, About Us, Transfer Types, Airports,
Book online, Testimonials, Contact Us,
Payment gateway
Plain HMTL/PHP (unable to edit):
Admin area [anything that interacts with
DB]
Admin area demo

18. http://202.27.219.40/~brandon/wordpress/