Final Report

Airline Reservation System DCS 5095

Acknowledgement

First and foremost, we would like to thank to our supervisor of this project, Miss

Shyamala for the valuable guidance and advice. She inspired us greatly to work in

this project. Her willingness to motivate us contributed tremendously to our project.

We also would like to thank her for showing us some example that related to the

topic of our project.

Besides, we would like to thank the authority of Multimedia University (MMU) for

providing us with a good environment and facilities to complete this project. Also,

we would like to take this opportunity to thank to the Centre of Affiliated Diploma

Programme (CADP) of Multimedia University (MMU) for offering this subject,

Computing Project. It gave us an opportunity to participate and learn about the

operation of flights ticket reservation. In addition, we would also like to thank

Malaysia Airline System (MAS) which provide us valuable information as the

guidance of our project.

Finally, an honorable mention goes to our families and friends for their

understandings and supports on us in completing this project. Without helps of the

particular that mentioned above, we would face many difficulties while doing this

project.

Centre of Affiliated Diploma Programme Page 1


Table of Contents

ACKNOWLEDGEMENT....................................................................................................................1 TABLE OF CONTENTS......................................................................................................................2 LIST OF TABLES ................................................................................................................................4 LIST OF FIGURES ..............................................................................................................................4 MANAGEMENT SUMMARY ............................................................................................................5 PART 1: INTRODUCTION.................................................................................................................7

1.1 Overview.........................................................................................................................8 1.2 Project Objectives ...........................................................................................................9 1.3 Project Goals .................................................................................................................10 1.4 Project Scope.................................................................................................................11 1.5 Gantt Chart I..................................................................................................................12 1.6 Project Milestones I.......................................................................................................15 1.7 Gantt Chart II ................................................................................................................16 1.8 Project Milestones II .....................................................................................................19 1.9 Team Organization........................................................................................................20 1.10 Project Standards and Procedures .................................................................................21 1.11 Documentation Format..................................................................................................26

PART 2: CASE STUDY AND LITERATURE REVIEW...............................................................27

2.1 Primary Study................................................................................................................28 2.2 Why ARS is Needed .....................................................................................................29 2.3 Existing Systems ...........................................................................................................31 2.4 ARS Concept and Features ...........................................................................................34 2.5 Software and Tool Involved..........................................................................................36

PART 3: SOLUTION .........................................................................................................................37

3.1 Problem Statement ........................................................................................................38 3.2 System Requirement .....................................................................................................39 3.3 Entity Relationship Diagram.........................................................................................40 3.4 Data Dictionary .............................................................................................................41 3.5 Relationship Diagram....................................................................................................44 3.6 Data Flow Diagram.......................................................................................................45

PART 4: SYSTEM PREVIEWS........................................................................................................47

4.1 View of Screen Design..................................................................................................48 4.2 System Screen Shots and Explanations.........................................................................50

4.2.1 Splash Screen ...........................................................................................................50 4.2.2 Staff Login Screen....................................................................................................51 4.2.3 Manager Login Screen .............................................................................................52 4.2.4 Main Screen for Airline Manager.............................................................................53 4.2.5 Main Screen for Ticketing Staff ...............................................................................54 4.2.6 New Airline Manager Information Screen ...............................................................55 4.2.7 New Ticketing Staff Information Screen..................................................................56 4.2.8 New Flight Information Screen ................................................................................57 4.2.9 Make Reservation Screen .........................................................................................58 4.2.10 New Passenger Information Screen.....................................................................59 4.2.11 Cancel Reservation ..............................................................................................60



4.2.12 Query of Airline Manager Information Screen....................................................61 4.2.13 Query of Ticketing Staff Information ..................................................................62 4.2.14 Query of Flight Information Screen.....................................................................63 4.2.15 Query of Passenger Information Screen ..............................................................64 4.2.16 About Screen .......................................................................................................65 4.2.17 Sample Reports....................................................................................................66

PART 5: SYSTEM TESTING ...........................................................................................................67

5.1 Test Plan........................................................................................................................68 5.2 System Testing ..............................................................................................................70

PART 6: DEVELOPER’S PROGRESS WORK..............................................................................72

6.1 Contribution of Lee Heng Leng ....................................................................................73 6.2 Contribution of Agnes Khoo Boon Yan........................................................................75 6.3 Contribution of Teh Pei Yee .........................................................................................77 6.4 Contribution of Kimberly Lo Sze Yie...........................................................................79 6.5 Developer’s Weekly Log ..............................................................................................81

PART 7: CONCLUSION ...................................................................................................................85

7.1 Conclusion ....................................................................................................................86 7.2 System Limitations........................................................................................................88 7.3 Further Enhancements...................................................................................................90

PART 8: BIBLIOGRAPHY...............................................................................................................91 PART 9: APPENDIXES.....................................................................................................................93

Appendix A: Minutes of Meeting................................................................................................94 Appendix B: Request Interview Letter ......................................................................................106 Appendix C: Interview Questions .............................................................................................108 Appendix D: Interview Session.................................................................................................111 Appendix E: Test Script ............................................................................................................118 Appendix F: Client/Server Setup Guide ....................................................................................125



List of Tables

TABLE 1.1: PROJECT MILESTONES I.............................................................................................15 TABLE 1.2: PROJECT MILESTONES II ...........................................................................................19 TABLE 1.3: DOCUMENTATION FORMAT .....................................................................................26 TABLE 3.1: DATA DICTIONARY.....................................................................................................43 TABLE 5.1: TEST PLAN.....................................................................................................................69 TABLE 6.1: LEE HENG LENG’S WEEKLY LOG ............................................................................81 TABLE 6.2: AGNES KHOO’S WEEKLY LOG .................................................................................82 TABLE 6.3: TEH PEI YEE’S WEEKLY LOG....................................................................................83 TABLE 6.4: KIMBERLY LO’S WEEKLY LOG ................................................................................84

List of Figures

FIGURE 1.1: GANTT CHART I..........................................................................................................14FIGURE 1.2: GANTT CHART II ........................................................................................................18 FIGURE 1.3: TEAM ORGANIZATION..............................................................................................20 FIGURE 3.1 ENTITY RELATIONSHIP DIAGRAM .........................................................................40 FIGURE 3.2 RELATIONSHIP DIAGRAM.........................................................................................44 FIGURE 3.3 CONTEXT DIAGRAM...................................................................................................45 FIGURE 3.4 DFD – LEVEL 0 DIAGRAM..........................................................................................46 FIGURE 4.1: VIEW OF SCREEN DESIGN FOR AIRLINE MANAGER .........................................48 FIGURE 4.2: VIEW OF SCREEN DESIGN FOR TICKETING STAFF ............................................49 FIGURE 4.3: SPLASH SCREEN.........................................................................................................50 FIGURE 4.4: LOGIN SCREEN ...........................................................................................................51 FIGURE 4.5: MANAGER LOGIN.......................................................................................................52 FIGURE 4.6: MAIN SCREEN FOR AIRLINE MANAGER...............................................................53 FIGURE 4.7: MAIN SCREEN FOR TICKETING STAFF .................................................................54 FIGURE 4.8: NEW AIRLINE MANAGER INFORMATION SCREEN ............................................55 FIGURE 4.9: NEW TICKETING STAFF INFORMATION ...............................................................56 FIGURE 4.10: NEW FLIGHT INFORMATION SCREEN.................................................................57 FIGURE 4.11: MAKE RESERVATION SCREEN..............................................................................58 FIGURE 4.12: NEW PASSENGER INFORMATION.........................................................................59 FIGURE 4.13: CANCEL RESERVATION SCREEN .........................................................................60 FIGURE 4.14: QUERY AIRLINE MANAGER INFORMATION SCREEN .....................................61 FIGURE 4.15: QUERY OF TICKETING STAFF INFORMATION ..................................................62 FIGURE 4.16: QUERY OF FLIGHT INFORMATION SCREEN ......................................................63 FIGURE 4.17: QUERY OF PASSENGER INFORMATION SCREEN..............................................64 FIGURE 4.18: ABOUT SCREEN ........................................................................................................65 FIGURE 9.1: CLIENT/SERVER CONNECTION.............................................................................125



Management Summary

Airline Reservation System (ARS) is specifically develop to help an airline to

manage the reservations of the flight tickets. It has user-friendly menu driven

environment to ease the use of the system. It enables productive and effective flight

reservation. Passengers make flight reservations through ticketing staff, who can

access a centralized system to check on flight details. The system able to create

flights, delete flights and reserve seats for passengers according to their requested

destination, date and time. It can also generate printed report on flight, passenger,

airline manager and ticketing staff.

The project is developed in the final trimester of our Diploma Information

Technology program. We divided this trimester into two where the first half session

of the trimester would be used to do the interim report such as initiation, planning

and the prototype of the system. During this session, we also defined the objectives

of our project, goals, scopes and problem statements so that we can complete the

project easily referring to it. Gantt chart and milestones were also specified to guide

our schedule to keep track of time we used in developing the system. Besides, we

also have done some researches on the airline reservation system and its websites

namely http://www.mas.com.my, http://www.airasia.com, and etc. We have

conducted a visit to Malaysia Airline (MAS) for the background studies about airline

reservation system. The existing airline reservation system is a non-graphical user

interface system.



The system that we developed is using Microsoft Visual Basic 6.0 and the database

storage is managed by Microsoft SQL Server 2000. This system requires a minimum

of Pentium III 500 MHz or compatible, 128 MBRAM (minimum) / 256 MBRAM

(recommended) and 800 MB of hard disk space. Software required includes,

Windows Operating System either 98/2000/XP for the client side, Microsoft 2000

Server for server side, Microsoft Visual Basic 6.0 and Microsoft SQL Server 2000.

On the second half of our trimester, we have to complete the final report, implement

and test on the system. We do some reviews on the system’s prototype and then

make changes to enhance the system. Then, the system is connected to the airline

reservation database. Team leader is monitoring overall project and divided tasks for

all members. Programming leader in charged of programming activities such as

writing coding to perform specific functions. Database manager managed the

database and did all data entries. While the document manager, is handling all

documentation for final report. After completing the system, test was conducted to

ensure no errors and bugs occurred. The system limitation is also defined for

maintenance and further enhancement in future.

At the end of trimester, the project was successfully developed. Though we faced

problems during the development of project, but we able to find solution and finished

the project before due date and as planned in the Gantt chart.



Part 1: Introduction



1.1 Overview

The purpose of the Airline Reservation System Project is to build an application

program, which an airline could use to manage the reservation of airline tickets.

Passengers make flight reservations through the ticketing staff of the airline, who can

access a centralized system to check on flight details. The system able to create

flights, delete flights and reserve seats for passengers according to their requested

destination, day and time.

The system interfaces to the ticketing staff and the airline manager. The staff

accesses flight data for passenger to consider a trip, and make reservations according

to passengers’ preferences. It searches all flights with a given origin and destination

airport. For each flight found, the system displays the flight number, arrival and

departure time and the seat capacity. The reservation is according to customer desire.

Reservation must be done within specific time that set by the airline before the flight.

The airline manager is responsible to maintain the flight schedule. He has the

authority to change the fare for a flight, departure, arrival date and time. He is also

able to schedule new flights and drop the flight from schedule. Airline manager has

the authority to insert new user or ticketing staff for the system.



1.2 Project Objectives

There are several main objectives for this project:

• To improve efficiency of flight reservations and ticket sales.

• To improve the processing of reservations and purchases.

• To provide up-to-date information for enquiries.

• To gain trust from passengers by improving customer services.

• To gain more loyal passengers by providing promising results.

• To help airline make more profit by having more returning passengers.

• To make the airline more competitive and up-to-date with other airlines.

• To reduce cost of the airline by decreasing counter of selling tickets.

• To report on flight status and sales performance.



1.3 Project Goals

The primary goal of this project is to help the passengers make flight reservation.

The system will be able to find all the flights fulfilling a passenger’s needs. It is also

capable to search all flights with a given origin and destination. The system

displayed the arrival and departure times, the price, and the flight number for each

flight it finds. Then, the passenger will decide the flight reservation based on the

displayed information.

The secondary goal is to provide a means for the airline manager to manage the

flights. The airline manager will be able to schedule new flights, drop flights from

the schedule and change the fare for a flight. Manager will also have clearer and

better view about the flight schedule. The manager can decide to add flights if there

are high demand of reservation at a certain time (e.g.: festive season). This system is

capable to increase the sales performance by providing daily/weekly/monthly sales

report.



1.4 Project Scope

This system worked in administration and ticket reservation department in an airline.

In ticket reservation department, the staff will use this system to help passenger for

daily ticket reservation. To reserve a flight seat, the ticketing officer helps passenger

seek for flights according to the passenger’s desire location, departure time and

arrival time. After the flight confirmation is done, ticketing staff will ask for

passenger information to make the flight reservation. The passengers will then

received a printed reservation coupon and then make their payment in the sales

counter. In administration department, the manager can use this system to generate

real time report according to the request of the manager. The report is viewable by

manager level only. The administration department’s manager can do modification

on flights, cancellation and addition of flights.

This project will be divided into five main modules according to its features so that it

would be easy for task separation and systematic development procedures. The

modules are Flight, Reservation, Airline Manager, Ticketing Staff and Passenger.

The features and documentation will be within the bound of these modules

mentioned which provides the clear scope of this project.



1.5 Gantt Chart I

The first session of our project is to develop the system’s prototype and interim

report. We divided the first session of tasks into six different parts from project

identification until presentation. The first task is Project Identification and Selection,

which starts on 18th of December 2003, four of us, had discussed on few topics and

we finally decided to work on Airline Reservation System.

The first task, Project Identification and Selection is expected to spend two days to

complete. The following task is Project Initiation and Planning, we start to develop

project plan and it includes the Gantt chart, Team Organization, and Introduction to

our project. Then, our next task is to work on Literature Review. We search for

existing reference for the system and project. Besides, we will also conduct a

research on proper tools that we should use to construct a system for Airline

Reservation System. This task is expected to finish in a week or twelve days. We will

make a visit to Malaysia Airline office, situated at Kuala Lumpur.

On 3rd January 2004, we planned to start a crucial task which is Analysis and

Design. At first, we have to analyze the requirements for this project and then we

starts to design Entity Relational Diagram and Data Flow Diagram. It will consume

most of the time in this task followed by drawing context diagram. The Analysis and

Design is expected to finish on 12th of January 2004. The final task before

presentation is developing Prototype and Report, a prototype will be developed and it



will consume most of the time while finalizing report will be the minor part in this

task. From 3rd of February 2004, we will finalize all the tasks we have done and

prepare for the presentation and it should be completed in not more than two weeks.



Figure 1.1: Gantt Chart I



1.6 Project Milestones I

In the milestones table, it is mainly divided into two major phases, which the first phase

complete by 6th February 2004 while the second phases is expected to be completed by

16th of March 2004 including the Presentation II. In first phases, it will be sub-divided

into six tasks and the completion date for each task is stated as the table below.

No.

Tasks

Milestone/Date complete

1 Project Identification and Selection

19th December 2003

2 Project Initiation and Planning

3rd January 2004

3 Literature Review

13th January 2004

4 Analysis and Design

12th January 2004

5 Prototype and Report

15th January 2004

6 Presentation 1 6th February 2004

Table 1.1: Project Milestones I



1.7 Gantt Chart II

The second session of this project starts after the submission of interim report and

prototype. We will start to prepare the final report. We divided our tasks mainly on

seven different parts from Review on Preview Project Work until Presentation.

The first task that we need to do is Review on Preview Project Work which starts on 2nd

of February 2004, all group members will carefully construct a full Review on Preview

Project Work. We will analyze what problems are to be solved and what improvement to

be made and design a new project plan. The first task will be expected to spend eight

days to complete.

The following task is Update Plan and Requirements. After completing the review

session, we will have the final update for our plan and project requirement. This plan

will 100% meet our target in development a successful Database CASE tool. This task

will expect to spend five days to complete.

Then, our next task is System Design which is Database and Software Architecture. We

will construct a database to the system. For the purpose of enhancement; we will design

on screen and repair the data model. This task is expected to finish in eight days.



The next task is Prototype & Review of major Modules. We will continue to work on the

prototype which we have done during the interim report week. Before starting the initial

system coding, we will carefully formulate a review of major modules. It expected to

finish on 2nd of March 2004.

After the implementation phase, we will go through the testing phase by constructing a

Test Plan and Test Data. We will create an acceptance test and begin system debugging

if problem occurs. This Test Plan and Test Data are expected to finish on 7th of March

2004.

The following task is Final Report and Testing Evaluation. In this testing phase, we will

continue on our final report, system testing and system evaluation. We will concentrate

on the Final Report as well as System Completion towards the end of project

development. We need to prepare a well written and high-quality final report.

The final task is the presentation of the project. A good preparation on this presentation

phase will insure a grade that fairly represents the project work that we have done. Thus,

we will focus on the preparation in order to manage a well organized and polished

presentation.



Figure 1.2: Gantt Chart II



1.8 Project Milestones II

The second phase of milestones is as shown as below. The completion date of project is

on the date of 16th March 2004. This second phase is sub-divided into seven tasks and

the completion date for each task is as shown.

No.

Tasks

Milestone/Date complete

1. Review on Preview Project Work

10th February 2004

2. Update Plan and Requirements

14th February 2004

3. System Design (Database & Software Architecture)

23rd February 2004

4. Prototype & Review of major Modules

2nd March 2004

5. Test Plan and Test Data

7th March 2004

6. Final Report & Test Evaluation 11th March 2004

7. Presentation 2 27th March 2004

Table 1.2: Project Milestones II



1.9 Team Organization

To develop the Final Year Project, we have formed a team with four members where

each of us is going to spread the tasks in order to do the project in a systematic way. The

Four positions for the completion of this project are Team Leader, Programming Leader,

Database Manager and Document Manager.

After discussion, the position assignments are as below:

Team Leader – Miss Lee Heng Leng

Programming Leader – Miss Agnes Khoo Boon Yan

Database Manager – Miss Teh Pei Yee

Document Manager – Miss Kimberly Lo Sze Yie

Figure 1.3: Team Organization



1.10 Project Standards and Procedures

To complete a quality group project, all group members should cooperate and enjoy

working in a team. One should contribute his or her knowledge and skills to the project.

All members are responsible in attending every meeting. The meetings were held

formally and the Database Manager takes the minutes.

As our team members have been assigned individual position to complete the Final Year

Project, each of us has specific jobs/tasks that need to take care during the

implementation of the project.

Team Leader – Miss Lee Heng Leng

The Team Leader of our team Miss Lee Heng Leng. She is responsible for all the

activities that are going to take and involve complete the development of Airline

Reservation System.

• Responsibilities for Miss Lee Heng Leng as a Team Leader are:

• Responsible to communicate with Lecturer for project information.

• Responsible for the meeting time of that available for group members to discuss

and develop project.



• Special rights in making final decisions if the team is unable to reach a decision.

• Encourage members to create and feel creative when they work with the

program.

• Encourage members to produce to their best ability.

• Manage and Coordinate the Project Activities.

• Submitting project reports on time.

• Research in the project areas.

• Assign appropriate tasks to members according to their responsibilities and

ability.

• Brainstorming of new ideas

• Final compilation of interim report.

• Prepare a software development schedule for team members to follow.

• Assign programming tasks to team members and assist them if they face any

programming problem during software development.

• Design ER Diagram, Data Flow Diagram and Context Diagram during design

phase.

• Guide group members in programming-related tasks and Database related tasks.

• Ensure the program adhere to design specification.

• In charge in Concept Design.



Programming Leader – Miss Agnes Khoo Boon Yan

The Programming Leader of our team is Miss Agnes Khoo Boon Yan. As a

Programming Leader, she is responsible conducting the programming activities.

• Responsibilities for Miss Agnes Khoo Boon Yan as a Programming Leader are:

• Responsible for conducting the programming activities.

• Plan, coordinate and control the software development tasks.

• Explore and develop skills to use programming tools.

• Guide group members in programming-related tasks.

• In charge of Concept Design.

• Prepare the proposed solution part including software architecture, system

architecture, class specifications of interim report.

• Approval of any updating/changing of the program.

• keep master copy of the software.

• Select appropriate programming language used to develop the program.

• Frequently check the master copy of document to ensure any updating of the

program are updated in the documentation as well

• Combine the program at the last phase of software development



Database Manager – Miss Teh Pei Yee

The Database Manager of our team is Miss Teh Pei Yee. She is responsible for data

collection activities that are going to take during the development of Airline Reservation

System.

• Responsibilities for Miss Teh Pei Yee as a Database Manager are:

• Responsible to record minute of meeting.

• Responsible for project standards and Procedures.

• Responsible for the project schedule of Gantt chart.

• Identify documentation standards and ensure that documents are ready in time

and in precise manner by following the schedule of Gantt chart.

• Data collection.

• Functional requirement and analysis.

• Database design and maintenance.

• Responsible to Implementation plan.



Document Manager – Miss Kimberly Lo Sze Yie

The Document Manager of our team is Miss Kimberly Lo Sze Yie. She is responsible

for all the documentation activities that are going to take during the development of the

Airline Reservation System.

• Responsibilities for Miss Kimberly Lo Sze Yie as a Document Manager are:

• Responsible for documentation activities including hardcopy and softcopy.

• Plan the document preparation tasks.

• Documentation backup.

• Final checking of all documents

• Save ‘master copy’ of all project documents

• Prepare introduction, objective, conclusion of interim report.

• Coordinate report preparation tasks.

• Final compilation of interim report

• Distributed and assigned parts of the documents belong to each member

according to their position and responsibilities

• Collect and combine documents from members which has completed

• Summarize and finalize the overall documentation of project to all group

members.



1.11 Documentation Format

The table below shows the standardized formatting for pages throughout this report:

Subject Types

Chapter Heading Fonts Times New Roman, Size 26, Bold

Sub-Chapter Heading Fonts Times New Roman, Size 16, Bold

Sub of Sub-Chapter Heading Fonts Times New Roman, Size 12, Bold

Figures / tables caption Times New Roman, Size 10, Bold

Header and Footer Times New Roman, Size 10

Paragraph Fonts Times New Roman, Size 12

Paragraph Spacing Double Spacing

Header and Footer Margin from edge 25mm

Top Margin 40mm

Left Margin 40mm

Right Margin 25mm

Bottom Margin 25mm

Table 1.3: Documentation Format



Part 2: Case Study and Literature

Review



2.1 Primary Study

Airline Reservation System (ARS) is developed to help an airline make reservations for

passenger. Its must capable to load and maintain the schedule of flights run by the

airline. For each flight, the system maintains the information on origin and destination

airports, the arrival and departure times, aircraft type (with its seat capacity), the fare,

the flight number, and the flight date.

Besides, the system loads and maintains the seats reserved for every given date of the

flight, and the list of passenger reservations. The system interfaces with the ticketing

officers and the airline managers. The ticketing officer accesses flight data for the

passengers considering a trip, and make reservations according to passengers'

preferences.

Implementation of ARS will definitely brings lots of benefits for the airlines. The system

also eases the sales of ticket and increases its revenue.



2.2 Why ARS is Needed

With Airline Reservation System implemented, the airlines may be subjected to many

benefits, the benefits are as listed below: -

• Increase in Sales of Tickets

With Airline Reservation System, we can track our passengers purchasing preferences

and with this we can promote special flight packages to our existing passengers.

Passengers’ reservations patterns can also be used to determine the marketable flight and

then try to provide more flights and services to fulfill the high demand. Besides, ARS is

also capable in increasing passenger loyalty and satisfaction by providing good

reservation and services.

• Reduce in Time and Cost

Traditional paper reservation records have many drawbacks: they can be incomplete,

torn, worn, misplaced, or lost. They also require a lot of storage space in addition to

requiring extensive administrative time from user. With the implementation of ARS, it

will prevent data lost with back-up function and decrease in cost and time. It can

increase the speed of searching, processing and making reservation. Thus, it gives

satisfactory to passengers. From the data stored in the system, it is capable to generate



daily/monthly sales report automatically. Users do not have to waste their time to

generate the report manually.

• More Organized Information

Flight ticket reservation method has better organization of information for better

retrieval with ARS. All other relevant data can be managed and well-organized using the

system. Data will be stored in the database accordingly. Thus, user can make a clear

view on any data as they wish without any problem.



2.3 Existing Systems

We managed to do a research on the existing automated ARS used in Malaysia Airlines.

The airlines reservation system used in Malaysia Airlines is known as KOMMAS.

KOMMAS is a DOS-base system that use by MAS for ticket reservation. This system

has 25 years history. It had been upgrade for 4 times in these 25 years to add more

features in it. Now, they still are using this system to do reservation for customers. All

brunch of MAS in overseas are using the same system to do reservation too. The system

can check on the departure time and day to specific place. Not only flights that offer by

MAS but also flights offered by other airline systems in Malaysia and overseas.

For reservation, the reservation person will key in the record and book the tickets. Once

booked, the system will check whether the flights or seats is confirm. This system has

link to the capacity of the aircraft. For example, this system tells the number of seats

occupied and empty seats for each class. If the seats had full, a note will pop up say that

seats are full and confirm can not be made. By this function, the reservation person can

tells the more accurately about which seats are available to customers.

The reservation person will then confirm with customers. Once confirm, the customers

will go to the ticketing counter to take the ticket and pay the money. The reservation



person will key in the reference number to the system. The information of customers

will pop up if he had made the reservation.

The deadline for customers to take the tickets is 2 weeks before departure time. If the

customers didn’t take the ticket and pay the money before these two weeks, the system

will automatically erase the reservation. This is to enable others to do reservation. There

is no deposit required in this process. For customers that want to change their flights

departure time or date, the reservation person just need to key in the customer’s

reference number and change the details. Customers also can cancel the flights if they

couldn’t make it. The information of customers will keep by the system for 6 months.

After 6 months, the system will automatically delete the passenger information.

This system also allows customers to make some special requirement. For example,

some people may have elegy to certain food, the reservation person will key in this

special requirement for food into the system, so that special meal will be provided to this

person. Customers also can choose seat that they prefer. In the other words, this system

is customers friendly. Booking is done by reservation department. But ticketing

department also can access it and make reservation for customers. Ticketing and

reservation department are link to each other, they can access the same database.

KOMMAS have a specific code for the user of this system. For persons who make

reservation and ticketing, they have the highest accessibility to use the system. For

managing level, they just can access the system and check the report of flights and



customer’s reservation information. For administration level of this system, they can

customize the flights and departure time.

System down was happened before. When the system is down, all the ticketing

reservation will do manually. The system also has backup the information of all flights

and customers’ information. This is to prevent the damage of database due to virus or

physical damage. So, there is no reason that they will lose their data.

However, this system has its weaknesses. It can not generate report according to the

requirement of user. Also, this system has no basic intelligent. User will only get the

report after one or two weeks. Due to this system is DOS base, the interface of this

system may not attractive. Also, it is not user friendly enough for the user. User will

need to memorize all the codes to make reservation, to view reports, to check on flight

and etc. Information that shown out from the system is messy. For the beginner user of

this system, they will face the difficulties to understand the information shown. For the

security part, user do not have own password to get into the system. They get into the

system just by using the access code that they had given.



2.4 ARS Concept and Features

Our Airline Reservation System provides slightly similar features compared to

KOMMAS. However, ARS has user friendly menu-driven environment. Below are the

lists of features in our system:-

• Add/Delete Airline Manager Information

• Add/ Delete Ticketing Staff Information

• Add/ Delete Flight Information

• Add/Delete Passenger Information

• Make Reservation

• View/Query/Cancel Reservation

• View/Query on Flight Information

• View/Query on Passenger Information

• View/Query on Airline Manager Information

• View/Query on Ticketing Staff Information

• Report on Flight, Passenger, Airline Manager and Ticketing Staff



Basically, our Airline Reservation System is divided into five main modules. The first

module is Airline Manager. This module mainly stores the profile of airline manager and

their access control. The second module is Ticketing Staff which used to store the

profiles of ticketing staff and keeps track of their authorization control.

The third module is Reservation. In this module, all reservation can be made or cancel.

From this module, all reservations that have been confirmed and reservation slip can be

printed for passenger to collect their ticket at ticket sales department. This module is also

connecting to another module called Passenger. In this module, passenger personal

details and reservation history will be stored in database.

The last module is Flight. This module is access by the airline manager to manage all

flight. It keeps information such as departure, arrival and aircraft type for all flights.

Passenger refers to the flight schedule to make reservation according to their

preferences.



2.5 Software and Tool Involved

To develop our Airline Reservation System (ARS), we have decided to use the

following software:-

• Microsoft Visual Basic 6.0

Microsoft Visual Basic 6.0 is chosen because the ease of using it to design the interface

for our system. Visual Basic is user friendly as it is a Graphic User Interface style. The

end user will find it easy to use the system with a friendly interface.

• Microsoft SQL Server 2000

Microsoft SQL Server 2000 is a strong backbone database system to manage all the

inserted data. It has tables of collection data about a specific topic, such as flight or

passenger. Besides, SQL Server 2000 is also used to manipulate the query to find and

retrieve data based on our SQL statements. Using stored procedure will also enhance the

speed of processing the SQL statements thus increasing the for the function request of

the ARS.



Part 3: Solution



3.1 Problem Statement

Airline Reservation System (ARS) did for the passengers reserve the flight meeting their

needs and preferences. Without sufficient airline reservation system, some problems

may encounter, such as passengers will have problems with planning a trip. Without a

confirmed flight ticket, a passenger can only assumed that they might get the ticket of

the time they desire but problems will arise if the ticket is not available.

Besides, it is also a waste of time and resources without a proper airline reservation

system. Passengers have to go to the airport to buy a ticket and it may waste their time to

travel to the airport. When they reach the airport, they might not get the ticket that they

want. It is also inconvenient for the passengers to go to the airport personally a few days

earlier to buy the tickets, which will double the cost of transportation. Passengers might

take other type of transportation since it does not promise a ticket.

Carelessness of human is also a factor of problem statement. With the existing system,

information given will be accurate and it is computerized without any errors. Unlike the

old days where we have to manually look for empty time slots.



3.2 System Requirement

Hardware Requirement

• Pentium III 500 MHz or compatible

• 128 MBRAM (minimum) / 256 MBRAM (recommended)

• 800 MB hard disk space

• Screen resolution 1024 by 768 pixels

Software Requirement

• Windows Operating System either NT/2000 Server (Server side)

• Windows Operating System either 98/2000/XP (Client side)

• Microsoft SQL Server 2000

• Microsoft Visual Basic 6.0



3.3 Entity Relationship Diagram

The Entity Relationship Diagram below is to show the relationship between different

data in the airline reservation system, and how data from different objects relate to each

other.

Figure 3.1 Entity Relationship Diagram



3.4 Data Dictionary

Following this is the data dictionary, which describes all the attributes and tables used in the software:

Table Name

Attribute Name

Content

Type

Format

Required

PK or FK

FK Reference

Table AIRLINE_MANAGER A_Code Manager Code integer ### Yes PK A_Login Manager login name varchar(10) xxxxx A_Password Manager login password varchar(10) xxxxx A_PassConfirm Manager password confirmation varchar(10) xxxxx A_Name Manager name varchar(50) xxxxx A_IC Manager identication number integer ### A_Gender Manager gender varchar(10) xxxxx A_Birthday Manager birth date date mm/dd/yyyy A_Phone Manager phone number varchar(20) xxxxx A_Mobile Manager mobile number varchar(20) xxxxx A_Email Manager email varchar(50) xxxxx A_Address Manager address varchar(50) xxxxx A_PostalCode Manager postal code varchar(10) xxxxx A_State Manager state varchar(20) xxxxx TICKETING_STAFF S_Code Staff code integer ### Yes PK S_Login Staff login name varchar(10) xxxxx S_Password Staff login password varchar(10) xxxxx S_PassConfirm Staff password confirmation varchar(10) xxxxx S_Name Staff name varchar(50) xxxxx S_IC Staff identication number integer ###



S_Gender Staff gender varchar(10) xxxxx S_Birthday Staff birth date date mm/dd/yyyy S_Phone Staff phone number varchar(20) xxxxx S_Mobile Staff mobile number varchar(20) xxxxx S_Email Staff email varchar(50) xxxxx S_Address Staff address varchar(50) xxxxx S_PostalCode Staff postal code varchar(10) xxxxx S_State Staff state varchar(20) xxxxx FLIGHT F_Code Flight code integer ### Yes PK F_Number Flight number varchar(10) xxxxx F_Aircraft Flight aircraft type varchar(30) xxxxx F_DepartLoc Flight departure location varchar(50) xxxxx F_DepartDate Flight departure date date mm/dd/yyyy F_DepartTime Flight departure time time hh:mm F_ArriveLoc Flight arrival location varchar(50) xxxxx F_ArrriveDate Flight arrival date date mm/dd/yyyy F_ArriveTime Flight arrival time time hh:mm A_Code Manager Code integer ### Yes FK AIRLINE_M

ANAGER PASSENGER P_Code Passenger code integer ### Yes PK P_Name Passenger name varchar(50) xxxxx P_Birthday Passenger date of birth date mm/dd/yyyy P_Gender Passenger gender varchar(10) xxxxx P_IC Passenger identification code integer ### P_Passport Passenger passport number varchar(20) xxxxx P_Email Passenger e-mail varchar(50) xxxxx P_Haddress Passenger home address varchar(50) xxxxx P_HPostal Passenger home postal code varchar(10) xxxxx P_HState Passenger home state varchar(20) xxxxx P_HPhone Passenger home phone varchar(20) xxxxx P_Mobile Passenger home mobile varchar(20) xxxxx



P_Company Passenger company varchar(30) xxxxx P_Job Passenger job title varchar(30) xxxxx P_Dept Passenger department varchar(30) xxxxx P_Office Passenger office varchar(20) xxxxx P_BAddress Passenger business address varchar(50) xxxxx P_BPostal Passenger business postal code varchar(20) xxxxx P_BState Passenger business state varchar(20) xxxxx P_BPhone Passenger business phone varchar(20) xxxxx P_Fax Passenger fax number varchar(20) xxxxx S_Code Staff code integer ### Yes FK TICKETING

_STAFF RESERVATION R_Code Reservation code integer ### Yes PK R_Quantity Reservation quantity integer ### S_Code Staff code integer ### Yes FK TICKETING

_STAFF P_Code Passenger code integer ### Yes FK PASSENGE

R F_Code Flight code integer ### Yes FK FLIGHT

Table 3.1: Data Dictionary



3.5 Relationship Diagram

Following diagram is the relationship diagram, which describes relationships between all

tables used in the software:

Figure 3.2 Relationship Diagram



3.6 Data Flow Diagram

Context Diagram below showed data flows between a generalized airline reservation

system within the domain and the other entities and abstractions with which it

communicates.

Figure 3.3 Context Diagram



Data Flow Diagram – Level 0 Diagram

Level 0 Diagram below is an intuitive way of showing how data is processed in the

system.

Figure 3.4 DFD – Level 0 Diagram



Part 4: System Previews



4.1 View of Screen Design

Airline Manger is allowed to full access of the system as shown as figure below.

Figure 4.1: View of Screen Design for Airline Manager



Ticketing Staff is only allowed to access to certain features of the system as shown as

figure below.

Staff Login

Reservation Query Windows

Main Menu

MakeReservation

CancelReservation

Ticketing StaffInformation

Tile Horizontally

Cascade

Tile Vertically

About

PassengerInformation

ReservationReport

Figure 4.2: View of Screen Design for Ticketing Staff



4.2 System Screen Shots and Explanations

4.2.1 Splash Screen

Figure 4.3: Splash Screen

This screen appears once you enter to the program. It shows the progress of the program

loading. Once the program finished loading, user can login into the system.



4.2.2 Staff Login Screen

Figure 4.4: Login Screen

This is the Login Screen is for ticketing staff to enter their login name and password to

authenticate their access to airline reservation system. Then, click OK to access into the

system. For airline manager to access into the system, manager will need to click on

“Manager Login”



4.2.3 Manager Login Screen

Figure 4.5: Manager Login

This is the Login Screen is for airline manger to enter their login name and password to

authenticate their access to airline reservation system. Then, click OK to access into the

system.



4.2.4 Main Screen for Airline Manager

Figure 4.6: Main Screen for Airline Manager

This is the main screen of Airline Reservation System (ARS) for airline manager. The

Menu Bar listed the features of the system. The features include New, Reservation,

Query, Report and Windows. Each of the features contain its’ sub features. There are

shortcuts for airline manager on the left hand side which allows manager quick access to

add and view flight



4.2.5 Main Screen for Ticketing Staff

Figure 4.7: Main Screen for Ticketing Staff

This is the main screen of Airline Reservation System (ARS). The Menu Bar listed the

features of the system. The features include New, Reservation, Query, and Windows.

Report is not allowed to ticketing staff. Each of the features contain its’ sub features.

There are shortcuts for ticketing staff on the left hand side which allows staff quick

access to make reservation, cancel reservation and reservation report.



4.2.6 New Airline Manager Information Screen

Figure 4.8: New Airline Manager Information Screen

When New - Airline manager button is selected on the New menu bar, it will load this

form that enables user to add new airline manager’s details. It includes Login Name,

Password, Confirm Password, Name, Gender, Phone, Mobile Number, Email, I.C. No.,

Birthday, Home Address, Postal Code and State.



4.2.7 New Ticketing Staff Information Screen

Figure 4.9: New Ticketing Staff Information

When New – Ticketing Staff button is selected on the New menu bar, it will load this

form that enables user to add user details. It includes Login Name, Password, Confirm

Password, Name, Gender, Phone, Mobile Number, Email, I.C. No., Birthday, Home

Address, Postal Code and State.



4.2.8 New Flight Information Screen

Figure 4.10: New Flight Information Screen

This screen can be accessed from the main screen through New menu, then New Flight.

New Flight information is where the airline manager key in all flight details to the

system. The details are categorized into New Flight Details (flight code, flight number,

aircraft type and fare), Departure (location, data and time), and Arrival (location, date

and time). Airline manager can later cancel and add flight again when changes occur.



4.2.9 Make Reservation Screen

Figure 4.11: Make Reservation Screen

Make Reservation screen is there the user search for flight information as requested from

the user. When the result is displayed, staff required to enter reservation details. Staff

also needs to click on Add Passenger button to add new information of passenger. Then

fill in the text box for flight code and quantity to be reserved. Then, click Confirm

Reservation button. To print the reservation slip to passenger, click on Print Reservation

button.



4.2.10 New Passenger Information Screen

Figure 4.12: New Passenger Information

When New Passenger button is selected on New in menu bar, it will load this form that

enables user to add passenger details. It includes passenger Name, Gender, I.C. No,

Passport Number, Email, Birthday, Home Street Address, Home Postal Code, Home

State, Home Phone, Mobile, Business Company, Job Title, Department, Office, Business

Street Address, Business Postal Code, Business State, Business Phone and Fax.



4.2.11 Cancel Reservation

Figure 4.13: Cancel Reservation Screen

This page is loaded when user select and click on Cancel Reservation from menu bar. To

cancel a reservation, user will key in the Passenger Passport Number and click Search

button. They also can choose to view all the Reservation Information by clicking on the

View All button. To delete the record, user need to select a record and click on Cancel

Reservation button.



4.2.12 Query of Airline Manager Information Screen

Figure 4.14: Query Airline Manager Information Screen

This page is loaded when Airline Manager is selected from Query in menu bar.

To search for Airline Manager Information, user will key in the Manager Login Name

and click Search. They also can choose to view all the reservation information by

clicking on the button View All. To delete the record, select on the record and click the

button Delete.



4.2.13 Query of Ticketing Staff Information

Figure 4.15: Query of Ticketing Staff Information

This page is loaded when Ticketing Staff is selected from Query in menu bar. To search

for Ticketing Staff Information, user will key in the Staff Login Name and click Search.

They can choose to view all the reservation information by clicking on the button View

All. To delete the record, user can by click on the record and click the button Delete.



4.2.14 Query of Flight Information Screen

Figure 4.16: Query of Flight Information Screen

This page is loaded when Flight is selected from Query in menu bar. To search for Flight

Information, user will key in the Flight Code and click Search button. They can choose

to view all the flight information by clicking on the button View All. To delete the

record, user can by click on the record and click the button Delete.



4.2.15 Query of Passenger Information Screen

Figure 4.17: Query of Passenger Information Screen

This page is loaded when Passenger is selected from Query in menu bar. To search for

Flight Information, user will key in the Passenger Passport Number and click Search.

They can choose to view all the flight information by clicking on the button View All.

To delete the record, user can by click on the record and click the button Delete.



4.2.16 About Screen

Figure 4.18: About Screen

This Screen will appeared when About is selected from Windows in the menu bar. This

screen shows all the information about the program including the names of programmer

team. If you click on the system info, you can see information of the system.



4.2.17 Sample Reports

The following are examples of printed reports from the system:

1. Airline Manager Report

2. Ticketing Staff Report

3. Flight Report

4. Reservation Report

5. Passenger Report



Part 5: System Testing



5.1 Test Plan

TEST

CASES OBJECTIVES

1. To test when the program is run, the login module is display at start up and

make sure the user has to key-in the correct password before entering main

page.

2. Make sure the main page is displayed after keyed-in the correct password.

3. Make sure the New User module will load the form that enables user to

choose whether load the Airline Manager form or Ticketing Staff form.

4. Make sure the Airline Manager form and Ticketing Staff form able to key in

the new login detail and personal detail and added into database.

5. Make sure the New Flight module allow airline manager to key in all flight

details to the system. The details are categorized into New Flight Details,

Departure and Arrival.

6. Make sure Make Reservation module able to search Flight and make

reservation. In Search Flight, user allows to search for flight information as

requested from passenger. Based on search result, reservation is made by

adding new passenger details. Then confirm the reservation and print the

reservation slip.

7. Make sure the Cancel Reservation module is able load the form that enable

user to key in the reservation code to search and cancel the reservation.

8. Make sure the Query’s Airline Manager module enable to check by insert the

manager code. Based on inserted query, the search results will be display.

Then select a record to delete.

9. Make sure the Query’s Ticketing Staff module enable to check by insert the

staff code. Based on inserted query, the search results will be display and



select a record to delete.

10. Make sure the Query’s Flight Information module enables to check by insert

the flight code Based on inserted query, the search results will be display and

select a record to delete.

11. Make sure the Query’s Passenger Information module enable user to search

for passenger name. Based on inserted query, the search results will be display

and select a record to delete.

12. Make sure the Report – Airline Manager, Ticketing Staff, Flight and

Passenger report will display all record to be printed.

13. Make sure the cascade, tile horizontally, tile vertically can function.

14. About ARS information will be display.

15. Make sure the Exit will end the program. The Exit function is in the New

module.

Table 5.1: Test Plan



5.2 System Testing

Testing is a critical element for software quality assurance. The test process is

implemented in our project to execute the system with the intent to find error. Tester

Khoo Boon Yan and Kimberly Lo Sze Yie are required to test the system according to

the test plan prepared by Teh Pei Yee.

Firstly, the login module is tested with both manager and staff login. With a valid user

name and password, the user is able to access to the system according to their

authentication control. Manager login is able to access all functions of the system while

staff login is limited to only make reservation function.

Next, the module of adding new airline manager, ticketing staff and flight are only

accessible to airline manager. Sample records are inserted in the module for testing. All

fields with asterisk (*) must be filled in. Else, there will be a pop out of message box

reminding the user to fill in the important fields. Incomplete fill-in is not able to add as a

new record. The module of query for all four tables of airline manager, ticketing staff,

flight and passenger is tested too. Search criteria such as manager login name, staff login

name, flight code and passenger passport number is inserted to search record. The

function of delete is also working properly. Thus, both ‘New’ and ‘Query’ module is



tested successfully. The system is error-free from adding, searching and deleting

records.

Then, the system is re-login with staff’s login. The module of ‘Make Reservation’ is

tested according to test plan. The module is able to search for requested flight. Then,

tested on add new passenger details and confirmed on the reservation to print the

reservation slip.

In sum, the system is free from bugs and errors. All forms are correctly loaded when

selected interactive button is clicked. The windows in the system are also able to arrange

in cascade, tile horizontally and tile vertically according to user preference’s click from

‘Window’ menu. Information about the system is shown in ‘About’. The system is then

also tested to exit properly. Finally, the verification is done by Lee Heng Leng to

confirm the system meets the specifications of error-free. All tests are successful as

expected results.



Part 6: Developer’s Progress Work



6.1 Contribution of Lee Heng Leng

After some discussion at the early stages, I was assigned to complete tasks regarding to

drawing charts and diagrams. Charts that I handled were Entity Relationship Diagram

(ERD), Data Flow Diagram (DFD) - Context and Level-0 Diagram for the project. I

managed to finish the context diagram way a head the schedule since it was a simple

task. I continued my work and prepared a Level 0 diagram. Although there were some

minor alterations in the diagram but generally I finished the diagram before the dateline.

Then, I also prepared the data dictionary and data model. Though tasks were given

individually and each members have the responsibility to complete it, but every one of

the group members help each other out in completing their tasks. Besides, I managed to

gather loads of information from different kind of resources including via Internet and

reference books for literature review. I also conducted some researches and an interview

in Malaysia Airlines with other group members for preparation of better project plan.

My following task was screen design to develop the prototype of our system. Since we

had discussed about the concept of the system, we distributed each members to complete

a few forms. I designed the screen of Main Screen, New Flight Information, New

Passenger, Make Reservation and Cancel Reservation. I also wrote explanations on each

screen shots of the system previews for interim report.



After the submission of interim report and prototype, we got the approval from our

supervisor in further development of the project. My group members and I reviewed on

the previous project work that we have done. I had made some changes for the interface

of the system such as for Main Menu Screen, Airline Manager, Ticketing Staff, Make

Reservation and Query. For the coding, I wrote part of the code for connection to

database, adding, searching and deleting. I also created the vertical menu in Main Menu,

Splash Screen and About form for the system. The system was successfully developed

with good team work. After completed system was tested by group members, I verified

the acceptant test.

For final report, I reviewed on all documents and make changes for the mistakes that the

group members had done. I also modified and rewrote the management summary and

conclusion. Then, I wrote on my own individual contribution and weekly log. Finally, I

converted the document from Microsoft Word format into PDF format.



6.2 Contribution of Agnes Khoo Boon Yan

As a member of the team, I had dedicated to jobs assigned by group leader. My role in

this project is as a programming leader. Thus, my job scope is not much related to the

paper work. I focused more on visual basic programming in developing the system.

For the interim report, I have prepared the cover, interview section and literature review.

I wrote a request letter to Malaysia Airlines (MAS) to request an interview section with

the Information Technology’s General Manager. I also had prepared the question for

interview section. During the interview session, I was in charged to interview the

manager with group leader while other group members responsible to jot down the

conversation. After we did the interview, I wrote a report to summarize the interview for

literature review. At the same time, I also wrote the interview dialog to keep it as

appendix in interim report. For the prototype, I had helped to prepare the interface of

Passenger Information, Flight Information and Make Reservation. Besides, I also help

my group mate to finish some part of project scope and management summary.

As programming manager, I had worked with group leader, Miss Lee Heng Leng, to find

solutions to connect the program to database. Besides, I also wrote coding to program

the staff login, manager login, add new airline manager, add new staff, add new flights

information and query for flights and passengers. I also helped the group leader to find



references of coding to solve the problems of some function that could not work

properly in our program. At the same time, I also wrote the coding for disabling some

features for ticketing staff’s login. After the system is successfully developed, I test on

the system to make remarks.

For the final report, I was in charged in Part 5: System Preview which requires in

capturing the system’s screen and explained the on each screen shots. I also prepared the

cover for the final report. And the last task I have done is preparing my weekly log and

individual contribution.



6.3 Contribution of Teh Pei Yee

The objectives of the team members are to build a successful Airline Reservation

System. As a member of Airline Reservation System members, I am willing to

contribute myself on ideas, financial, design and time in order to accelerating our

project.

As a Database Manager of Airline Reservation System, I documented the minutes of

meeting to keep track of details of discussion and arising matters. Meeting had been

arranged as scheduled. Meetings are recorded as minutes to keep track of discussion as

future reference. Beside that, I had handled the Project Schedule – Gantt chart, Team

Organization, Project Standards & Procedures, Milestones and Implementation Plan. For

the Implementation plan, I need to include another Gantt chart and Milestones. I had

make some changed at the Implementation Plan after the Interim report. I had learned

how to use Microsoft project to draw Gantt chart. And, I had learned how to use

Microsoft Visio to draw flow chart for the team organization. I need to ensure that

documents are ready in time and in precise manner by following the schedule of Gantt

chart.

In addition, I managed to gather loads of information from Internet and reference books

for literature review. I also conducted some researches and an interview in Malaysia



Airlines with other group members for preparation of a better project plan. During the

interview Section at Malaysia Airlines office, Documentation manager and I had

collected all the information during the Interview. After that, our Programming Manager

will make a final Interview Section. .

For the System Preview, I had done for the Login Screen prototype. Besides, I also had

created all tables in the database of Airline by using SQL server. There are Airline

Manager, Ticketing Staff, Flight, Passenger and Reservation table. I need to make sure

the primary key, fieldname and the data type is correct. If not, it can not run the Airline

Reservation system. So, that is important to create the tables. Beside that, I need to

prepare the test plan and the acceptance test. It will help our tester to test the system. I

did the Data report for Airline manager, Ticketing Staff, Flight and Passenger. I connect

it by using Data Environment. Then I need to create 4 commands so that I can connect

Airline manager, Ticketing Staff, Passenger and Flight from database. When the Airline

Reservation System can run successfully, I have inserted some sample records into the

database.



6.4 Contribution of Kimberly Lo Sze Yie

As a part of the group members, I was assigned to complete the task of the

documentation after the first discussion. As a Documentation Manager, I was

responsible to collect the entire document from other group members that had handle by

them and I will finalize the interim document and print it out. Before print the interim

report, I checked for the arrangement and the documentation format. I kept the Master

Copy for backup. I followed up the changes of the documentation from time to time if

there is a change. During the period, I had done the Acknowledgement, Objectives,

Management Summary, Project Scope, Conclusion, and Bibliography. During the period

of doing the given task, I faced some problem. I have some difficulty in doing the

Management Summary and Project Scope. However, with the help of the other group

members, I manage to finish it before the deadline.

Besides, I also did the prototype for the system namely New Staff Information by using

the Microsoft Visual Basic 6.0. I had made an interview in Malaysia Airline System

(MAS) with other group members for our project case study. From the interview we get

more ideas on our project. During the interview session, Database Manager and I were

responsible to jot down the interview dialog between the I.T. Manager of MAS, our

Team Leader and Programming Manager.



After the first part of the preparation, we have to concentrate on the final report and the

system function part. I had done the conclusion part for final report which is System

Limitations and Further Enhancement. I also did the Visual Basic coding for Delete

Function. After we had complete develop the system, we have a testing plan. I was

assigned to be the tester of the system. As a tester, I have the responsibility to make sure

that the system is run smoothly without any errors. I did the testing according to the

testing plan. I have to follow the step that list in the testing plan and test it one by one. It

is to make sure that everything are being tested and run completely. If there is any error,

I will have discussion with the programming manager and database manager to make

improvement of our system.



6.5 Developer’s Weekly Log

Developer’s Name: Lee Heng Leng (Team Leader)

No. Date Tasks ExpectedEnd Date

Actual End Date

Comments

1 12/18/2003 Prepare project proposal 12/19/2003 12/19/2003 Airline Reservation System 2 12/21/2003 Define project goal and

documentation format 12/22/2004 12/22/2004

3 12/23/2004 Research and study on existing airline reservation system

1/12/2004 1/12/2004 Documentation on primary study, system concepts, features and bibliography

4 1/3/2004 Define flow of system in analysis and design

1/8/2004 1/10/2004 Design data dictionary, ERD, DFD - context diagram & Level 1 diagram

5 1/3/2004 Develop prototype – creating interface of system

1/12/2004 1/10/2004 Form created – Main Screen, New Flight, New Passenger, Make & Cancel Reservation

6 1/10/2004 Collect all forms from group members and linked in prototype

1/15/2004 1/12/2004 Refer to books to learn some visual basic coding

7 2/2/2004 Presentation 1 preparation 2/6/2004 2/6/2004 8 2/10/2004 Update prototype 2/25/2004 2/28/2004 Add Splash and About screen to system.

Changes on Reservation and History forms

9 2/15/2004 Redo data dictionary & relationship diagram

2/18/2004 2/18/2004 Required changes of tables in database

10 2/28/2004 Connection of Visual Basic to database of SQL Server

3/1/2004 3/1/2004 Connect with ODBC and ADODC.

11 3/1/2004 Visual basic coding to enhance system

3/11/2004 3/10/2004 Function of adding, deleting and searching records.

12 3/11/2004 Verified acceptant test 3/12/2004 3/12/2004 13 3/13/2004 Convert final report into PDF format. 3/13/2004 3/13/2004 Using Adobe Acrobat 6.0 Professional

Table 6.1: Lee Heng Leng’s Weekly Log



Developer’s Name: Agnes Khoo Boon Yan (Programming Leader)

No Date Tasks ExpectedEnd Date

Actual End Date

Comments

1 12/18/2003 Prepare project proposal 12/19/2003 12/19/2003 Airline Reservation System. 2 12/22/2003 Prepare for case study and gather

information of company. 12/22/2003 12/22/2003 Malaysia Airlines (MAS)

3. 12/27/2003 Prepare interview questions 12/24/2003 12/23/20034. 12/30/2003 Write request letter to MAS request

for interview 2/1/2003 30/12/2003 Make arrangement for interview section.

5. 1/2/2004 Research and study on existing airline reservation system

1/16/2004 1/12/2004 Successful make a visit at MAS office.

6. 1/8/2004 Develop prototype – creating interface of system

1/12/2004 1/10/2004 Created prototype for- Customers information, Flights information and also Reservation Customers Information

7. 1/14/2004 Prepare dialog for interview section 1/15/2004 1/15//2004 8 1/16/2004 Study existing system, prepare

research result of the system 18/01/2004 18/01/2004 Case Studies

9. 2/2/2004 Presentation 1 preparation 2/5/2004 2/5/2004 10 2/28/2004 Connection of Visual Basic to

database of SQL Server 3/1/2004 3/1/2004 Connect with ODBC and ADODC.

11 3/1/2004 Visual basic coding to enhance system

3/11/2004 3/10/2004 Programming for Login, Manager Login, New Airline Manager, New Ticketing Staff, New Flights and Query for Flights and Passenger. Coding to disable certain feature for staff login.

12 3/11/2004 Fix program’s errors and bugs 3/11/2004 3/11/2004 Entity name in database not match with program, Minor errors fixed

13 3/12/2004 Test the system 3/12/2004 3/12/2004 Project completed

Table 6.2: Agnes Khoo’s Weekly Log



Developer’s Name: Teh Pei Yee (Database Manager)

No. Date Tasks ExpectedEnd Date

Actual End Date

Comments

1 12/21/2003 Prepare Project Planning 12/30/2003 12/30/2003 Define Project Standard and Procedures, Gantt Chart, Milestones and Team Organization.

2 12/23/2003 Prepare first minute of meeting 12/24/2003 12/23/2003 3 12/30/2003 Prepare second minute of meeting 12/31/2003 12/30/2003 4 1/1/2004 Prepare Project Plan 1/3/2004 1/3/2004 Gantt Chart, Milestone 5 1/2/2004 Research and study on existing

airline reservation system 1/12/2004 1/12/2004 Successful make a visit at MAS office.

6 1/6/2004 Prepare third minute of meeting 1/7/2004 1/7/2004 7 1/8/2004 Develop prototype – creating

interface of system 1/12/2004 1/10/2004 Created Login Form.

8 1/3/2004 Prepare fourth minute of meeting 1/14/2004 1/13/2004 9 1/5/2004 Prepare Implementation Plan 1/7/2004 1/7/2004 Gantt Chart, Milestone

10 1/9/2004 Prepare minute of meeting with supervisor.

1/9/2004 1/9/2004

11 2/10/2004 Prepare minute of meeting with supervisor.

2/11/2004 2/11/2004

12 2/10/2004 Update and make some change in the Implementation Plan

2/25/2004 2/28/2004 Analyzes the Gantt Chart.

14. 2/17/2004 Prepare fifth minute of meeting 2/17/2004 2/17/2004 15. 2/24/2004 Prepare sixth minute of meeting 2/24/2004 2/24/2004 16. 2/26/2004 Create all tables in the Database of

Airline 2/29/2004 2/29/2004 Tables: Airline Manager, Ticketing Staff,

Passenger, Flight, and Reservation. 17. 3/2/2004 Prepare seventh minute of meeting 3/2/2004 3/2/2004 18. 3/2/2004 Prepare the Test Plan and the

Acceptance Test 3/9/2004 3/9/2004

19. 3/9/2004 Design and connect Report forms to database

3/10/2004 3/10/2004 Report – Airline manager, Ticketing staff, Flight, Passenger

Table 6.3: Teh Pei Yee’s Weekly Log



Developer’s Name: Kimberly Lo Sze Yie (Document Manager)

No. Date Tasks Expected EndDate

Actual End Date

Comments

1 12/23/03 Project Plan 12/29/03 12/29/03 Acknowledgement, Objectives, Problem Statement, Project Scope

2 12/30/03 Preparing interim report 1/05/04 1/5/04 Management Summary, Conclusion, Bibliography, Individual Contribution

3 1/6/04 Develop prototype – design form of system’s interface

1/12/04 1/12/04 Form created -New Ticketing Staff

4 1/13/04 Collect all documents and print interim report

1/15/04 1/15/04 Update all documents

5 2/2/04 Presentation 1 preparation 2/06/04 2/4/04 6 1/3/04 Visual Basic coding 2/14/04 2/13/04 Delete record function 7 1/3/04 Visual Basic coding 2/22/04 2/28/04 Repair previous function 8 1/3/04 Write project conclusion, system

limitation and further enhancement 3/07/04 3/7/04

9 7/3/04 Complete final report with corrected grammar and format

3/12/04 3/10/04 Submitted to group leader after completing

10 10/03/04 Test the system and make remarks 3/12/04 3/12/04 All test successful

Table 6.4: Kimberly Lo’s Weekly Log



Part 7: Conclusion



7.1 Conclusion

The answer to information technology is a theoretical and an empirical, hands-on

discipline. The objective of this project, which aims to expose Centre of Affiliated

Diploma Programme (CADP)’s undergraduate student through the practical experience

of working on a large project, has given us a chance to put into practice of the software

development concepts that we have only been studied in theories. We are trained to

work effectively as part of team, interacting with users, developing specification and

documents developing prototypes and improving our writing and oral presentation skills.

Throughout this final trimester, we have developed an airline reservation system. The

system is proposed during title selection of projects. The computer-based airline

reservation system is developed to manage the reservation and sale of airline tickets.

During this project, we expect a chance to sharpen our skills on technical, analysis or

interpersonal skills. This project is finished according to software development life cycle

approach and through this approach we were able to learn more on practically how to

work in a project whether individually or in a group.

On the early stage, we developed the problem project scope and objective to determine

requirements to make the project successfully. There were a few types of modeling we

used such as, Data Flow Diagram - Context Diagram and Level 0 Diagram, and to help



all group members to visualize how the system is going to be. Then, the physical visual

system is developed using Microsoft Visual Basic 6.0 and the database storage managed

by Microsoft SQL Server 2000.

While developing the system, we encountered a lot of problems in visual basic coding. It

is the most problematic part of the entire project. There were errors in programming and

coding. We find references from websites and library. Then, we discuss with our

project’s supervisor to have the solutions. Through the process, we have expanded our

knowledge in visual basic programming. We have also known on connectivity between

the visual basic system to the database manager (Microsoft SQL Server 2000).

Finally the project is completed with the effort of all group members working together

relentlessly. A good teamwork is contributed in this project where group members were

co-operated and well hold their responsibility. Special thanks to Miss Shyamala as our

supervisor of this project who taught us important criteria and skills needed to

successfully fulfill the course requirement.



7.2 System Limitations

The system is finally completed and well-developed as planned. However, there were

several limitations occurred in the system. The limitations are somehow slightly affected

the system. One of the limitations of the software is the system only supports for

domestic flight. Domestic flight means it only handles local flights (within Malaysia).

Reservations are only allowed for all local flights. Passengers are free to make

reservation for local flights at any time and fly to any states they like. However, they

could not make reservations for international flights. This system is unable to support

huge international flights for all countries.

Besides, the system that we developed also does not offer for specific seat reservation.

Passengers are not allowed to choose their seat according to own preferences. The flight

seat is free-seat. It based on first-come-first-serve. The aircraft is not divided to any first,

business or economics’ seat class. If passengers want to have an own preference seat, he

can arrive early in the plane to choose the seat before others do. However, late comers

are only provided to available empty seat.

In addition, the system is also limiting to no edit feature for inserted record in the

system. Users need to be alert when inserting new records as there were no editing

feature for all tables. After making a reservation or inserting new record, no changes are



allowed. If passengers request to change their flight in case of emergency, they have to

cancel the previous reservation and make a new reservation. The system does not

provide any feature to for passenger to change their reservation directly. Sometimes

passengers might be frustrated to cancel their reservation and make a new one.

Therefore, passengers are also advised to confirm their reservations before making any

flights reservation.



7.3 Further Enhancements

The system can be further enhanced with a seat reservation available. It is to fulfill

passengers request to sit where they prefer. They are allowed to choose their seat

whether near to window’s seat or in the middle. Ticketing staff can helps passengers to

book their seat by just clicking ‘seat plan’ button of the specific flight that they want to

take. When the button is clicked, seat plan is showed and ticketing staff will help

passengers to reserve the seats. Once the seat is reserved, it is not allowed to any other

passengers. Besides, the system can also be expanded into an international airline

reservation system. With this implementation, the system would be able to use in world

wide airlines. It is also preferably to increase the effectiveness and productivity of the

flight reservation system. All classes of passengers such as students, business men and

tourists can use this system to make reservation to wherever they want to go. In other

hand, to ease the user while using the system, the system will be further enhanced with

editing and updating record functions. Ticketing staff can edit an inserted record directly

without canceling and then adding a new record. Passengers also do not need to cancel

and redo their reservations. They can change their flight reservation as they wish. With

this enhancement, user will be satisfied and it also brings convenient to passengers as

they can take another flight in case of personal emergency.



Part 8: Bibliography

[1] “Welcome to Malaysia Airlines”, Malaysia Airlines (2003), http://www.mas.com.myDate Accessed: 1st January 2004 [2] “Welcome to Air Asia”, AirAsia.com (2003), http://www.airasia.com/general.php?p=pmain&l=enDate Accessed: 5th January 2004 [3] “Singapore Airlines”, Singapore Airlines (2003), http://www.singaporeair.comDate Accessed: 10th January 2004 [4] “Japan Airlines”, Japan Air System (2003), http://www.jal.co.jp/en/Date Accessed: 10 January 2004 th

[5] “Case Study: Airline Reservation System”, Naval Postgraduate School (2002) http://www.cs.nps.navy.mil/people/faculty/mantak/AirlineReservationSystem/Date Accessed: 10th January 2004 [6] “Introduction to Apollo Airline Reservation System”, Digital Education (1998) http://www.digitaledu.com/courses/social/SLAR01.htmlDate Accessed: 11th January 2004 [7] “Relational Database Management Systems - Airline Reservation System”, Lay Networks (2003) http://www.laynetworks.com/Relational%20Database%20Management%20Systems.htmDate Accessed: 11th January 2004 [8] “Case Studies: Airline Seat Company Takes Off with WRQ Verastream”, WRQ (2003), http://www.wrq.com/customers/casestudies/airline_seat.htmlDate Accessed: 12th January 2004 [9] “A Sophisticated Airline Reservation System”, AxsRes (2003) http://www.eds.ch/fileadmin/countries/eds_ch/portfolio/air_transportation/obaxsRes.pdfDate Accessed: 12th January 2004 [10] “Transportation to Lift Rules on Airline Reservation Systems”, Post-Newsweek Media, Inc. (2004), http://www.gcn.com/vol1_no1/daily-updates/24530-1.htmlDate Accessed: 14th January 2004 [11] “eBay Travel –Airline Tickets”, eBay Inc. (2004), http://pages.ebay.com/travel/index.html?ssPageName=MOPS5:HTR01


http://www.mas.com.my/

http://www.airasia.com/general.php?p=pmain&l=en

http://www.singaporeair.com/

http://www.jal.co.jp/en/

http://www.cs.nps.navy.mil/people/faculty/mantak/AirlineReservationSystem/

http://www.digitaledu.com/courses/social/SLAR01.html

http://www.laynetworks.com/Relational Database Management Systems.htm

http://www.wrq.com/customers/casestudies/airline_seat.html

http://www.eds.ch/fileadmin/countries/eds_ch/portfolio/air_transportation/ob_axsRes.pdf

http://www.gcn.com/vol1_no1/daily-updates/24530-1.html

http://pages.ebay.com/travel/index.html?ssPageName=MOPS5:HTR01


Date Accessed: 14th January 2004 [12] Jennifer Davies, “Confirm: Computerized Reservation System”, University of Wolverhampton (2002), http://www.scit.wlv.ac.uk/~cm1995/cbr/cases/case06/FOUR.HTMDate Accessed: 14th January 2004 [13] “Travel Time”, Travel Time, Inc. (1995 – 2004), http://www.traveltime.com/Date Accessed: 14th January 2004 [14] “Aeroflot Russian Airlines”, Aeroflot (2003), http://www.aeroflot.com/news/news.shtml?news_id=26Date Accessed: 16th January 2004 [15] “Computerized Reservation System: Analysis and Impact Assessment”, NBTA Aviation Committee (2004), http://www.nbta.org/newsroom/documents/CRS_04_Summary.pdfDate Accessed: 16th January 2004 [16] “Case Study: Air France”, Barry & Associates, Inc. (2003) http://www.service-architecture.com/object-oriented-databases/articles/air_france.htmlDate Accessed: 20th January 2004 [17] “Visual Basic Source Code”, KATHER Produkties (2000) http://www.kather.net/visualbasicsource/codesnippets/scindex.htmDate Accessed: 20th February 2004 [18] "Designing Complex Interfaces in VB", DevX.com (2003) http://www.devx.com/getHelpOn/Article/17577/0/page/1 Date Accessed: 20th February 2004


http://www.scit.wlv.ac.uk/~cm1995/cbr/cases/case06/FOUR.HTM

http://www.traveltime.com/

http://www.aeroflot.com/news/news.shtml?news_id=26

http://www.nbta.org/newsroom/documents/CRS_04_Summary.pdf

http://www.service-architecture.com/object-oriented-databases/articles/air_france.html

http://www.kather.net/visualbasicsource/codesnippets/scindex.htm


Part 9: Appendixes



Appendix A: Minutes of Meeting

First Discussion of Airline Reservation System

Date: Tuesday, 23rd December 2003

Time: 9.20 pm

Venue: CLC ground floor

Present: Lee Heng Leng, Teh Pei Yee, Kimberly Lo Sze Yie, Agnes Khoo

Boon Yan

No. DESCRIPTION

1.0

1.1

2.0

2.1

2.2

3.0

3.1

3.2

Topic Selection

Airline Reservation System has been chosen for our Final Year Project.

Proposal had been submitted on 19th December 2003.

Project Grouping and Position Assigning

The project team is formed consisting of four students who are taking the

subject of Computing Project (DCS 5095).

Each members is assigned to a different position:

a) Lee Heng Leng (DM009) as Team Leader.

b) Agnes Khoo Boon Yan (DM007) as Programming Leader.

c) Teh Pei Yee (DM007) as Database Manager.

d) Kimberly Lo Sze Yie (DM007) as Document Manager.

Software selection for the project

The project will be developed using Microsoft Visual Basic 6.0.

Several considerations were taken on using Microsoft Access and Microsoft



3.3

4.0

4.1

5.0

5.1

SQL Server for database management.

After discussion among group members, Microsoft SQL server 2000 has been

chosen to manage the project database.

Request Letter

Miss Agnes Khoo assigned to prepare and send the request letter to conduct a

visit to Malaysia Airline (MAS). We need to get do case study on airline

reservation system.

Project Plan Discussion

Project plan’s for the elements as following:

No Task Person In Charged

1 Acknowledgement Miss Kimberly Lo

2 Objective Miss Kimberly Lo

3 Problem Statement Miss Kimberly Lo

4 Project Scope Miss Kimberly Lo

5 Question for interview Miss Agnes Khoo

6 Team Organization Miss Teh Pei Yee

7 Project Schedule – Gantt Chart Miss Teh Pei Yee

8 Project Standard and Procedures Miss Teh Pei Yee

9 Minute Meeting Miss Teh Pei Yee

10 Data Flow Diagram (DFD) Miss Lee Heng Leng

11 Entity Relationship Diagram (ERD) Miss Lee Heng Leng

12 Develop System’s Prototype Miss Lee Heng Leng &

Miss Agnes Khoo



Second Discussion of Airline Reservation System

Date: Tuesday, 30th December 2003

Time: 2.10 pm

Venue: Plaza Siswa


Boon Yan

No. DESCRIPTION

1.0

1.1

1.2

Project Plan Discussion

Discuss the problem that we encountered.

Project Plan’ s element as the following

No Task Person In Charged

1 Overview Miss Lee Heng Leng

2 Project Goals Miss Lee Heng Leng

3 Documentation Format Miss Lee Heng Leng

4 Case study & Literature Review Miss Lee Heng Leng &

Miss Agnes Khoo

5 Interview Summary Miss Agnes Khoo

6 Milestone Miss Teh Pei Yee

7 Implementation Plan Miss Teh Pei Yee

8 Management Summary Miss Kimberly Lo

9 Conclusion Miss Kimberly Lo

10 Bibliography Miss Kimberly Lo

11 Cover Page Miss Agnes Khoo



2.0

3.0

3.1

4.0

Discussion on System Screen Design ( Prototype)

The system based on the module of Airline Manager, Ticketing Staff,

Reservation, Flight and Passenger.

Discussion for the next meeting

Next meetin will be held in Miss Teh Pei Yee and Miss Agnes Khoo Boon

Yan’s house. Miss Teh Pei Yee’s computer will be used to database

management and Miss Khoo Boon Yan’s computer will be use as for Visual

Basic programming.

Request letter

Miss Agnes Khoo will send the request letter to MAS office in this week.



Third Discussion of Airline Reservation System

Date: Tuesday, 6th Jan 2004

Time: 2 pm

Venue: Lee Heng Leng’s room


Boon Yan

No. DESCRIPTION

1.0

1.1

2.0

2.1

3.0

Venue

The venue as planned in last meeting for had changed due to personal reason.

Discussion

All copies of what we documentation will be submitted to team leader, Miss

Lee Heng Leng. She will check all documents are correct. After that, the

document will be passed to document manager.

Screen design

This main screen of system’s interface had been developed by Miss Lee Heng

Leng. Each member is assigned to some tasks of screen designing of the

prototype.

No Task Person In Charged 1 Main, New Flight, New Reservation,

New Passenger, Cancel Reservation. Miss Lee Heng Leng

2. New Ticketing Staff Miss Kimberly Lo 3. Query Flight, Query Passenger, Query

Reservation. Miss Agnes Khoo

4. Login Page Miss Teh Pei Yee



Fourth Discussion of Airline Reservation System

Date: Tuesday, 13th Jan 2004

Time: 2 pm


Present: Lee Heng Leng, Teh Pei Yee, Kimberly Lo Sze Yie, Agnes Khoo Boon

Yan

No. DESCRIPTION

1.0

1.1

2.0

2.1

3.0

4.0

4.1

Interim Report

We discussed the table of content in the interim report. We plan to submit the

interim report by 16th of January 2004. On the 15th January 2004, all members

need submit their documentation to Document Manager.

Gantt Chart

Miss Teh Pei Yee had completed a Gantt chart. She was assigned to prepare

another Gantt chart for the Implementation Plan.

Screen design

Programming Leader, Miss Agnes Khoo assigned to design reservation query

form in visual basic.

Individual Contribution

All members assigned to write their own individual contribution.



Meeting with Supervisor

Date: Friday, 9th January 2004

Time: 2 pm

Venue: Miss Shyamala’s office


Boon Yan

No. DESCRIPTION

1.0

2.0

3.0

4.0

5.0

6.0

Gantt Chart

Minute Meeting

Interim Report

Data Flow Diagram

Entity Relationship Diagram

Interview Questions



Meeting with Supervisor

Date: Tuesday, 10th February 2004

Time: 4 pm

Venue: Miss Shyamala’s office


Yan

No. DESCRIPTION 1.0 2.0 3.0 4.0 5.0 6.0 7.0 8.0

Database using Microsoft SQL Sever 2000 Operating System on server side – Windows 2000 Server Connection via ODBC Presentation 2 Final Report Seat Plan Acceptance Test Client and server configuration



Fifth Discussion of Airline Reservation System


Time: 2.00 pm

Venue: FBL 4021


Yan

No. DESCRIPTION

1.0

1.1

2.0

2.1

3.0

3.1

3.2

4.0

5.0

Review on Previous Project Work ( Interim Report )

We constructed a full review on interim report. We analyzed the problems and

discussed on improvements to be made.

Database

Microsoft SQL Server 2000 is used to manage the system’s database and

Microsoft Windows 2000 Server is used as our operating system for the server

side.

Project Plan

Refer to milestones for all task’s date completion.

Refer to Gantt Chart to ensure flow of works.

Prototype

Changes will be made on the prototype to ease the use of the system.

Seat plan

Miss Agnes Khoo assigned to develop seat plan referring to aircraft Boeing 747-

200



Sixth Discussion of Airline Reservation System


Time: 2.00 pm



Yan

No. DESCRIPTION

1.0

1.1

1.2

2.0

2.1

Database Management

Problems occurred when connecting the system (Microsoft Visual Basic 6.0) to

database (Microsoft SQL Server 2000) All members assigned to find the solution.

Final decision on using Miss Agnes Khoo‘s computer as a server and Miss Lee

Heng Leng‘s computer as a client.

Documentation Discussion

Project plan’s element are included as following:

No Task Person In Charged 1 Documentation on Conclusion, System

Limitation and Further Enhancement. Miss Kimberly Lo

2 Seat Plan, Connection, VB Coding Miss Agnes Khoo 3 Test Plan, Acceptance Test and database

management. Miss Teh Pei Yee

4 Connection, update and modification of the system’s interface such as frmAirlineManager, frmStaff, frmPassenger, mnuHistory, frmSplash, frmabout, frmMake Reservation, frmCheckReservation, msgbox, etc.

Miss Lee Heng Leng



Seventh Discussion of Airline Reservation System

Date: Tuesday, 2nd March 2004

Time: 2.00 pm

Venue: Jaya Jusco Food Court


Yan

No. DESCRIPTION

1.0

2.0

2.1

2.2

2.3

System

On 9th of March 2004, Tuesday, all members were assigned to involve in the

Testing Evaluation. Miss Teh Pei Yee will prepare the Testing Plan and Miss

Kimberly will be as a tester. Meanwhile, Miss Lee Heng Leng will prepare

client/server installation guide and Miss Agnes Khoo will setup the client/server

installation.

Final Check

Miss Kimberly Lo, documentation manager, needs to do final checking on the

entire final report.

Team leader, Miss Lee Heng Leng will check the overall development and

implementation of the documentation, connection, and the program.

Programming leader, Miss Agnes Khoo assigned to conduct the programming

tasks. She needs to check for program’s errors and debug, add comments to the



2.4

3.0

3.1

program’s coding for better understanding.

Database manager, Miss Teh Pei Yee checks on database whether got any errors

and ensure the program successfully connected to the database.

Individual Contribution and weekly log

Each group member need to prepare their own individual contribution and weekly

log.



Appendix B: Request Interview Letter

50, Jalan Bukit Beruang 3, Taman Bukit Beruang, Bukit Beruang, 75450 Melaka. IT General Manager, Malaysia Airline, 4th floor, MAS Building, 50250 Jalan Sultan Ismail, Kuala Lumpur. 2-01-2004 Dear Sir, Request For Interview With regards to the matter above, we as a team of 4 from Multimedia University Diploma IT final years students would like to have an interview with you regarding MAS Flight Reservation system. 2. We are currently embarking on final year project entitle “Computerize Airline Reservation System”, hence the objective of this interview is to know more about current MAS Flight Reservation System and also to find out what are the future enhancement features that can added to improve. Below are details of 4 of us

I. Agnes Khoo Boon Yan ID: 1021179431 II. Joey Lee Heng Leng ID: 1021191630 III. Teh Pei Yee ID: 1021103633 IV. Kimberly Lo Sze Yie ID: 1021191368

3. Enclose is the recommendation letter from our supervisor. We hope that you can make our interview session on 9/1/2004(Friday), 2:30p.m. However, if this date is not convenient to you, we hope you can make another arrangement before 16/1/2004.



4. You can contact any of the following persons if you have enquiry towards this interview section.

I. Agnes Khoo Boon Yan 016-2049587 II. Joey Lee Heng Leng 016-4541391

5. We sincerely hope that you will give your support and cooperation as it is very crucial to our project research. Thank you in advance. Sincerely, ________________ (Khoo Boon Yan) Project Secretary H/P- 0162049587



Appendix C: Interview Questions

Section 1 – Tourism Companies/Airlines

1. How do you book the multiple tickets from the airport?

2. Do you face any difficulties or complaints from the customers?

3. Do you use system to book tickets?

4. How does the system link to the airline?

5. Is the system efficient?

6. How is the connection speed?

7. Is the system user friendly/interface/content relativity

8. Does system down often?

9. What details/particular from the customers that you usually get?

10. Do you check financial status of the customers?

11. Does the system check for criminal status?

12. How to pay deposit?

13. Does the system has any rules/regulation/information for customers?

14. What the procedure from a customers book the ticket till get ticket?

15. How to do the transaction for payment

16. How is the security, database/admin login

17. What are improvement you think should be implemented



18. What are the benefits, pros and cons before and after the existing of the system?

19. How you store your previous customers information

20. How you change the destination, date, time of the customers’ ticket

21. How you cater the elderly and disable people

22. How to reserve the special seat from the customer requirement?

23. What type of the report the system will be generated?

Section2 – Airlines

1. What OS, network. Storage?

2. How big is the database? or how big is your data warehouse?

3. How you backup

4. How often you back up

5. What technology that you use to back up

6. How you define the security terms in your system?

7. What language that you use to develop the system

8. Do you have any plan to upgrade your system?

9. Does your company upgrade the system before?

10. Do you mind to share your plan with us?

11. What are the others channels. That the customers can make the reservation? Such

as wap, gprs, or telephone automated answering?

12. What is accurately of the system? Error?



13. How you solve this?

14. Can the statistics report be generated?

15. What types of reports and what is their repetitive purpose?

16. Regarding the administrator login, how many level of log in that you have? Like

administrator login, management log in and front test log in?



Appendix D: Interview Session

We start our interview section with Mr. Terrance which is IT Sales and Marketing

manager sharp at three o ‘clock. Joey Lee Heng Leng and Agnes Khoo Boon Yan in

charge to ask question regarding the airline reservation system that use by Malaysia

Airlines (MAS). Teh Pei Yee and Kimberly Lo Sze Yie in charge to jot down the

answers from Mr. Terrance. Below are the dialogs between us.

T = Mr. Terrance

J = Joey Lee Heng Leng

A = Agnes Khoo Boon Yan

J: Good afternoon Mr. Terrance. I am Joey Lee Heng Leng, group leader of our

project, nice to meet you. Let me introduce, this is Agnes Khoo, this is Kimberly and

this is Teh Pei Yee. We are all final year diploma student from MMU.

T: Nice to meet you too. Is there anything that I can help you all?

J: Yes, we are here to know details about ticket reservation system that currently

use by MAS.



T: O.k. The name of our ticket reservation system is KOMMAS. KOMMAS is a

DOS-base system that use by MAS for ticket reservation. This system has 25 years

history. It had been upgrade for 4 times in these 25 years to add more features in it.

Now, we still are using this system to do reservation for customers. All brunch of MAS

in overseas are using the same system to do reservation too. The system can check on

the departure time and day to specific place. Not only flights that offer by MAS but also

flights offered by other airline systems in Malaysia and overseas.

J: Ic. So can you tell us how the reservation been done from head to toe?

T: Sure! For reservation, the reservation person will key in the record and book the

tickets. Once booked, the system will check whether the flights or seats is confirm. This

system has link to the capacity of the aircraft. For example, this system tells the number

of seats occupied and empty seats for each class. If the seats had full, a note will pop up

say that seats are full and confirm can not be made. By this function, the reservation

person can tells the more accurately about which seats are available to customers. The

reservation person will then confirm with customers. Once confirm, the customers will

go to the ticketing counter to take the ticket and pay the money. The reservation person

will key in the reference number to the system. The information of customers will pop

up if he had made the reservation.

A: Is there any deposit required in for ticket reservation?



T: This is no deposit required.

J: Did you have deadline for customers to collect the ticket?

T: Yes, customer will need to collect the ticket 2 weeks before the departure time.

Else the reservation will automatically cancel by the system. This is to enable other

customer can make reservation. However, there are special cases that customers can not

collect the ticket within this time period. So those customers, if they called to our

counter and tell us their problem, we will change the deadline for then to collect the

ticket in the system.

A: Can customers change their departure time or day?

T: Yes, they will have a reference number once they did the reservation. To change

the departure time or day, they will need to give the reference number to the reservation

person. The reservation person just needs to key in the customer’s reference number and

change the details. Customers also can cancel the flights if they couldn’t make it.

A: Do you keep the information of your previous customers?

T: Yes, the system will keep the information of our previous customers for 6 month.

After 6 months the system will automatically remove the information from database.



J: If your customers make any special requirement, what the system will do.

T: for sure we have some customers that will do special requirement. For example,

some people may have elegy to certain food, the reservation person will key in this

special requirement for food into the system, so that special meal will be provided to this

person. Customers also can choose seat that they prefer. In the other words, this system

is customers friendly.

J: Who has the authority to make the reservation?

T: Booking is done by reservation department. But ticketing department also can

access it and make reservation for customers. Ticketing and reservation department are

link to each other, they can access the same database.

A: I there any other ways for customers to do reservation except call to the counter?

T: Yes. They can make their reservation through travel agent. Reservation system

that use by travel agent has a link to KOMMAS. The process is some with our

reservation system. KOMMAS will know which travel agent had booked the ticket.

A: is there any level of access in this system?



T: Yes. Different position will have different level of access. KOMMAS have a

specific code for the user of this system. For persons who make reservation and

ticketing, they have the highest accessibility to use the system. For managing level, they

just can access the system and check the report of flights and customer’s reservation

information. For administration level of this system, they can customize the flights and

departure time.

J: does the system generate report?

T: Yes, but the problem is we can not get the report according to our personal

requirement.

J: does system down happened before?

T: Yes, for few times. When the system is down, all the ticketing reservation will do

manually.

A: Do you backup the information of flights and customers?

T: Sure! The system will backup the information of all flights and customers’

information. This is to prevent the damage of database due to virus or physical damage.

So, there is no reason that we will lose our data.



J: Does the system have any weakness?

T: Yes. It can not generate report according to the requirement of user. Also, this

system has no basic intelligent. We will only get the report after one or two weeks. Due

to this system is DOS base, the interface of this system may not attractive. Also, it is not

user friendly enough for us. We will need to memorize all the codes or make reference

to the booklet given to check on the code to make reservation, to view reports, to check

on flight and etc. Information that shown out from the system is messy. For the beginner

user of this system, they will face the difficulties to understand the information shown.

For the security part, user do not have own password to get into the system. They get

into the system just by using the access code that they had given.

A: Do you have any plan to upgrade your system?

T: Yes, we are now moving forward online reservation. But, we are not going to

upgrade the system. We will buy the system for online reservation from outside. The

reason is MAS is not professional in implementing a system by computer. It is better we

let company that expert in doing this to do it.

J: I think we have got the information that we need from you. This is our last

request. Can you show us the reservation system?



T: yes, no problem. But I only have the access code for viewing the report.

J: It’s OK. We don’t mind. Thanks Mr. Terrance.

T: Welcome.

Our interview section last for 1 hour. We got the chance to see the system as well. From

this interview section, we have the idea how the reservation system works.



Appendix E: Test Script

CRITERIA FULFILLED REMARKS

Login Page

Enter valid login staff’s username and

password. Click OK (login confirmation)

to enter the Main page.

Test successful.

None

Click on Manager Login. Enter valid

manager’s login username and password.

Click OK (login confirmation) to enter

the Main page.

Test successful.

None

Enter invalid login password, click OK

and display invalid password message,

require reenter password.

Test successful.

Pop up message box –

“Invalid username and

password”

Enter invalid login username and

password in Manager Login. Click OK

and display invalid password message,

require reenter password.

Test successful.

Pop up message box –

“Invalid username and

password”

Main Menu Screen

For manager login, user can access to full

system features in main menu screen.

Test successful. None

For staff login, some features in the main

screen are disabled.

Test successful. Disabled feature such

as New User, Flight

and Report.

New Airline Manager

Input the login name. If not, there will be



a pop out “Please input login name”

message box.


Input the password. If not, there will be a

pop out “Please input password” message

box.

Test successful.

None

Input the confirm password. If not, there

will be a pop out “Please confirm

password” message box.

Test successful.

None

If the password is not match confirm

password, it will pop out the message box

of “Please make sure the password is

correct” message box.

Test successful.

None

Input record into database by clicking

OK button, then will pop out a successful

record message box.

Test successful.

Field without asterisk *

are allowed to be null.

Click Cancel button to unload the form. Test successful. None

New Ticketing Staff

Input the Login name. If not, there will

be pop out a “Please Input login name”

message box.

Test successful.

None

Input the Password. If not, there will pop

out a “Please input password” message

box.

Test successful.

None

Input the Confirm password. If not, there

will pop out “Please confirm password”

message box.

Test successful.

None

If the password is incorrect, there will

pop out the password is incorrect. “Please

Test successful.

None



make sure the password is correct”

message box.



record message box.

Test successful.

Field without asterisk *

are allowed to be null.

Click Cancel button to unload the form.


New Flight Information

Input the flight number. If not, there will

be pop out a “Please input flight number”

message box.

Test successful.

None

Select aircraft type. If not, there will be

pop out a “Please select aircraft type”

message box.

Test successful.

None

Select departure location. If not, there

will be pop out a “Please select departure

location” message box.

Test successful.

None

Select departure date. If not, there will be

pop out a Please select departure time

message box.

Test successful.

None

Select the departure time. If not, there

will be pop out a Please input departure

time message box.

Test successful.

None

Select the arrival location. If not, there

will be pop out a Please select arrival

location message box.

Test successful.

None

Select departure date. If not, there will be

pop out a Please select departure date

Test successful.

None



message box.

Select departure time. If not, there will be

pop out a Please select departure time

message box.

Test successful.

None



record message box.

Test successful.

No fields are allowed

to be null in this form.


Make Reservation

Select the departing and arriving location,

then click search button to search about

flight information.

Test successful.

None

Display of search results. Test successful. None

Click on the Add Passenger button to

load add passenger form for making

reservation.

Test successful.

None

Input flight code of reservation to be

made. Else message box pop out “Please

input flight code”

Test successful.

None

Input quantity of reservation to be made.

Else message box pop out “Please input

reservation quantity”

Test successful.

None

To confirm reservation, click Confirm

Reservation button.



To print reservation, click on Print

Reservation.


Cancel Reservation



To search a reservation, insert the

reservation code in the query on

Reservation then click Search.

Test successful.

Reservation code must

be integer.

Display search results. Test successful. None

To view all reservation information, click

on the View All button.


Confirm to select a record and click

Cancel Reservation button to cancel the

reservation.

Test successful.

None

Click Quit button to unload the form. Test successful. None

Query of Airline Manager Information

Input the manager code to search Airline

Manager information.

Test successful. Manager code must be

integer.

Based on inserted query, the search

results will be display by clicking the

Search button.

Test successful.

None

To view all query Airline Manager

information, click on the View All button


Select a record and click Delete to delete

the record.



Query of Ticketing Staff Information

Input the staff code to search Ticketing

Staff information.

Test successful. Staff code must be

integer.



Search button.

Test successful.

None

To view all query Ticketing Staff



information, click on the View All

button.



the record.



Query of Flight Information

Input the Flight code to search Flight

information.

Test successful. Flight code must be

integer



Search button.

Test successful.

None

To view all query Flight information,

click on the View All button.



the query.



Query of Passenger Information

Input the Passenger name to search

Passenger information.




Search button.

Test successful.

None

To view all query passenger information,

click on the View All button.



the query.





Report

Click Airline Manager Report menu to

display report.


Click Ticketing Staff Report menu to

display report.


Click Flight Report menu to display

report.


Click Passenger Report menu to display

report.


Window

Click Cascade menu to arrange form

cascade.


Click Tile Horizontally menu to arrange

form tile horizontally.


Click Tile Vertically menu to arrange

form tile vertically.


About

Display about ARS information. Test successful. None

Exit

Display a box that confirm to Exit. Test successful. None

Exit program by clicking Yes. Test successful. None

Not Exit program by clicking No. Test successful. None

Prepared by: Teh Pei Yee

Tested by: Kimberly Lo Sze Yie & Agnes Khoo Boon Yan

Verified by: Lee Heng Leng

Date: 11th March 2004



Appendix F: Client/Server Setup Guide

In large client/server systems, thousands of users may be connected to a SQL Server at

the same time. SQL Server has full protection for these environments, with safeguards

that prevent problems such as having multiple users trying to update the same piece of

data at the same time. SQL Server also effectively allocates the available resources, such

as memory, network bandwidth, and disk I/O, among the multiple users.

Figure 9.1 Client/Server Connection



While SQL Server works very effectively as a server, it can also be used in applications

that need a stand-alone database stored locally on the client. SQL Server can

dynamically configure itself to run efficiently with the resources available on a client

without the need to dedicate a database administrator to each client.

Creating ODBC DSN

You can check for MDAC and force a TCP/IP connection to the server by creating an

ODBC Data Source. Try creating a Domain Server Name (DSN) by following the steps

below:

1. Click on Windows / Start / Control Panel

2. Double Click on Data Sources (ODBC)

(Note: some versions of windows, click Administrative Tools first)

3. Click the System DSN tab

4. Click the Add Button

5. Scroll to the bottom of the driver list and click SQL Server

6. Click the Finish button

7. Type <Your Name> in the Name & Description field

8. In the Server field, type the IP address of the computer where SQL Server

(MSDE) is running

9. Click the Next button

10. Click the "With SQL Server authentication ..." option

11. Click the Client Configuration button

12. Click TCP/IP option for the network library



13. Make sure the Server Alias and Server Name fields have the IP address of your

server

14. Click the Ok button

15. Click the "Connect to SQL server to obtain..." option

16. Enter "sa" (no quotes) for the user name,

17. Leave password blank unless you already had SQL Server and use a different

password


19. Click on "Change the default database to:..." option

20. Click the Database drop down list and select <Your Name>


22. Click the Finish button

23. Click the Test Data Source button

If you follow the above process, your connection will be successfully established.

Reference: http://www.expresstechnology.com/TechBulletins/ClientServer.htm


Final Report

Documents

affiliated diploma programme

teh pei yee

lee heng leng

miss agnes khoo

left hand side

client server setup guide

html date accessed

htm date accessed