Aiou

PIA RESERVATION SYSTEM

CHAPTER # 1

INTRODUCTION

Brief Introduction of the organization  Problem Definition  Scope of the Project  Broad Based Objectives  Specific Objectives 

1

PIA RESERVATION SYSTEM

INTRODUCTION OF PAKISTAN INTERNATIONAL AIRLINE (PIA)

Introduction This is a summary of the History of PIA (PIAC or Pakistan International Airlines Corporation), Pakistan's national flag carrier.

The Formation of PIAC The roots of PIA date to pre-partition, since it acquired Orient Airways, which was the creation of Quaid-e-Azam, Mohammad Ali Jana. On the advice of the Quaid, who realized partition of the Sub-continent was inevitable, Orient Airways, the First Muslim owned airline, was founded in Calcutta, 1946 by Mr. Isphahani. In 1951 the government realized that the Pakistan needed a National Flag carrier; it ordered three Lockheed L-1049C Super Constellations that year and the concept of PIA was established. PIA flew its first service from Karachi to Dacca (now Dhaka) on 07th June 1954, linking the two wings of Eastern and Western Pakistan, the latter now being Bangladesh. The acquisition of Orient Airways through Merger took place in 1955. Flight International's Survey of PIA, 10th April 1969 Thirty three years ago, in Flight International's World Airline Survey, the publication had summarized PIA as follows: Pakistan International Airlines Corporation (PIA) was founded by the Government of Pakistan on March 11, 1955. When PIA took over Orient Airways. 2

PIA RESERVATION SYSTEM

As a company PIA had been founded in 1951 and its first operations were between East and West Pakistan in June 1954. A service to London was begun in early 1955. The Corporation is responsible for the operation of all services within Pakistan, including airbus services and feeder services in East and West Pakistan and regional services to Katmandu, Rangoon and Kabul. An eleven times-weekly service between Karachi and London is operated via points in the Middle East and Europe, and via Moscow. PIA also operates services to Bangkok, Canton and Shanghai and to Jeddah, Nairobi, Dubai, and Doha and to Bahrain and Kuwait. Short takeoff and landing (STOL) aircraft are being considered as a replacement for the helicopter services in East Pakistan. Head Office: PIA Building, Karachi Airport, Pakistan Executives: Managing Director, S. U. Durrani Director of Planning, M. M. Salim Director of Finance, A. Rahman Commercial Director, Anwar Hussain Director of Flight operations, Capt M T Baig Director of Engineering, Aijaz Ali Director of Administration, M. Ahmed Director of Customer services, Capt S. U. Kureshi Director of Operation co-ordination, Capt A. M. Khan Employees 12,670 Fleet Boeing 747 - 300 Boeing 747-200 Airbus A300 - B4 Airbus A-310 Boeing 737 - 300 Fokker F-27-200 / 400 Twin Otter Total 44 Air Crafts

6 4 8 6 7 11 2

Pakistan International in the 70s and 80s In 1974 PIA contracted Negus and Negus of London to re-design a new more attractive livery that would be more favorably attributed to the Airline. They came up with the Green and Gold livery which had remained until the late 80s/Very Early 90s.

3

PIA RESERVATION SYSTEM

The 90s PIA replaced its famous Green and Gold livery with a sportier one of Green, Moss Green and Turquoise stripes. It is said by PIA, that this new theme is a sportier look, representing the active participation and sponsorship of Pakistan's National Sports. In 1999, PIA acquired five Ex-Cathay Pacific Boeing 747-367s to replace the older series 747s operating on Long-Haul International routes. Though some of the older 747s still operate such as in mixed configuration. PIA; Present Day PIA is currently seeking New Aircraft to extend its fleet, interest lies in the Airbus A340, More 747-367s or the Wide body 777. Whilst at the time of writing the exact purchase plans have not been concreted, further evolution of the National Flag carrier will be welcomed by many.

PROBLEM DEFINITOIN The basic problems faced by them are to integrate records and the daily information about the reservation due to the large number of seat reservation, and cancellation of reserved seats, it’s difficult for them to maintain daily records of reservation, and cancellation, so they require much operational staff to maintain the records of daily reservation and cancellation to update records so that they can easily find out the current reserved seats and available seats in different flights. Finally the total daily, monthly and annual reservation records are kept but it is very costly. Another problem is to keep the records of customers from which they can contact the any specific customer in some special cases, like flight cancellation because of bad weather or any government interference. All the records are kept in hard copies. So to keep those hard copies they needed more physical space to keep them safe. For this purpose they used cupboards and other physical things. The big problem is the duplicity in the records, for this reason if there is need to update any record then they had to update it from different hard copies.

SCOPE OF THE PROJECT Scope of the project includes: • • • •

System Analysis System Design System Development System Implementation 4

PIA RESERVATION SYSTEM •

System Testing & Evaluation

•

User Guide (User Documentation)

SYSTEM OBJECTIVES 1The Airline Reservation System (ARS) is a software application to assist an airline with transactions related to making ticket reservations, which includes blocking, reserving, canceling and rescheduling tickets. 2From the viewpoint of the airline o To minimize repetitive work done by the system administrator and reservation clerks. o To maintain consistency among different access modes, e.g. by phone, by web, at the information desk and across different physical locations. The users should be basically taken through the same steps by the system as they go through in conventional desk-reservation systems. o To maintain customer information in case of emergency, e.g. flight cancellation due to inclement weather. The airline company to track user preferences and travel patterns to serve them better, plan routes, for better marketing and efficient scheduling of flights, can also use the profile. 3Maximize the revenue of the airline company by various means: o To increase awareness among frequent travelers about various special Offers and discounts. o To minimize the number of vacant seats on a flight and maximize flight capacity utilization. o To maintain the capability to adopt a flexible pricing policy. The price of the tickets should be dynamically determined based on how early, before the date of departure, the customer buys the ticket. 4A survey conducted by airline companies shows that users of an existing reservation system would respond favorably to an ARS that satisfied or helped them satisfy the following objectives: o To reduce effort and frustration for travelers in scheduling a trip, especially by reducing the search effort for the flight they need to take. o To show all possible combinations and itineraries available for a pair of origin-destination cities. o To reduce redundancy in the information required from the customers in order for them to buy tickets, create user accounts etc. o To check the validity of input data and give a feedback to the user in case of errors or inconsistency. o To provide flexible access modes to users - internet, telephone, PDA. o To protect customers’ privacy concerns. o To make it easy for travelers to check the ticket status or make changes to their trip.

5

PIA RESERVATION SYSTEM

FEASIBILITY REPORT Date: 10 November 2003 To: Pakistan international airline From: Mamoona Afzal Kiran Mohsin Subject: feasibility assessment for project of PIA Scope / requirement: the new system will: The database should support large no of records at least in capacity of Giga Bytes. It should be secure from un-authorized access. SOFTWARE APPLICATION PROGRAMS: Database: Front End Tool: Repot:

MS ACCESS VB.NET Seagate Crystal Report

PROPOSED SOLUTION: The Solution proposed for development of project will go through a series of steps:  Database will be designed that will later populated with data.  Database will be handled using Ms Access.  All records will be later extract from populated database and linked with the VB.NET forms.  Ongoing support will be provided from time to time.

TYPES OF FEASIBILITY REPORT We have defined the feasibility and determined when to perform a feasibility analysis. Most analysts have agreed that three categories of feasibility test: those three tests, which we apply at an analysis of the institute. They are as under:

1. 2. 3.

OPERATIONAL FEASIBILITY TECHNICAL FEASIBILITY ECONOMIC FEASIBILITY

6

PIA RESERVATION SYSTEM

1. OPERATINAL FEASIBILITY Operational feasibility is a measure of how well the solution of problems or a specific ALTERNATIVE SOULSTION will work in the institute. It is also a measure of how people feel about system.

2. TECHNICAL FEASIBILITY Technical feasibility is a measure of the practically of a specific technical solution and of the availability of technical resources. It is also a measure of schedule feasibility, if deadline are established.

3. ECONOMIC FEASIBILITY Economic feasibility is a measure of the cost –effectiveness of a project or solution (thesis often called a cost- benefit analysis). The bottom line in many projects is economic feasibility. During the early phase of the PROJECT, economic feasibility analysis amounts to line more than judging whether the possible benefits of solving the problem are worthwhile. Costs are practically impossible to estimate have not been identified. However, as soon as specific requirements and solution have been identified. The analyst can weight the costs and benefits of each alter.

7

PIA RESERVATION SYSTEM

CHAPTER # 2

EXISTING SYSTEM ANALYSIS

Detail Study of Existing System  Drawbacks in Existing System  Main Analysis Diagram (s) 

8

PIA RESERVATION SYSTEM

EXISTING SYSTEM ANALYSIS ANALYSIS Analysis is the key to success of any kind of system development. It is very important to first grasp the domain knowledge and then study the area to which the project belongs. It is only then one can clearly identify the requirements of the system

FACT FINDING TECHNIQUES In analysis phase there are different fact finding techniques which help us to find the right way to do develop any project.

1. Interview Interviews are an important fact-finding technique and help in determining the mood of the employees of any organization. An interview is a planned meeting during which information from the employees is gathered, and the interviewer should be a skilled person having all the know how of planning, conducting and documenting the interviews properly. In our analysis of the current system interview was very vital for gathering the necessary information because there are many hidden aspects of the system that need to be extracted from the top management and this can only be achieved through personal meeting in the form of interviews.

2. Questionnaire It is a commendable approach in terms of target of audience. It enables large number of participants, from various departments to even various countries, to be involved in systems investigation. With standardized questions and assurance of anonymity, the facts gathered tend to be more reliable and often more honest responses. In our analysis of the current system, questionnaire was a great help in determining the general trend of doing things in the company and to find the core functionality of the different subsystems.

3. Survey Survey is a good tool in finding out about the system through personally knowing how the system is working and what are the real problems that exist within the system and its subsystems. We explain above three different fact finding techniques but we used questionnaire and interviews in this project.

9

PIA RESERVATION SYSTEM

QUESTIONNAIRES FOR AIRLINE RESERVATION SYSTEM 1.Customer 1.Customer ask what when he talk to u first time. It depends on the customer’s requirements. He/she would ask about reservation or to buy a ticket. 2.If 2.If Customer asks about Domestic flight… what are the requirements? PIA required nothing, but sometimes a NID (National Identity) card from customer for his/her domestic traveling. 3.If 3.If Customer asks about International flight… what are the requirements? PIA required valid Passport, visa and sometimes health documents from customer for his/her International traveling. 4.What 4.What is the difference between Booking & Reservation? There is no difference between Booking & Reservation. 5.How How Customer reserves his/her seat. seat. Customer can reserve his/her seat by calling, and at the spot in office. But now a day’s customer has facility to reserve his/her seat using internet (website). 6.What 6.What does u do on your side? Duty officer (employee) just checks the customer requirements and fulfills them if possible. 7.After 7.After that what you tell to the Customer? Duty officer tells him what other possible ways. 8.What 8.What things are possible to happen, from buying the ticket to his departure? Customer can cancel, postpone or re-schedule his/her seat. And flight can also be delayed due to some problems. 9.What 9.What things can be modify, after when the Customer have bought a ticket. Customer can re-schedule, cancel, and block his /her seat. 10.With 10.With out paying, Can a customer reserve his seat… if yes… what are the ways… Yes, with certain time limit to buy ticket.

10

PIA RESERVATION SYSTEM

11.If 11.If a customer have bought the ticket, but he is not interesting to go… how much amount you charge… (%) It varies from time period to time period… 12.In 12.In what cases discount can be given on. For Groups (journalists), for Students (students can get discount in both cases, Domestic or International but in International they should have study visa). 13.How 13.How the ticket can Auto-Cancel. After the expiry of time limit, the system will cancel the reservation. 14.What 14.What is PNR? Passenger Name Record 15.What 15.What is APIS? (Advance Passenger Information System) PIA is a signatory to APIS and accordingly is liable to electronically transmit all passengers and crew data to US bound flights. 16.What 16.What is Pre-Reserved Seats? Pre-Reserve facility is available on all International and Domestic flights. 17.What 17.What is Advance Boarding Facility at Check-in Counters? Check-In Counters available at PIA booking offices at KHI, LHE, ISB, RWP, LYP, MUX, UET and PEW. The facility is only available to passengers traveling on Domestic flights without checked baggage. 18.How 18.How Customer asks u about his desired route, and then what do u does there. He just places his requirements, which always varies from customer to customer. And on our side we just tell him the possible routs which PIA is offering. 19.How 19.How and why you store your desired data/information. All the data is saved in head office, which called Purge Record. Head Office is in TURSA. 20. What are your Bus1iness Rules? Business Rules are listed below in details.

11

PIA RESERVATION SYSTEM

INTERVIEWS Interviewer Name:

MAMOONA, KIRAN

Interviewee Name:

MEERZA

Designation:

Local Training Co-coordinator

Place:

PIA Office of Marketing

Date:

10/09/2003

Duration:

2 hours

1. What is the procedure for booking seat for the customer? PIA has a sales department, which runs many offices through out the country to serve its customers. The customers visit these offices to inquire about the products that the company offers, from the sales representatives. After gathering enough information and negotiating with the representative, the customer places the order that goes to directly to the sales department for processing. 2. How is a particular order processed? The sales department receives the orders from its different sales representatives in traveling agencies, or directly through the customer. Once these orders are received, the sales dept. checks with the inventory department whether the organization can honor the deal or not, and in what time period. After getting clearance from the inventory personnel, the PIA employee or Travel agent starts negotiating with the customer about the deal and a file are created for that order containing the details about customer and the trip, and a confirmation no. is assigned to the customer. 3. What is the procedure of filing the records for a trip? The organization has a standard procedure for filing the records for a trip. After the deal has been negotiated with the customer and the details are finalized, the sales staff sorts out all the necessary records. A typical kind of sales file contains the confirmation number, details about the trip plan, the prices, mode of payment the different dates set for the order completion, the quantities required etc. 4. What are the standards and norms that are being followed in a seat reservation processing? The organization maintains certain standards for all the processes that take place within its different departments. The sales department being a part of this scenario has to work under these guidelines, and has set specific priorities while processing the orders.

12

PIA RESERVATION SYSTEM

They give special treatments to all the clients having high rank in the organizations grading, and all the trips originating. The sales department demands its entire customer a minimum processing time of two (2) weeks and accepts any replacement requests before the passing of 48 hours from the departure time. 5. What is the procedure of manually maintaining your system? There is not much maintenance required for a manual system. The only maintainable part is the filing of records in registers. These registers are stored at safe locations, so that they remain protected from being destroyed or damaged, under different unfavorable circumstances. A regular staff has been hired for the maintenance and safety of these registers at the storage location. The storage location may be rooms or fullfledged buildings, having the necessary equipment and lodging. 6. What is the yearly cost of maintaining the system? Rs. 0.5 Million. 7. Nowadays every company is thinking about computerizing its system. What do you think about computerizing your system? Computer is a good tool for resource management and it indeed will help the company in many ways. The company is facing quite a many problems in its everyday working, due to human errors. The company has to spend a lot on human resources and office work; still newer problems arise every fortnight. These problems are going to increase more, if the scope of the system increases, as the management plans for expansions and upgrades, due to a higher percentage of errors per employee. The computer based system, as being envisaged does not have so many error the number of bugs, if any, remains the same whatever the size of the organization. Moreover, it gives the management better control over the company affairs and resource management. 8. What are your company’s future expansion plans? Currently organization has many expansion plans, which include production increase its routs to other countries. To achieve this, the organization intends to open new offices or increase its staff and has allocated huge amounts of money to make the computer system more productive. 9. How many hours of on site monitoring do you perform? The manager performs two hours of monitoring each day, by visiting the work area him/herself. During the monitoring the manager checks the different daily reports, analyze them and issue related flights. He she then verifies that the work is being carried out in accordance with the quality standards that are followed by the organization. The manager also check that the working conditions are well enough in the office and then if the building needs physical repairs.

13

PIA RESERVATION SYSTEM

10. What information regarding a reservation do you share with other departments? The sales department has quite a lot of information to share with other departments of the organization. When a seat is booked with the reservation department, they send a copy of that reservation to the inventory department, to determine if the organization is able to honor its deal with the customer, and at what date. The inventory department in turn shares information about its available resources with the sales people. 11. How is the information shared with other departments? All the departments have receiving clerks who receive all the information coming from other departments in the form of files. It is their duty to collect these files and forward them to there respective locations. They also interact with the receiving clerks of the other departments. 12. What is the procedure of recovery in case of data loss? Since the manual file based system has no backups, any damage to the files will cost the company all its data. 13. What is the payment methodology? Currently, the payments for all the transactions are made through checks and the reservation department accept any returns in cash. More recently the new system of credit card payments has been launched, and has received an overwhelming response from the customers.

DETAIL STUDY OF EXISTING SYSTEM From the questionnaire we obtain the following information about the existing system. CURRENT BUSINESS ACTIVITIES ABOUT RESERVATION In this system the whole procedure consists on two sides, one is customer (passenger) and another is employee. Customer may need some information about availability of seats, reservation, blocking, confirmation, rescheduling, cancellation and base price.

Checking Availability of Seats Duty officer ask the customer to tell the following details - class, one-way or round trip, departure date and the number of adult passengers, children and senior citizens. ‘Class’ refers to business class, first class, club class, smoking, non smoking. This choice made by the customer. The customer will get the choice of one-way, round trip. Departure date refers to either a single date or a range of dates. Duty officer will not tell to the customer,

14

PIA RESERVATION SYSTEM dates in the past or those dates that are too beyond in the future (as determined by the PIA policy). In case, the trip is a round trip, the duty officer also asks the customer to tell the departure date on the return trip. Having taken all the above information from the customer, the duty officer checks for wrong information. In case of any incompatibility, the duty officer informs the customer. Having taken all the information as listed above, the duty officer check the flight schedule in the response about the request provided by the customer. The duty officer provide information to the customer - for each flight number - the flight number, departure time in origin city, arrival time in destination city, the duration of the flight and the number of seats available on that flight.

Reservation Having taken all the information from customer, the duty officer proceeds to update the reservation database. It decrement the number of available seats on the particular flight for the particular class by the number of travelers being represented by the customer. The duty officer now tells the price of the ticket. This will be the sum of the prices for all the members of the travel party being represented by the customer. If customer buys the ticket, the duty officer charges the price of the ticket. System simultaneously generates a confirmation number. The ticket has been reserved.

Blocking Blocking is the process to refer to the temporary holding of a seat(s) on a flight for a specific period of time. The customer pays no cost for blocking a ticket, but must make a decision at least two week earlier to the date of departure.

Confirmation A customer who has earlier blocked a ticket, he is required either to confirm the ticket before two weeks of the departure date or the ticket stands cancelled. If customer make the ticket confirm, the duty officer issue him a confirmation number/letter.

Re-Scheduling This process means that the customer is allowed only to postpone the travel date and he has to pay the difference in fare. No other details can be changed through this process. For example the number of passengers can’t be changed. The duty officer makes a new confirmation number and issues it to the customer.

15

PIA RESERVATION SYSTEM

Cancellation The customers also have a choice to cancel the confirmed ticket or a blocked ticket. The duty officer also informs to customer any rules regarding the cancellation of tickets, what percentage of the price will be refunded.

Base Price This refers to the maximum price of a ticket, which usually is the price when the purchase is made at the last minute. This is used in arriving at the discounted price which depends on various factors like early booking etc.

Route The customers also have a choice to chose their desired routes if PIA has the facility of that particular route. Customer can ask about the longest possible route but in economical fare. Customer can ask about shortest possible route but may be he would have to pay more fare than normal. Customer can ask about neither too long nor short which would be PIA’s regular flights of that particular destination. After the origin and destination city’s airports are determined and assigned a code, the Duty officer now accesses the flight schedule and checks if there is a direct operational service between the two cities. If not, the Duty officer suggests possible routes and transfer points. The customer now presented with a choice of either selecting one of the routes.

BUSINESS RULES For Domestic Passengers: 1For reservation Flight, Date & section is required. 2Groups (journalist) may have discount if and only if they are more than 20 persons. 3Students may have 30% discount. 4After the expiry of time, the System will cancel the reservation. 5If passenger cancels his ticket before 18 hours of departure time, then 25% will be deducted and if passenger cancels his ticket before less than 18 hours from departure time, then 50% amount will be deducted. 6All passengers booked on Domestic Flights should be ticketed within 30 days of

16

PIA RESERVATION SYSTEM PNR (Passenger Name Record) creation or 3 days prior to departure which ever is earlier. 7Tickets can be booked maximum 1 year earlier.

For International Passengers: 1For reservation Passport and Valid Visa is required. 2Groups (journalists etc.) may have discount if they are more than 20 persons. 3Students may have 20% discount if they have student visa and confirmation letter from university where they are going to study. 4Customers have a choice to choose his/her desired routes. 5If a passenger cancels his ticket there will be nothing deducted in low season (April to November) but in high season (December to March) $50 would be deducted in some cases. 6All passengers booked on International Flights must be ticketed within 30 days of PNR (Passenger Name Record) creation or 14 days prior to departure, which ever is earlier. 7Established Fares 8Direct Fares o No stay between Departure and Arrival. 9 Through Fares (Rout Fares) o There are Stays between Departure and Arrival; passengers are not allowed to get out from plane during that stay time.

DRAW BACKS IN EXISTING SYSTEM 1.More Runtime Cost The current system does not cost much during establishment but the running time costs are very high. The time is wasted by extra load of work in the maintenance of the current system also since it is semi computerized and not online.

2.Data Redundancy The current system is based on files and several redundant files exist at many different locations for different departments because computer is not provided to every employee. The same data is stored at different localities which causes space and time loss. There is no need for duplication of data for any organization. The PIA wastes time and money on data redundancies.

17

PIA RESERVATION SYSTEM

3.Data Integrity The redundancies of files create problems for the employees of PIA to change the records for some files located at different places. This creates difficulties in the flow of data and the output of information is almost negligible and incorrect.

4.Searching is Slow / Difficult To search data from files and registers is always slow and just a wastage of time and space. The chances of errors are high.

5.No Online Facilities for customers There is no online facility for the customers of PIA. There is no such system by which customers can place on-line orders. Therefore the old system does not provide any attractive facility to the customer (passengers) of other cities or countries.

6.Searching of Data is Slow One can imagine how difficult it is to search data manually from registers and papers. PIA current system is totally based on registers. If one has to search data, he has to go through files of record written down in registers. Therefore, it is just wastage of time and manpower.

7.No Backup The current system has no backups available for the PIA because there is no procedure of backup of important data as current system itself is based on files which take too much time and working space and makes it impossible to recover data in case of data loss or damage.

8.More Human Resources Required To handle the current system, the PIA requires more human resources for every department and service areas. This cost much for PIA since more people are hired for different purposes. Hence, the PIA has to pay much for hiring more employees.

18

PIA RESERVATION SYSTEM

9.More Chances of Errors The chances of errors and problems increase for PIA current system, in the form of disinformation being delivered. This may even cause greater harm to the PIA due to wrong planning and disinformation.

10. Difficult Error Correction Any minor or major errors are not easily handled and fixed in the current system. Sometimes it gets hectic and chaotic for the staff or employee to fix the errors. It requires extra working hours and time that results in customer dissatisfaction. 11. More Chances of Data Loss

The current system of PIA is file based. Any calamity can destroy the data and no recovery of data lost, halting the complete operation of the PIA.

12. More Physical Space Required To store the registers / files in the current system, the PIA needs more storage place. The staffs needs extra work to run the old system and it requires too much physical space and results in large storage and office buildings, making the whole system overburdened and overstrained.

19

PIA RESERVATION SYSTEM

PROCESS DIAGRAM FOR PIA RESERVATION SYSTEM

Marketing

Customer

Browse Forms

Order Process

Category Browsing

Receipt

Payment

Block Flight

Shipment Handling Charge

Check Available Seats

Check Out

20

PIA RESERVATION SYSTEM

MAIN SYSTEM DIAGRAM LEVEL-0 DFD

Customer

Request to Reserve

Seat Block

Seat

AIR RESERVATION SYSTEM

Check Seats

Available Seats Information

Employee

21

PIA RESERVATION SYSTEM

Employee Blocking

Customer Issue

Information Block Notification

Request for Block Seat

Blocking 1.0

Request for

Block Seat

Confirmation 3.0

Cancel Seat

Cancellation 6.0

Base Price 4.0 Available Seats for Information

Check Available Seats 2.0

Available Seats for Information

Add Confirmed Seat Information

Block Seat for Customer

Conformed Seats Information

Reservation

Change Date

DB

Balance 7.0

Rescheduling

5.0 Rescheduling

Check Return Mileage Money

Cancel Information

Available Seats for Information

Money

Next Flight Information

Customer Price Information

Request to cancel

22

PIA RESERVATION SYSTEM

CHAPTER # 3

   

PROPOSED SYSTEM

Objectives System Proposal Main System Diagram Benefits /Main Features of Proposed System

23

PIA RESERVATION SYSTEM

OBJECTIVES OF THE PROPOSED SYSTEM • IMPROVED SERVICES An objective of the proposed system is to improve the existing System’s services, in order to:   

Increase customer satisfaction Provide the quality Create a controlled information management Environment

• BETTER PERFORMANCE To provide better performance is also an objective of our proposed system. Better performance will be managed by providing    

Desired flexibility Fast response Ability to support changes. Ability to maintain the quality of services.

• EFFICIENT GUI One of the objectives of the proposed system is to provide a user friendly GUI, that will enable the user to work on clicks and make the information transfer possible with the most common I/O devices.

• MORE INFORMATION An objective of our proposed system is to develop a system that will eliminate the problem of insufficient and incomplete information.

• DECISION SUPPORT By providing the facility of what-if analysis, we will make a decision support system.

24

PIA RESERVATION SYSTEM

• STRONGER CONTROLS The proposed system will have stronger controls. Controls like passwords, various levels of user access and option will be added.

• ELIMINATION OF RUNNING COST We are going to develop the proposed system with an objective to eliminate the running cost by overcoming the continuous stationary expenses, manual storage need, and extra staff in the information resource department of PIA.

SYSTEM PROPOSAL PAKISTAN INTERNATIONAL AIRLINE (PIA) Lahore.

SUBJECT: SYSTEM PROPOSAL This refers to the concern regarding the above captioned subject. We specify this proposal for PIA Lahore.

SCOPE OF THE PROJECT The scope of the work shall be as below:  Reservation System Analysis  Design  Development  System implementation  System testing & evaluation  User guide

25

PIA RESERVATION SYSTEM

TIME SCHEDULE Index

Activity 1

2

Time

Engineering: a) Analysis b) Design Construction & Release: a) Development b) Testing & Implementation c) User Documentation

Overall:

2 2

weeks weeks

3-4 weeks 2 weeks 2 weeks

11-12 weeks

SYSTEM MAINTENANCE In order to keep the software updated (modified) and to avoid any problems due to computer viruses, power failures and system crashes we offer our services for maintaining the software.

SYSTEM HARDWARE The recommended system hardware for your system to run efficiently and smoothly should be  Pentium P-III 700 MHz or above CPU with 64 MB or above RAM  HP Laser Jet 1100 or wide carriage 132 column Epson LQ-2170  Windows XP OR NT Plate form. Yours’ Sincerely

Mamoona Afzal (BCS-AIOU) Kiran Mohsin (BCS-AIOU)

26

PIA RESERVATION SYSTEM

MAIN SYSTEM DIAGRAM (PROPOSED)

User

Flight Information

Flight Schedule 1.0

Issue Time Request for Reserve Seat

Check Available Seats 2.0

Available Seats for Information Request for Confirm Seat

Confirmation 3.0 Add Confirmed Seat Information

Available Seats for Information

Reserved Seat Information

Conformed Seats Information

Reservation DB

Change Date

Rescheduling

4.0

Rescheduling Cancel Seat

User

Cancellation 5.0

Next Flight Information

Cancel Information Request to cancel

27

PIA RESERVATION SYSTEM

BENEFITS/MAIN FEATURES OF THE PROPOSED SYSTEM Proposed system will provide following benefits: Due to the above-mentioned facility, system will produce comparatively low expenses and causes fast response time. 1- Proposed system will provide comprehensive user help. 2- In proposed system airline reservation ‘integrated’. Hence it will cause decrease in running cost. 3- Proposed system will give facts & figures in percentage. So this proposed system will provide the reports in a better and more understandable way. 4- Proposed system will generate the graphical representation 5- Proposed system will provide the batter searching facilities. 6- A special benefit of proposed system is user-friendliness. 7- Robust screens will allow user to easily communicate with the system. 8- Proposed system is likely to generate several types of reports that will help in decision-making. 9- It will help the company to reduce the costs in present and also in the future. 10- In proposed system, there is a facility of backup data (using Back-up and Recovery Manager) for the employee pay records. Therefore the durability of the data increases as the data can be Stored on another hardware device (i.e.: tape drive or zip drive) and data is not lost due to hardware problems. 11- The proposed system gives much more security in terms of data by providing administrator-level security and user access control with username and password . Hence no one having, mischievous can easy access the employee records.

28

PIA RESERVATION SYSTEM

CHAPTER # 4

SYSTEM DESIGN

Input Design  Output Design  Code Design  User Interface Design 

29

PIA RESERVATION SYSTEM

INPUT DESIGN Input Design of the system is as follow:

INPUT MEDIA AND DATA ENTRY METHOD In this regard we have selected:  Keyboard and mouse as input media (however system can fully be handled only through keyboard).  Direct entry as the data entry method.

30

PIA RESERVATION SYSTEM

31

PIA RESERVATION SYSTEM

32

PIA RESERVATION SYSTEM

SAMPLE CODE

Dim frm1 As New frmlogin () Dim frm10 As New cancelseat () Dim st As String st = "provider=microsoft.jet.oledb.4.0;password='';user source='d:\finalproject\dbf\pia.mdb'" Try dbcon.ConnectionString = st dbcon.Open () cmd.Connection = dbcon cmd1.Connection = dbcon Catch ex As Exception MsgBox (ex.ToString) End Try Frm1.ShowDialog ()

id=admin;data

End Sub END MODULE Public Class frmmain Inherits System.Windows.Forms.Form #Region " Windows Form Designer generated code " Public Sub New() MyBase.New() 'This call is required by the Windows Form Designer. InitializeComponent() 'Add any initialization after the InitializeComponent() call End Sub 'Form overrides dispose to clean up the component list. Protected Overloads Overrides Sub Dispose (By Val disposing As Boolean) If disposing Then If Not (components Is Nothing) Then components.Dispose () End If End If MyBase.Dispose (disposing) End Sub 'Required by the Windows Form Designer Private components As System.ComponentModel.IContainer 'NOTE: The following procedure is required by the Windows Form Designer 'It can be modified using the Windows Form Designer. 'Do not modify it using the code editor. Friend WithEvents MainMenu1 As System.Windows.Forms.MainMenu

33

PIA RESERVATION SYSTEM Friend WithEvents MenuItem1 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem2 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem3 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem4 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem5 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem6 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem7 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem8 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem9 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem10 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem11 As Syqtem.Windows.Forms.MenuItem Friend WithEvents MenuItem12 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem13 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem14 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem15 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem16 As System.Windows.Forms.MenuItem Friend WithEvents MenuItem17 As System.Windows.Forms.MenuItem <System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent() Dim resources As System.Resources.ResourceManager = New System.Resources.ResourceManager(GetType(frmmain)) Me.MainMenu1 = New System.Windows.Forms.MainMenu() Me.MenuItem1 = New System.Windows.Forms.MenuItem() Me.MenuItem2 = New System.Windows.Forms.MenuItem() Me.MenuItem3 = New System.Windows.Forms.MenuItem() Me.MenuItem4 = New System.Windows.Forms.MenuItem() Me.MenuItem5 = New System.Windows.Forms.MenuItem() Me.MenuItem17 = New System.Windows.Forms.MenuItem() Me.MenuItem6 = New System.Windows.Forms.MenuItem() Me.MenuItem7 = New System.Windows.Forms.MenuItem() Me.MenuItem8 = New System.Windows.Forms.MenuItem() Me.MenuItem9 = New System.Windows.Forms.MenuItem() Me.MenuItem10 = New System.Windows.Forms.MenuItem() Me.MenuItem11 = New System.Windows.Forms.MenuItem() Me.MenuItem12 = New System.Windows.Forms.MenuItem() Me.MenuItem13 = New System.Windows.Forms.MenuItem() Me.MenuItem14 = New System.Windows.Forms.MenuItem() Me.MenuItem15 = New System.Windows.Forms.MenuItem() Me.MenuItem16 = New System.Windows.Forms.MenuItem() ' 'MainMenu1 ' Me.MainMenu1.MenuItems.AddRange(New System.Windows.Forms.MenuItem() {Me.MenuItem1, Me.MenuItem6, Me.MenuItem11, Me.MenuItem15, Me.MenuItem16}) ' 'MenuItem1 ' Me.MenuItem1.Index = 0 Me.MenuItem1.MenuItems.AddRange(New System.Windows.Forms.MenuItem() {Me.MenuItem2, Me.MenuItem3, Me.MenuItem4, Me.MenuItem5, Me.MenuItem17}) Me.MenuItem1.Text = "Main" ' 'MenuItem2 ' Me.MenuItem2.Index = 0 Me.MenuItem2.Text = "Plane Information" '

34

PIA RESERVATION SYSTEM 'MenuItem3 ' Me.MenuItem3.Index = 1 Me.MenuItem3.Text = "Flight Schedule" ' 'MenuItem4 ' Me.MenuItem4.Index = 2 Me.MenuItem4.Text = "Add Reservation" ' 'MenuItem5 ' Me.MenuItem5.Index = 3 Me.MenuItem5.Text = "Passenger Information" ' 'MenuItem17 ' Me.MenuItem17.Index = 4 Me.MenuItem17.Text = "Cancel Reservation" ' 'MenuItem6 ' Me.MenuItem6.Index = 1 Me.MenuItem6.MenuItems.AddRange(New System.Windows.Forms.MenuItem() {Me.MenuItem7, Me.MenuItem8, Me.MenuItem9, Me.MenuItem10}) Me.MenuItem6.Text = "Reports" ' 'MenuItem7 ' Me.MenuItem7.Index = 0 Me.MenuItem7.Text = "Plane" ' 'MenuItem8 ' Me.MenuItem8.Index = 1 Me.MenuItem8.Text = "Flight Schedule" ' 'MenuItem9 ' Me.MenuItem9.Index = 2 Me.MenuItem9.Text = "Reservation" ' 'MenuItem10 ' Me.MenuItem10.Index = 3 Me.MenuItem10.Text = "Passenger" ' 'MenuItem11 ' Me.MenuItem11.Index = 2 Me.MenuItem11.MenuItems.AddRange(New System.Windows.Forms.MenuItem() {Me.MenuItem12, Me.MenuItem13, Me.MenuItem14}) Me.MenuItem11.Text = "Utilities" ' 'MenuItem12 '

35

PIA RESERVATION SYSTEM Me.MenuItem12.Index = 0 Me.MenuItem12.Text = "Login" ' 'MenuItem13 ' Me.MenuItem13.Index = 1 Me.MenuItem13.Text = "New User" ' 'MenuItem14 ' Me.MenuItem14.Index = 2 Me.MenuItem14.Text = "About- Credits" ' 'MenuItem15 ' Me.MenuItem15.Index = 3 Me.MenuItem15.Text = "Help" ' 'MenuItem16 ' Me.MenuItem16.Index = 4 Me.MenuItem16.Text = "Exit" ' 'frmmain ' Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13) Me.BackColor = System.Drawing.Color.Honeydew Me.ClientSize = New System.Drawing.Size(760, 446) Me.Icon = CType(resources.GetObject("$this.Icon"), System.Drawing.Icon) Me.MaximizeBox = False Me.Menu = Me.MainMenu1 Me.MinimizeBox = False Me.Name = "frmmain" Me.StartPosition = System.Windows.Forms.FormStartPosition.CenterScreen Me.Text = "PIA Reservation System" Me.WindowState = System.Windows.Forms.FormWindowState.Maximized End Sub #End Region

Private Sub MenuItem2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem2.Click Dim frm1 As New frmplaneinfo() frm1.ShowDialog() End Sub Private Sub MenuItem7_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem7.Click Dim frmrpt As New frmrpt1() frmrpt.Show() End Sub

36

PIA RESERVATION SYSTEM Private Sub MenuItem16_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem16.Click Me.Close() End Sub Private Sub MenuItem3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem3.Click Dim frm2 As New frmsch() frm2.Show() End Sub Private Sub MenuItem4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem4.Click Dim frm3 As New Profile() frm3.ShowDialog() End Sub Private Sub MenuItem8_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem8.Click Dim frmrpt1 As New flschedrpt() frmrpt1.ShowDialog() End Sub Private Sub MenuItem5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem5.Click Dim frm4 As New frmshps() frm4.ShowDialog() End Sub Private Sub MenuItem12_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem12.Click Dim frm5 As New frmlogin() frm5.ShowDialog() End Sub Private Sub MenuItem14_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem14.Click Dim frm7 As New frmcredit() frm7.ShowDialog() End Sub Private Sub MenuItem13_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem13.Click Dim frm6 As New frmuser() frm6.ShowDialog() End Sub

37

PIA RESERVATION SYSTEM Private Sub MenuItem17_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem17.Click Dim frm7 As New cancelseat() frm7.ShowDialog() End Sub Private Sub MenuItem10_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem10.Click Dim frm8 As New passinforpt() frm8.ShowDialog() End Sub Private Sub MenuItem9_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MenuItem9.Click Dim frmrpt2 As New frmreserrpt() frmrpt2.ShowDialog() End Sub End Class Imports sds = System.Data.OleDb Public Class frmplaneinfo Inherits System.Windows.Forms.Form #Region " Windows Form Designer generated code " Public Sub New() MyBase.New() 'This call is required by the Windows Form Designer. InitializeComponent() 'Add any initialization after the InitializeComponent() call End Sub 'Form overrides dispose to clean up the component list. Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean) If disposing Then If Not (components Is Nothing) Then components.Dispose() End If End If MyBase.Dispose(disposing) End Sub 'Required by the Windows Form Designer Private components As System.ComponentModel.IContainer 'NOTE: The following procedure is required by the Windows Form Designer 'It can be modified using the Windows Form Designer. 'Do not modify it using the code editor. Friend WithEvents Label6 As System.Windows.Forms.Label

38

PIA RESERVATION SYSTEM Friend WithEvents PictureBox2 As System.Windows.Forms.PictureBox Friend WithEvents PictureBox1 As System.Windows.Forms.PictureBox Friend WithEvents Label2 As System.Windows.Forms.Label Friend WithEvents Label3 As System.Windows.Forms.Label Friend WithEvents Label4 As System.Windows.Forms.Label Friend WithEvents btnnew As System.Windows.Forms.Button Friend WithEvents btnsave As System.Windows.Forms.Button Friend WithEvents txtflno As System.Windows.Forms.TextBox Friend WithEvents txtpname As System.Windows.Forms.TextBox Friend WithEvents txtsc As System.Windows.Forms.TextBox Friend WithEvents btnsear As System.Windows.Forms.Button Friend WithEvents btnup As System.Windows.Forms.Button Friend WithEvents txtpnam1 As System.Windows.Forms.TextBox Friend WithEvents btndel As System.Windows.Forms.Button Friend WithEvents txtpnam2 As System.Windows.Forms.TextBox Friend WithEvents txtpnam3 As System.Windows.Forms.TextBox Friend WithEvents btnref As System.Windows.Forms.Button Friend WithEvents btndisp As System.Windows.Forms.Button Friend WithEvents Label1 As System.Windows.Forms.Label <System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent() Dim resources As System.Resources.ResourceManager = New System.Resources.ResourceManager(GetType(frmplaneinfo)) Me.Label6 = New System.Windows.Forms.Label() Me.PictureBox2 = New System.Windows.Forms.PictureBox() Me.PictureBox1 = New System.Windows.Forms.PictureBox() Me.Label2 = New System.Windows.Forms.Label() Me.Label3 = New System.Windows.Forms.Label() Me.Label4 = New System.Windows.Forms.Label() Me.txtflno = New System.Windows.Forms.TextBox() Me.txtpname = New System.Windows.Forms.TextBox() Me.txtsc = New System.Windows.Forms.TextBox() Me.btnsave = New System.Windows.Forms.Button() Me.btnnew = New System.Windows.Forms.Button() Me.btndel = New System.Windows.Forms.Button() Me.btnsear = New System.Windows.Forms.Button() Me.btnup = New System.Windows.Forms.Button() Me.txtpnam1 = New System.Windows.Forms.TextBox() Me.txtpnam2 = New System.Windows.Forms.TextBox() Me.txtpnam3 = New System.Windows.Forms.TextBox() Me.btnref = New System.Windows.Forms.Button() Me.btndisp = New System.Windows.Forms.Button() Me.Label1 = New System.Windows.Forms.Label() Me.SuspendLayout() ' 'Label6 ' Me.Label6.BackColor = System.Drawing.Color.SeaGreen Me.Label6.Location = New System.Drawing.Point(0, -8) Me.Label6.Name = "Label6" Me.Label6.Size = New System.Drawing.Size(680, 96) Me.Label6.TabIndex = 15 ' 'PictureBox2 ' Me.PictureBox2.Image = CType(resources.GetObject("PictureBox2.Image"), System.Drawing.Bitmap)

39

PIA RESERVATION SYSTEM Me.PictureBox2.Name = "PictureBox2" Me.PictureBox2.Size = New System.Drawing.Size(224, 88) Me.PictureBox2.TabIndex = 17 Me.PictureBox2.TabStop = False ' 'PictureBox1 ' Me.PictureBox1.BackColor = System.Drawing.Color.SeaGreen Me.PictureBox1.Image = CType(resources.GetObject("PictureBox1.Image"), System.Drawing.Bitmap) Me.PictureBox1.Location = New System.Drawing.Point(224, -24) Me.PictureBox1.Name = "PictureBox1" Me.PictureBox1.Size = New System.Drawing.Size(200, 112) Me.PictureBox1.TabIndex = 18 Me.PictureBox1.TabStop = False ' 'Label2 ' Me.Label2.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label2.Location = New System.Drawing.Point(120, 280) Me.Label2.Name = "Label2" Me.Label2.Size = New System.Drawing.Size(104, 24) Me.Label2.TabIndex = 20 Me.Label2.Text = "Flight Number" ' 'Label3 ' Me.Label3.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label3.Location = New System.Drawing.Point(120, 248) Me.Label3.Name = "Label3" Me.Label3.Size = New System.Drawing.Size(104, 24) Me.Label3.TabIndex = 4 Me.Label3.Text = "Plane Name" ' 'Label4 ' Me.Label4.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label4.Location = New System.Drawing.Point(120, 312) Me.Label4.Name = "Label4" Me.Label4.Size = New System.Drawing.Size(120, 32) Me.Label4.TabIndex = 22 Me.Label4.Text = "Seaing Capacity:" ' 'txtflno ' Me.txtflno.BackColor = System.Drawing.SystemColors.HighlightText Me.txtflno.Location = New System.Drawing.Point(248, 280) Me.txtflno.Name = "txtflno" Me.txtflno.Size = New System.Drawing.Size(96, 20) Me.txtflno.TabIndex = 5 Me.txtflno.Text = "" ' 'txtpname

40

PIA RESERVATION SYSTEM ' Me.txtpname.BackColor = System.Drawing.SystemColors.HighlightText Me.txtpname.Location = New System.Drawing.Point(248, 248) Me.txtpname.Name = "txtpname" Me.txtpname.Size = New System.Drawing.Size(96, 20) Me.txtpname.TabIndex = 3 Me.txtpname.Text = "" ' 'txtsc ' Me.txtsc.Location = New System.Drawing.Point(248, 312) Me.txtsc.Name = "txtsc" Me.txtsc.Size = New System.Drawing.Size(96, 20) Me.txtsc.TabIndex = 6 Me.txtsc.Text = "" ' 'btnsave ' Me.btnsave.Image = CType(resources.GetObject("btnsave.Image"), System.Drawing.Bitmap) Me.btnsave.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btnsave.Location = New System.Drawing.Point(128, 144) Me.btnsave.Name = "btnsave" Me.btnsave.Size = New System.Drawing.Size(56, 56) Me.btnsave.TabIndex = 7 Me.btnsave.Text = "&Save" Me.btnsave.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'btnnew ' Me.btnnew.Image = CType(resources.GetObject("btnnew.Image"), System.Drawing.Bitmap) Me.btnnew.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btnnew.Location = New System.Drawing.Point(48, 144) Me.btnnew.Name = "btnnew" Me.btnnew.Size = New System.Drawing.Size(80, 56) Me.btnnew.TabIndex = 8 Me.btnnew.Text = "&New Plane" Me.btnnew.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'btndel ' Me.btndel.Image = CType(resources.GetObject("btndel.Image"), System.Drawing.Bitmap) Me.btndel.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btndel.Location = New System.Drawing.Point(304, 144) Me.btndel.Name = "btndel" Me.btndel.Size = New System.Drawing.Size(64, 56) Me.btndel.TabIndex = 65 Me.btndel.Text = "Delete" Me.btndel.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'btnsear ' Me.btnsear.Image = CType(resources.GetObject("btnsear.Image"), System.Drawing.Bitmap) Me.btnsear.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btnsear.Location = New System.Drawing.Point(248, 144) Me.btnsear.Name = "btnsear" Me.btnsear.Size = New System.Drawing.Size(56, 56)

41

PIA RESERVATION SYSTEM Me.btnsear.TabIndex = 64 Me.btnsear.Text = "Search" Me.btnsear.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'btnup ' Me.btnup.Image = CType(resources.GetObject("btnup.Image"), System.Drawing.Bitmap) Me.btnup.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btnup.Location = New System.Drawing.Point(368, 144) Me.btnup.Name = "btnup" Me.btnup.Size = New System.Drawing.Size(56, 56) Me.btnup.TabIndex = 63 Me.btnup.Text = "&Update" Me.btnup.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'txtpnam1 ' Me.txtpnam1.BackColor = System.Drawing.SystemColors.HighlightText Me.txtpnam1.Location = New System.Drawing.Point(248, 248) Me.txtpnam1.Name = "txtpnam1" Me.txtpnam1.Size = New System.Drawing.Size(96, 20) Me.txtpnam1.TabIndex = 66 Me.txtpnam1.Text = "" ' 'txtpnam2 ' Me.txtpnam2.BackColor = System.Drawing.SystemColors.HighlightText Me.txtpnam2.Location = New System.Drawing.Point(248, 248) Me.txtpnam2.Name = "txtpnam2" Me.txtpnam2.Size = New System.Drawing.Size(96, 20) Me.txtpnam2.TabIndex = 67 Me.txtpnam2.Text = "" ' 'txtpnam3 ' Me.txtpnam3.BackColor = System.Drawing.SystemColors.HighlightText Me.txtpnam3.Location = New System.Drawing.Point(248, 248) Me.txtpnam3.Name = "txtpnam3" Me.txtpnam3.Size = New System.Drawing.Size(96, 20) Me.txtpnam3.TabIndex = 68 Me.txtpnam3.Text = "" ' 'btnref ' Me.btnref.Image = CType(resources.GetObject("btnref.Image"), System.Drawing.Bitmap) Me.btnref.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btnref.Location = New System.Drawing.Point(368, 144) Me.btnref.Name = "btnref" Me.btnref.Size = New System.Drawing.Size(56, 56) Me.btnref.TabIndex = 69 Me.btnref.Text = "Refresh" Me.btnref.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'btndisp ' Me.btndisp.Image = CType(resources.GetObject("btndisp.Image"), System.Drawing.Bitmap)

42

PIA RESERVATION SYSTEM Me.btndisp.ImageAlign = System.Drawing.ContentAlignment.TopCenter Me.btndisp.Location = New System.Drawing.Point(184, 144) Me.btndisp.Name = "btndisp" Me.btndisp.Size = New System.Drawing.Size(64, 56) Me.btndisp.TabIndex = 70 Me.btndisp.Text = "Display" Me.btndisp.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'Label1 ' Me.Label1.Font = New System.Drawing.Font("Arial Black", 14.25!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label1.Location = New System.Drawing.Point(120, 104) Me.Label1.Name = "Label1" Me.Label1.Size = New System.Drawing.Size(208, 24) Me.Label1.TabIndex = 71 Me.Label1.Text = "Plane Information" Me.Label1.TextAlign = System.Drawing.ContentAlignment.MiddleCenter ' 'frmplaneinfo ' Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13) Me.BackColor = System.Drawing.Color.Honeydew Me.ClientSize = New System.Drawing.Size(472, 366) Me.Controls.AddRange(New System.Windows.Forms.Control() {Me.Label1, Me.btndisp, Me.btnref, Me.txtpnam3, Me.txtpnam2, Me.txtpnam1, Me.btndel, Me.btnsear, Me.btnup, Me.btnnew, Me.btnsave, Me.txtsc, Me.txtpname, Me.txtflno, Me.Label4, Me.Label3, Me.Label2, Me.PictureBox1, Me.PictureBox2, Me.Label6}) Me.Icon = CType(resources.GetObject("$this.Icon"), System.Drawing.Icon) Me.MaximizeBox = False Me.MinimizeBox = False Me.Name = "frmplaneinfo" Me.StartPosition = System.Windows.Forms.FormStartPosition.CenterScreen Me.Text = "Add Plane Information" Me.ResumeLayout(False) End Sub #End Region Dim dset As New DataSet() Dim sflag As Boolean = False Private Sub frmplaneinfo_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles MyBase.Load btnref.Visible = False txtpnam1.Visible = False txtpnam2.Visible = False txtpnam3.Visible = False txtpname.Enabled = False txtflno.Enabled = False txtsc.Enabled = False btnsave.Enabled = False End Sub

43

PIA RESERVATION SYSTEM Private Sub btnsave_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnsave.Click cmd.CommandText = "insert into planeinfo values ('" & txtpname.Text & "','" & txtflno.Text & "'," & Val(txtsc.Text) & "," & Val(txtsc.Text) & ")" Try cmd.ExecuteNonQuery() Catch ex As Exception MsgBox(ex.ToString) End Try btnsave.Enabled = True End Sub Private Sub btnnew_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnnew.Click txtpname.Enabled = True txtflno.Enabled = True txtsc.Enabled = True btnsave.Enabled = True txtpname.Focus() txtpname.Clear() txtflno.Clear() txtsc.Clear() End Sub Private Sub btnsear_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnsear.Click txtpnam3.Visible = False txtpname.Visible = False txtpnam2.Visible = False txtpnam1.Visible = True txtpnam1.Focus() txtpnam1.Clear() txtflno.Clear() txtsc.Clear() End Sub Private Sub txtpnam1_KeyDown(ByVal sender System.Windows.Forms.KeyEventArgs) Handles txtpnam1.KeyDown

As

Object,

ByVal

e

As

If e.KeyCode = Keys.Enter Then cmd.Connection = dbcon Dim Rd As sds.OleDbDataReader cmd.CommandText = "select * from planeinfo where planenm='" & txtpnam1.Text & "'" Try Rd = cmd.ExecuteReader If Rd.Read Then txtflno.Text = Rd(1) txtsc.Text = Rd(2) sflag = True Else sflag = False End If Catch Ex As Exception

44

PIA RESERVATION SYSTEM MsgBox(Ex.Message) Finally Rd.Close() Rd = Nothing End Try If sflag = False Then MsgBox("Plane Name Not Found ") End If End Sub

Private Sub txtpnam2_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles txtpnam2.TextChanged End Sub Private Sub txtpnam2_KeyDown(ByVal sender As Object, ByVal System.Windows.Forms.KeyEventArgs) Handles txtpnam2.KeyDown If e.KeyCode = Keys.Enter Then cmd.Connection = dbcon Dim Rd As sds.OleDbDataReader cmd.CommandText = "select * from planeinfo where planenm='" & txtpnam2.Text & "'" Try Rd = cmd.ExecuteReader If Rd.Read Then txtflno.Text = Rd(2) txtsc.Text = Rd(3) sflag = True

e

As

If MsgBox("Are You Sure", MsgBoxStyle.YesNo, "Delete") = MsgBoxResult.Yes Then Rd.Close() Rd = Nothing cmd.CommandText = "delete * from planeinfo where planenm='" & txtpnam2.Text & "'" Try cmd.ExecuteNonQuery() Catch ex As Exception MsgBox(ex.ToString) End Try Exit Sub End If Exit Sub Else sflag = False End If Catch Ex As Exception MsgBox(Ex.Message) Finally Try Rd.Close() Rd = Nothing Catch End Try End Try If sflag = False Then MsgBox("Plane Name Not Found ")

45

PIA RESERVATION SYSTEM End If End Sub Private Sub btndel_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btndel.Click txtpnam3.Visible = False txtpname.Visible = False txtpnam1.Visible = False txtpnam2.Visible = True txtpnam2.Clear() txtpnam2.Focus() End Sub Private Sub btnup_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnup.Click txtpname.Visible = False txtpnam1.Visible = False txtpnam2.Visible = False btnref.Visible = True btnup.Visible = False imports sds = System.Data.OleDb Public Class frmuser Inherits System.Windows.Forms.Form #Region " Windows Form Designer generated code " Public Sub New() MyBase.New() 'This call is required by the Windows Form Designer. InitializeComponent() 'Add any initialization after the InitializeComponent() call End Sub 'Form overrides dispose to clean up the component list. Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean) If disposing Then If Not (components Is Nothing) Then components.Dispose() End If End If MyBase.Dispose(disposing) End Sub 'Required by the Windows Form Designer Private components As System.ComponentModel.IContainer 'NOTE: The following procedure is required by the Windows Form Designer 'It can be modified using the Windows Form Designer. 'Do not modify it using the code editor.

46

PIA RESERVATION SYSTEM Friend WithEvents tbr1 As System.Windows.Forms.ToolBar Friend WithEvents btn1 As System.Windows.Forms.ToolBarButton Friend WithEvents ImageList1 As System.Windows.Forms.ImageList Friend WithEvents btn2 As System.Windows.Forms.ToolBarButton Friend WithEvents btn3 As System.Windows.Forms.ToolBarButton Friend WithEvents Label1 As System.Windows.Forms.Label Friend WithEvents txtuser As System.Windows.Forms.TextBox Friend WithEvents Label2 As System.Windows.Forms.Label Public WithEvents cmdpre As System.Windows.Forms.Button Public WithEvents cmdnext As System.Windows.Forms.Button Public WithEvents Label3 As System.Windows.Forms.Label Friend WithEvents txtpasw As System.Windows.Forms.TextBox Friend WithEvents txtcount As System.Windows.Forms.TextBox Friend WithEvents txtusr1 As System.Windows.Forms.TextBox <System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent() Me.components = New System.ComponentModel.Container() Dim resources As System.Resources.ResourceManager = New System.Resources.ResourceManager(GetType(frmuser)) Me.tbr1 = New System.Windows.Forms.ToolBar() Me.btn1 = New System.Windows.Forms.ToolBarButton() Me.btn2 = New System.Windows.Forms.ToolBarButton() Me.btn3 = New System.Windows.Forms.ToolBarButton() Me.ImageList1 = New System.Windows.Forms.ImageList(Me.components) Me.Label1 = New System.Windows.Forms.Label() Me.txtuser = New System.Windows.Forms.TextBox() Me.Label2 = New System.Windows.Forms.Label() Me.txtpasw = New System.Windows.Forms.TextBox() Me.cmdpre = New System.Windows.Forms.Button() Me.cmdnext = New System.Windows.Forms.Button() Me.Label3 = New System.Windows.Forms.Label() Me.txtcount = New System.Windows.Forms.TextBox() Me.txtusr1 = New System.Windows.Forms.TextBox() Me.SuspendLayout() ' 'tbr1 ' Me.tbr1.Buttons.AddRange(New System.Windows.Forms.ToolBarButton() {Me.btn1, Me.btn2, Me.btn3}) Me.tbr1.DropDownArrows = True Me.tbr1.ImageList = Me.ImageList1 Me.tbr1.Name = "tbr1" Me.tbr1.ShowToolTips = True Me.tbr1.Size = New System.Drawing.Size(344, 42) Me.tbr1.TabIndex = 0 ' 'btn1 ' Me.btn1.ImageIndex = 0 Me.btn1.Text = "New User" Me.btn1.ToolTipText = "New User" ' 'btn2 ' Me.btn2.ImageIndex = 1 Me.btn2.Text = "Save"

47

PIA RESERVATION SYSTEM Me.btn2.ToolTipText = "Save" ' 'btn3 ' Me.btn3.ImageIndex = 2 Me.btn3.Text = "Delete User" Me.btn3.ToolTipText = "Delete User" ' 'ImageList1 ' Me.ImageList1.ColorDepth = System.Windows.Forms.ColorDepth.Depth8Bit Me.ImageList1.ImageSize = New System.Drawing.Size(16, 16) Me.ImageList1.ImageStream = CType(resources.GetObject("ImageList1.ImageStream"), System.Windows.Forms.ImageListStreamer) Me.ImageList1.TransparentColor = System.Drawing.Color.Transparent ' 'Label1 ' Me.Label1.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label1.Location = New System.Drawing.Point(56, 72) Me.Label1.Name = "Label1" Me.Label1.Size = New System.Drawing.Size(104, 24) Me.Label1.TabIndex = 1 Me.Label1.Text = "User Name:" ' 'txtuser ' Me.txtuser.Location = New System.Drawing.Point(96, 104) Me.txtuser.Name = "txtuser" Me.txtuser.Size = New System.Drawing.Size(120, 22) Me.txtuser.TabIndex = 2 Me.txtuser.Text = "" ' 'Label2 ' Me.Label2.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label2.Location = New System.Drawing.Point(48, 136) Me.Label2.Name = "Label2" Me.Label2.Size = New System.Drawing.Size(104, 24) Me.Label2.TabIndex = 3 Me.Label2.Text = "Password:" ' 'txtpasw ' Me.txtpasw.Location = New System.Drawing.Point(96, 168) Me.txtpasw.Name = "txtpasw" Me.txtpasw.PasswordChar = Microsoft.VisualBasic.ChrW(42) Me.txtpasw.Size = New System.Drawing.Size(120, 22) Me.txtpasw.TabIndex = 4 Me.txtpasw.Text = ""

48

PIA RESERVATION SYSTEM ' 'cmdpre ' Me.cmdpre.BackColor = System.Drawing.Color.Honeydew Me.cmdpre.Cursor = System.Windows.Forms.Cursors.Default Me.cmdpre.Font = New System.Drawing.Font("Arial", 8.0!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.cmdpre.ForeColor = System.Drawing.SystemColors.ControlText Me.cmdpre.Image = CType(resources.GetObject("cmdpre.Image"), System.Drawing.Bitmap) Me.cmdpre.Location = New System.Drawing.Point(208, 224) Me.cmdpre.Name = "cmdpre" Me.cmdpre.RightToLeft = System.Windows.Forms.RightToLeft.No Me.cmdpre.Size = New System.Drawing.Size(27, 27) Me.cmdpre.TabIndex = 10 Me.cmdpre.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'cmdnext ' Me.cmdnext.BackColor = System.Drawing.Color.Honeydew Me.cmdnext.Cursor = System.Windows.Forms.Cursors.Default Me.cmdnext.Font = New System.Drawing.Font("Arial", 8.0!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.cmdnext.ForeColor = System.Drawing.SystemColors.ControlText Me.cmdnext.Image = CType(resources.GetObject("cmdnext.Image"), System.Drawing.Bitmap) Me.cmdnext.Location = New System.Drawing.Point(248, 224) Me.cmdnext.Name = "cmdnext" Me.cmdnext.RightToLeft = System.Windows.Forms.RightToLeft.No Me.cmdnext.Size = New System.Drawing.Size(27, 27) Me.cmdnext.TabIndex = 9 Me.cmdnext.TextAlign = System.Drawing.ContentAlignment.BottomCenter ' 'Label3 ' Me.Label3.AutoSize = True Me.Label3.BackColor = System.Drawing.Color.Transparent Me.Label3.Cursor = System.Windows.Forms.Cursors.Default Me.Label3.Font = New System.Drawing.Font("Book Antiqua", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Label3.ForeColor = System.Drawing.SystemColors.ControlText Me.Label3.Location = New System.Drawing.Point(40, 232) Me.Label3.Name = "Label3" Me.Label3.RightToLeft = System.Windows.Forms.RightToLeft.No Me.Label3.Size = New System.Drawing.Size(81, 16) Me.Label3.TabIndex = 7 Me.Label3.Text = "Total Users :" ' 'txtcount ' Me.txtcount.Location = New System.Drawing.Point(136, 224) Me.txtcount.Name = "txtcount"

49

PIA RESERVATION SYSTEM Me.txtcount.Size = New System.Drawing.Size(56, 22) Me.txtcount.TabIndex = 12 Me.txtcount.Text = "" ' 'txtusr1 ' Me.txtusr1.Location = New System.Drawing.Point(96, 104) Me.txtusr1.Name = "txtusr1" Me.txtusr1.Size = New System.Drawing.Size(120, 22) Me.txtusr1.TabIndex = 13 Me.txtusr1.Text = "" ' 'frmuser ' Me.AutoScaleBaseSize = New System.Drawing.Size(6, 15) Me.BackColor = System.Drawing.Color.Honeydew Me.ClientSize = New System.Drawing.Size(344, 278) Me.Controls.AddRange(New System.Windows.Forms.Control() {Me.txtusr1, Me.txtcount, Me.cmdpre, Me.cmdnext, Me.Label3, Me.txtpasw, Me.Label2, Me.txtuser, Me.Label1, Me.tbr1}) Me.Font = New System.Drawing.Font("Microsoft Sans Serif", 9.75!, System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, CType(0, Byte)) Me.Icon = CType(resources.GetObject("$this.Icon"), System.Drawing.Icon) Me.MaximizeBox = False Me.MinimizeBox = False Me.Name = "frmuser" Me.StartPosition = System.Windows.Forms.FormStartPosition.CenterParent Me.Text = "Users" Me.ResumeLayout(False) End Sub #End Region Dim sflag = False Dim dset As New DataSet() Private Sub tbr1_ButtonClick(ByVal sender As System.Object, ByVal e As System.Windows.Forms.ToolBarButtonClickEventArgs) Handles tbr1.ButtonClick Select Case tbr1.Buttons.IndexOf(e.Button) Case 0 txtusr1.Visible = False txtuser.Visible = True txtuser.Clear() txtpasw.Clear() Case 1 cmd.CommandText = "INSERT INTO usr values ('" & txtuser.Text & "','" & txtpasw.Text & "' )" Try cmd.ExecuteNonQuery() Catch ex As Exception MsgBox(ex.Message) End Try Case 2 txtuser.Visible = False

50

PIA RESERVATION SYSTEM txtusr1.Visible = True txtusr1.Clear() txtpasw.Clear() txtusr1.Focus() End Select End Sub Private Sub cmdpre_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdpre.Click Me.BindingContext(dset, "usr").Position -= 1 recnodisp() End Sub Private Sub cmdnext_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdnext.Click Me.BindingContext(dset, "usr").Position += 1 recnodisp() End Sub Sub recnodisp() txtcount.Text = Me.BindingContext(dset, "usr").Position + 1 & " of " & Me.BindingContext(dset, "usr").Count End Sub Private Sub txtusr1_KeyDown(ByVal sender As Object, ByVal e As System.Windows.Forms.KeyEventArgs) Handles txtusr1.KeyDown If e.KeyCode = Keys.Enter Then cmd.Connection = dbcon Dim Rd As sds.OleDbDataReader cmd.CommandText = "select * from usr where usr='" & txtusr1.Text & "'" Try Rd = cmd.ExecuteReader If Rd.Read Then txtpasw.Text = Rd(2) sflag = True If MsgBox("Are You Sure", MsgBoxStyle.YesNo, "Delete") = MsgBoxResult.Yes Then Rd.Close() Rd = Nothing cmd.CommandText = "delete * from usr where usr='" & txtusr1.Text & "'" Try cmd.ExecuteNonQuery() Catch ex As Exception MsgBox(ex.ToString) End Try Exit Sub End If Exit Sub Else sflag = False End If Catch Ex As Exception MsgBox(Ex.Message) Finally

51

PIA RESERVATION SYSTEM Try

Rd.Close() Rd = Nothing Catch End Try End Try If sflag = False Then MsgBox("User Name Not Found ") End If End Sub Private Sub frmuser_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load adap1 = New sds.OleDbDataAdapter("select * from usr", dbcon) dset.Clear() adap1.Fill(dset, "usr") 'dtgrd1.DataSource = dset.Tables(0) Try txtuser.DataBindings.Add("text", dset, "usr.usr") txtpasw.DataBindings.Add("Text", dset, "usr.pwd") recnodisp() Catch Ex As Exception MsgBox(Ex.Message) End Try txtusr1.Visible = False txtuser.Visible = True End Sub End Class

52

PIA RESERVATION SYSTEM

OUTPUT DESIGN Output Design of the system is as follow:

OUTPUT MEDIA AND OUTPUT TYPE (S) According to the requirements we have selected following output media and output types: 



Output media for this reservation system includes Printers and Screens. Output types are printed reports and screen status sheets.

RESERVATION REPORTS (THE PRINTED OUTPUT) Major and important output of the system is in the form of reports.Following types of reports have been designed:

•

AIRLINE

RESERVATION REPORTS

Airline reservation reports are as follow

1) AVAILABILITY REPORT 2) PLANE INFORMATION REPORT 3) FLIGHT SCHEDULE REPORT 4) PASSENGER INFORMATION REPORT

53

PIA RESERVATION SYSTEM

54

PIA RESERVATION SYSTEM

55

PIA RESERVATION SYSTEM

56

PIA RESERVATION SYSTEM

USER INTERFACE DESIGN To illustrate the user interface design of this reservation system , we developed a formal graphical prototype. In this regard, we designed the following user interface screens: 1) Process Control Screen 2) Data Entry Screen

PROCESS CONTROL SCREEN DESIGN For controlling the system processes and procedures, we have used a Menu-based approach. All the system’s operational components can be accessed from the main system menu screen. This screen includes the following basic main menus: 1) Main 2) Reports 3) Utilities 4) Help Each menu has submenues and lower level menus. These menus are shown in userguide / help.

DATA ENTRY SCREEN DESIGN Data entry screens that have been designed are as follow: 1) Screen for Adding Rooms Record 2) Screen for Modifying Rooms Record 3) Screen for Adding Halls Record 4) Screen for Modifying Halls Record 5) Bill printing options screen Note: Sample screens are attached with the documentation.

57

PIA RESERVATION SYSTEM

DATABASE DESIGN

AIRLINE RESERVATION SYSTEM BACKGROUND

This project deals with the development of a Software Requirements Specification (SRS) document that specifies what an airline reservation system should and should not do. The SRS document is divided into five sections namely 1. System Objectives This section lists all the goals and objectives of the system categorized based on the viewpoint of the airline company and the customer (passenger). These are higher-level goals which are somewhat broad in nature. They help in a top-down development of the SRS. 2. System Context This section clearly depicts the environment and boundaries of the Airline Reservation System and the entities with which it interacts. It helps us see how the system fits into the existing scheme of things. What the system will do by itself and what it expects other entities to do is clearly delineated 3. Functional Requirements This section is the bulk of the document and precisely states the functions of the system – what it should do and what it should not. This section is split into subsections modeled after the real world activities like reserving tickets, rescheduling tickets etc. Freedom from ambiguity and navigability were kept in mind while documentation. A consistent terminology has been followed throughout and the terms are explained in the appendix. The subsections follow a logical sequence that reflects the real world. For example, a customer cannot reschedule a ticket unless he has bought one earlier and cannot buy one unless he has checked its availability. 4. Non-functional Requirements These are quality requirements that stipulate the performance levels required of the system for various kinds of activities. Numerical lower and upper limits set conditions on the response times, access times etc of the system. Sometimes, tradeoffs are necessary among various non-functional requirements.

58

PIA RESERVATION SYSTEM

5. Future Requirements These are the specifications which are not provided for now in the current version of Airline Reservation System but which could be incorporated into future versions. Some of these need advanced technologies and interfaces with other systems. The Airline Reservation System could be designed in future to enhance the existing capabilities or add entirely new ones. The assumptions and limitations of the Airline Reservation System have been interspersed in the SRS to present the same in their proper context.

1.

System Objectives

1.1

The Airline Reservation System (Airline Reservation System) is a software application to assist an airline with transactions related to making ticket reservations, which includes blocking, reserving, canceling and rescheduling tickets. 1.2 From the viewpoint of the airline 1.2.1 Minimize repetitive work done by the system administrator and reservation clerks. 1.2.2 Maintain consistency among different access modes, e.g. by phone, by web, at the information desk and across different physical locations. The users should be basically taken through the same steps by the system as they go through in conventional desk-reservation systems. 1.2.3 Maintain customer information in case of emergency, e.g. flight cancellation due to inclement weather. The profile can also be used by the airline company to track user preferences and travel patterns to serve them better, plan routes, for better marketing and efficient scheduling of flights. 1.2.4 Maximize the revenue of the airline company by various means: 1.2.4.1 Increase awareness among frequent travelers about various special offers and discounts. 1.2.4.2 Minimize the number of vacant seats on a flight and maximize flight capacity utilization. 1.2.4.3 Maintain the capability to adopt a flexible pricing policy. The price of the tickets should be dynamically determined based on how early, before the date of departure, the customer buys the ticket. 1.3 A survey conducted by airline companies shows that users of an existing reservation system would respond favorably to an Airline Reservation System that satisfied or helped them satisfy the following objectives: 1.3.1

Reduce effort and frustration for travelers in scheduling a trip, especially by reducing the search effort for the flight they need to take.

59

PIA RESERVATION SYSTEM

1.3.2

1.3.5 1.3.6 1.3.7

Show all possible combinations and itineraries available for a pair of origindestination cities. Reduce redundancy in the information required from the customers in order for them to buy tickets, create user accounts etc. Check the validity of input data and give a feedback to the user in case of errors or inconsistency. Provide flexible access modes to users – internet, telephone, PDA. Protect customers’ privacy concerns. Make it easy for travelers to check the ticket status or make changes to their trip.

2.

SYSTEM CONTEXT

2.1

The Airline Reservation System will provide the following types of easy-to-use, interactive, and intuitive graphical and telephonic interfaces.

2.1.1

The Airline Reservation System will provide an easy-to-use, intuitive Graphical User Interface (GUI) as part of the Clerk/Administrator’s working desktop environment. The Airline Reservation System will also provide an easy-to-use, simple telephonic user interface, which can be accessed by the customers through telephone or cell phone from anywhere. This interface shall provide access, only to the following functionalities, namely, check flight schedule and check ticket status including any change in the flight timings. The functionality available through this telephonic interface is limited because of security constraints.

1.3.3 1.3.4

2.1.3

3.

FUNCTIONAL REQUIREMENTS

3.1

User Accounts

3.1.1 The passenger, who will henceforth be called the ‘user’, will be presented with 3 choices by the reservation system, as the first step in the interaction between them. A user can choose one of these and his choice would be governed by whether he is a guest or a registered user and whether he wants to check the availability of tickets or also block/buy them. The terms ‘registered user’ and ‘guest’ are described below. 3.1.1.1 A user who has traveled by the airline earlier would have been given a user id and a password. He would have his personal information stored in the database referred to earlier in section 2 as ‘DB-user’. This ‘personal information’ would be henceforth referred to as ‘profile’. Such a user with a profile in DB-user shall be called a ‘registered user’. A registered user will be able to check the availability of tickets as well as block/buy a ticket by logging into the system.

60

PIA RESERVATION SYSTEM

3.1.1.2 A new user, on the other hand, would either have to a) register himself with the system by providing personal information or b) log into the system as a guest. In case of ‘a’, the new user becomes a registered user. In case of ‘b’, the new user would remain a guest. A guest can only check the availability of tickets and cannot block or buy tickets. But a registered user can also act as a guest if he only wants to check the availability of tickets. ‘Availability of tickets’ always refers to viewing the flight schedule for given days, the price of tickets and any discount offers. The system shall present the user with an option to exit from the system at any time during the following processes.

3.2

REGISTRATION AND CREATION OF USER PROFILE The system shall require a user to register, in order to carry out any transactions with it except for checking the availability of tickets. It will ask the user for the following information at the least – a user id, a password, first name, last name, address, phone number, email address, sex, age, preferred credit card number. The system will automatically create a ‘sky miles’ field and initialize it to zero in the user’s profile.

3.3

CHECKING AVAILABILITY

3.3.1

After logging in a user (either a registered user or a guest), the system shall request him to enter the following details – origin city and destination city. “City’ is a generic term and refers to a city or town as the case may be. The origin and destination cities would be entered as text. The system shall now refer to the flight schedule database, referred to as ‘DBgeography’ in section 2, and check if there is any ambiguity with the names of the cities. In case there are more than two cities with same name as entered by the user, the system shall list all of them (with more qualifications) and ask the user to select one of them. In case, either the origin or destination cities are not listed in DB-geography as being directly serviced by the airline, the system shall suggest the nearest city to which service is available, including the distance of the destination city from this nearest city. After the origin and destination cities are ascertained, the system shall now access the flight schedule database, referred to as ‘DB-schedule’ in section 2, and checks if there is a direct operational service between the two cities. If not, the system shall suggest possible routes and transfer points using a ‘route selection algorithm’. The user shall now be presented with a choice of either selecting one of the routes. In case he selects a route, the system shall fill in the intermediate stop over points and create a multiple trip itinerary for the user.

3.3.2

3.3.3

61

PIA RESERVATION SYSTEM

3.3.4 The system shall now ask the user to enter the following details - class, one-way or round trip, departure date and the number of adult passengers, children and senior citizens. 3.3.4.1 ‘Class’ refers to business class/first class/club class/smoking/non smoking. This choice shall be made by the user through a drop down menu indicating all the possible combinations of choices. 3.3.4.2 One-way/round trip shall be either a drop down menu or a check box selection. ‘Departure date’ refers to either a single date or a range of dates, entered through a calendar-like menu. This menu shall not show dates in the past or those dates that are too ahead in the future (as determined by the airline policy). In case, the trip is a round trip, the system shall also ask the user to enter the departure date on the return trip. 3.3.4.3 Having taken all the above input from the user, the system checks for any false entries like the departure date on the return trip being earlier than the departure date on the onward trip. In case of incompatibility, the system shall display a suitable error message and prompt the user to enter the information correctly. 3.3.5 Having taken all of the information as laid out above in 3.3.1 and 3.3.4, the system shall now access the flight schedule database ‘DB-schedule’ and queries it using the input provided by the user. 3.3.6 The system queries the reservation database ‘DB-reservations’ to check which of the flights on the schedule have seats available. The system displays the results in a suitable form (a tabular form) with the following information depicted – for each flight number – the flight number, departure time in origin city, arrival time in destination city, the duration of the flight (taking into account the possibility of a change of time zone) and the number of seats available on that flight. 3.3.6.1 There can be several flights between two cities and all of them will be listed for the particular date that the user wants to depart from the Origin City. In case, the user has entered a range of dates, the system shall display all the flights for all those dates in the range. 3.3.6.2 If the user has requested a round trip, the system shall display two tables - one for the onward trip and one for the return trip. There will be a check box in front of each line in the table representing a flight with available seats. 3.3.6.3 The user is now asked to check one of the boxes reflecting a choice of a flight number and time. In case of a round trip, the user is asked to check one box each in the two tables. 3.3.7 The system shall now display the price of the ticket for the trip. This will be the sum of the prices for all the members of the travel party being represented by the user. 3.3.7.1 The system shall also list any rules regarding the cancellation of tickets – what percentage of the price will be refunded within what date ranges. This will be displayed as a table.

62

PIA RESERVATION SYSTEM

3.4 Making Reservations/Blocking/Confirmation 3.4.1 After having taken the user through the step 3.3, Checking Availability, The system will now ask the user if he wishes to block/buy the ticket. If yes, and a) if the user has been a guest, he will have to first register and become a registered user and then log onto the system. b) If the user is already a registered user, and if he has logged on already, he can block/buy the ticket, but if he has been acting as a guest, he will have to log on. 3.4.2 Having ensured that the user is logged on validly according to 3.4.1, the system compares the departure date with the system date. If the departure date falls within 2 weeks of the system date, the system informs the user that he has no option to block the ticket and asks him if he would like to buy it. 3.4.2.1 If the difference between the departure date and system date is more than 2 weeks, the system asks the user if he would like to block or buy the ticket. The system informs the user that he can block the ticket at no cost now. It also informs him that if he chooses to block the ticket, he should make a final decision before 2 weeks of the departure date. The system shall send an email to the user, 3 weeks before the departure date as a reminder, in case he decides to block the ticket now. 3.4.3 Having taken the input from the user in 3.4.2, the system shall now proceed to update the reservation database DB-reservation. It will decrement the number of available seats on the particular flight for the particular class by the number of travelers being represented by the user. 3.4.3.1 In case of a blocking, the system makes a note of it in the database - to be used if the user doesn’t turn up before 2 weeks of the departure date. It generates a blocking number and displays it for the user to note down. 3.4.3.2 In case the user buys the ticket, the system accesses his profile and charges the price of the ticket to his credit card number. It simultaneously generates a confirmation number and displays it to the user for him to note down. The ticket has been reserved. 3.4.3.3 It adds the mileage of the trip (accounting for the number of travelers) to the sky miles in his profile. 3.5

CONFIRM TICKET

3.5.1

A user who has earlier blocked a ticket after going through the steps 3.2 through 3.4 is required to either confirm the ticket before two weeks of the departure date or the ticket stands cancelled. To let the user confirm a ticket, the system shall first log him on and ask for his blocking number. Then it accesses DB-reservation and removes the check mark, which so far represented a blocked seat. The seat is now confirmed and reserved for the user. The system accesses DB-user and charges the price of the ticket to the credit card number of the user. It simultaneously generates a confirmation number and displays it for the user to note down. The ticket has been reserved.

3.5.2

3.5.3

63

PIA RESERVATION SYSTEM

3.5.4 3.6

It adds the mileage of the trip (accounting for the number of travelers) to the sky miles in his profile.

RESCHEDULE TICKET

3.6.1

The system shall present the user with an option to re-schedule his travel party’s trip. In order to do this, the system first logs on the user and requests his confirmation number. It will not allow a user to reschedule a blocked ticket but only a confirmed ticket. Using this, it queries DB-reservation and presents the details of the trip to the user, including but not limited to origin city, destination city, date of departure and date of arrival (in case the trip is a round trip). 3.6.2 The system shall now ask the user to select new dates from the calendar-menu. It now goes through step 3.3. 3.6.2.1 In case, there are no available tickets for the dates entered, it displays a suitable message informing him that rescheduling to that date is not possible. 3.6.2.2 In case there are tickets available, the system asks the user to select the flight number for the trip (another for the return trip if the trip is a round trip) and proceeds to update the database. 3.6.3 The system accesses DB-reservation and decrements the number of available seats on the flight(s) by the number of members in the user’s travel party. It then increments the entry for the previous flight by the same number to reflect an increase in the available seats on it as a result of the rescheduling. 3.6.4 The system now checks if there is any difference in the prices of the tickets. If so, it accesses DB-user and charges or credits the credit card as the case may be. The system generates a new confirmation number and displays it to the user.

3.7

CANCELLATION

3.7.1

The system shall also give the user an option to cancel a confirmed ticket or a blocked ticket. 3.7.1.1 The latter case is simpler and will be dealt with first – the system shall first log on the user and request the blocking number. Then it accesses DB-reservation and updates it by incrementing the number of available seats by the number of people in the user’s travel party. 3.7.1.2 In the former case, i.e., for a confirmed ticket, it asks for the confirmation number and accesses DB-reservation and presents the details of the trip as in step 3.6.1. 3.7.2 It then lists the applicable rules for cancellation of tickets and depending on the system date and the departure date; it displays the % of the amount that would be refunded if the user cancels the ticket. 3.7.3 After the user cancels the ticket, the system generates a cancellation number and displays it for the user to note down. It accesses DB-reservation and updates it by incrementing the number of available seats on that flight by the number of

64

PIA RESERVATION SYSTEM

travelers in the user’s party. It accesses DB-user and credits the refund amount to his credit card number. The system then deducts the mileage of the trip (taking into account the number of travelers in his party) from the sky miles in his profile.

3.8

UPDATE PROFILE The system shall enable the user to update his profile at any time. Changes can be made in fields including but not limited to address, phone number and preferred credit card number.

3.9

VIEW TICKET STATUS The system shall allow a user to view all information about his trip. After logging him on, it asks for his blocking number or his confirmation number. It accesses DB-reservation and retrieves the details of the trip and presents them to the user in a convenient format, including any last minute changes to the flight timings etc. Such changes will be highlighted.

3.10 QUERY FLIGHT DETAILS The system shall allow any user (registered or none registered) to access the details about the arrival and departure times of a flight by requesting the user to input the flight number and date. The system accesses DB-schedule and presents the time of arrival and departure. 3.11 TELEPHONE ACCESS The system shall be accessible through a touch-tone telephone. The telephonic interface shall, at the least, provide the customer with the facility to check availability of tickets and query flight details. The system shall walk the customer exactly through steps 3.3 and 3.9 respectively but through a telephonic interface.

4 NON-FUNCTIONAL REQUIREMENTS 4.1

PERFORMANCE

4.1.1

Response time of the Airline Reservation System should be less than 2 second

65

PIA RESERVATION SYSTEM

4.1.2 4.1.3

4.2 4.2.1 4.2.2

4.2.4

most of the time. Response time refers to the waiting time while the system accesses, queries and retrieves the information from the databases (DB-user, DBschedule etc) (A local copy of flight schedule database is maintained as DBschedule to reduce this access time) Airline Reservation System shall be able to handle at least 1000 transactions/inquiries per second. Airline Reservation System shall show no visible deterioration in response time as the number of users or flight schedule data increases.

RELIABILITY Airline Reservation System will be available 24 hours a day, 7 days a week Airline Reservation System shall always provide real time information about flight availability information. Airline Reservation System shall be robust enough to have a high degree of fault tolerance. For example, if the user enters a negative number of passengers or a value too large, the system should not crash and shall identify the invalid input and produce a suitable error message. Airline Reservation System shall be able to recover from hardware failures, power failures and other natural catastrophes and rollback the databases to their most recent valid state.

4.3.1

USABILITY

4.3.2

Airline Reservation System shall provide an easy-to-use graphical interface similar to other existing reservation system so that the users do not have to learn a new style of interaction. The web interface should be intuitive and easily navigable Users should be able to understand the menu and options provided by Airline Reservation System. Any notification or error messages generated by Airline Reservation System shall be clear, succinct, polite and free of jargon.

4.3.2 4.3.3

4.4

Integrity

4.4.1

Only system administer has the right to change system parameters, such as pricing policy etc. The system should be secure and must use encryption to protect the databases. Users need to be authenticated before having access to any personal data.

4.4.2

66

PIA RESERVATION SYSTEM

4.5.1 INTEROPERABILITY 4.5.2

Airline Reservation System shall minimize the effort required to couple it to another system, such as flight schedule database system.

5

Future Requirements

5.1 Support for waiting list functionality 5.1.1. Airline Reservation System shall be made more flexible in ticket reservation handling, and shall accept waiting list for reservation. 5.1.2 The waiting list handling capability of Airline Reservation System shall be made more advanced, by enabling it to send requests to the Flight Scheduler to schedule extra flights, depending on the demand in a particular corridor, and providing the wait listed passengers with a new flight. 5.2 The telephonic interface of the Airline Reservation System shall be improved to support more functionality like allowing the customers to cancel a ticket etc., by incorporating security measures. 5.3 Airline Reservation System shall be made more dynamic and helpful to the users by enabling it to send instant messages to the passengers, of a cancelled or rescheduled flight, through email, phone, fax etc., informing them about the change, and providing them with other feasible alternatives. 5.4 Information about the kind of meals served in a flight and the type of entertainment offered on a flight should be incorporated into the system. 5.5 5.6 5.7 5.8

Provide service integration with auto rental agencies and hotel chains. Interface for the travel agents shall be provided in the future versions with additional features like informing them of any availability of seats on a flight which was earlier booked to capacity. Choices like aisle or window seats shall be provided to the users. The Airline Reservation System shall be able to handle the situation where flight services are available to multiple airports in a single city.

67

PIA RESERVATION SYSTEM

A I RL IN E T I CK E T IN G R E S E RVAT I ON S Y S T E M (E NT I TY R E L AT I ON S H I P D IA GR A M )

SCHEDULE

Flight Number Departure Date Departure Time Arrival Date Arrival Time Origin Destination

RESERVATION

Customer Name Father Name Flight Number Departure Date Departure Time Arrival Date Arrival Time Seat Number Cancel Seat

PLANE

Plane Name Flight Number Total Seats Available Seats

CUSTOMER

Customer Name Father Name NID Age Gender Address Contact Number Reservation Date Origin Destination

68

PIA RESERVATION SYSTEM

APPENDIX

1. ER Diagram The ER diagram is drawn to have a better understanding of the whole scenario; it was used to conceptualize the phenomena, actions and interactions between various entities and to arrive at the specific requirements in a comprehensive manner. The ER diagram is attached with this SRS. 2. Definition of the terms used •

• •

•

• •

Blocking – This term refers to the temporary holding of a seat(s) on a flight for a specific period of time. The user incurs no cost for blocking a ticket, but must make a decision at least two weeks prior to the date of departure. Confirming – Process of changing a ticket from a Blocked status to a bought status. Rescheduling – This process means that the user is allowed only to postpone the travel date and he has to pay the difference in fare. No other details can be changed through this process. For example the number of passengers can’t be changed. Base Price – This refers to the maximum price of a ticket, which usually is the price when the purchase is made at the last minute. This is used in arriving at the discounted price which depends on various factors like early bird booking etc. Flight – This refers to a one-way trip made by an aircraft from a particular to a particular destination at a particular time on a particular weekday. Flight Number – This uniquely identifies a flight.

3

Precondition/post-condition style with template data spec

3.1

Reserving Ticket Triggering event The user invokes “buy tickets” feature from the Airline Reservation System user interface. Precondition 1. The user has logged into the system. 2. User has entered all the necessary input - details of the trip 3. Seats are available for the above request.

69

PIA RESERVATION SYSTEM

Post condition 1. The seat requested is reserved and a reservation number is issued to the customer. 2. The available number of seats in the database DB- reservation is updated. 3. Sky miles are updated in the customer profile. 4. The Customer pays money is charged for the ticket fare. 3.2

Changing ticket status from blocked to confirmed Triggering Event The user invokes the “Confirm Ticket” feature in the Airline Reservation System user interface after the confirmation of the customer. Precondition 1. The user is logged onto the Airline Reservation System. 2. The user has entered a blocking number. 3. The date of departure is at least two weeks into the future Post condition 1. The ticket is reserved and a reservation number is generated and displayed. 2. The check mark indicating the blocked status in the DB reservation is removed, and an updated database results. 3. The customer is charged money of the ticket fare.

70

PIA RESERVATION SYSTEM

71

PIA RESERVATION SYSTEM

CHAPTER # 5

SYSTEM IMPLEMENTATION

 Method Used For Implementation (Parallel Conversion)

72

PIA RESERVATION SYSTEM

SYSTEM IMPLEMENTATION SYSTEM IMPLEMENTATION& MAINTENANCE In development of a newly proposed system, the implementation and maintenance are the last phase of system development life cycle (SDLC). The purpose of the system implementation is to build a properly operational system, to install it in the organization and then allow users to take over its operation for use and evaluation. Implementation also includes finalizing complete system, and preparing support system to assist as they encounter difficulties. The purpose of system maintenance is to fix and enhance the system to respond to problems and changing business conditions. Maintenance work also includes activities from all system all development phase and usually eventually leads to a decision to abandon a system and build a replacement, starting the cycle over again.

IMPLEMENTATION Implementation is the activity of getting the designed system in operation. The implementation of any system is a difficult and time-consuming change. The conversion to the new system must plan carefully. The new system may be totally new or a replacement of the existing system or it may be a major modification to the existing one. In either case proper implementation is essential to provide a reliable system to meet the requirement .It is a planned work and requires more attention of the system designer.

Following are the major aspect of the system implementation. 1. 2. 3. 4. 5. 6.

Coding Testing Installation Documentation Training Support

73

PIA RESERVATION SYSTEM

METHOD USED FOR IMPLENENTATION

POST-IMPLEMANTION REVIEW The post- implementation review usually takes place about a year after the system is implemented. PERIODIC evaluation of the new proposed system in terms of the system efficiency, accuracy, security etc. It reviews the new system to see if it has indeed satisfies the designed system objectives.

MAINTENANCE Once an information system is installed, the system is essentially in the maintenance phase of the (SDLC).Maintenance us necessary to eliminate errors and enhance system functionally during the operation. it also cater changes in future that can be of any from like: Basic pay scale by government Allowance variations Variation in recovery period of advances Gross Provident Fund Interest Rate One year and result obtain from the new system can be compared to the output of the old system. This strategy will permit changes and adjustment of the new system without disturbing information

.

74

PIA RESERVATION SYSTEM

CHAPTER # 6

SYSTEM TESTING AND EVLUATION

 Testing Strategies  Code Testing  User Training  Conclusion

75

PIA RESERVATION SYSTEM

TESTING The testing process can being and process can being and proceed in parallel with the coding. As each program module is produced, it can be tested individually, then as part of a larger program, and then as part of a large system .A main requirement of testing is that it must be planned. Testing involves using test data and scenarios to verify that each component and the whole system work under normal and abnormal circumstances. The purpose of testing is confirming that the system satisfies requirements, including finding errors.

TESTING STRATEGIES (USED) Following testing strategies have been used to test the new Reservation of Pakistan International airline Lahore:

• UNIT TESTING We have performed Unit Testing for the new Reservation System PIA Lahore by dividing the whole system into Input/Output, Data Formates, Record Keys, Calculations, Table Constructions, Logical Control Structures, Comparisons and Error Processing Units.

• SYSTEM TESTING System has been multiple times tested and evaluated to ensure that it is operating according to the desired requirements by integrating all modules of the system. Major level modules that have been tested includes:    

Seat Reservation Module Plane information Module Fight Schedule Module Other Operational Modules (including basic Operations, tools and options etc.)

76

PIA RESERVATION SYSTEM

• VOLUME TESTING A large amount of data has been entered in the new Reservation System. This data includes: 1) Dummy data (for testing purpose) 2) Actual data (taken from parallel working old Reservation System) Overall volume testing has been performed through Peak Load Testing, Storage Testing, Performance and Response Time Testing, Recovery Test, Procedure Level Test and Human Factor Test.

CODING Coding is the process, whereby the physical designs specifications are created by the analysis team are turned into working computer code by the programming team. Different code modules have been tested using sampling approch and conclusions have been derived from these tests. Due to the much bulky and heavy code,we have aslo adopted heuristic approach.

USER TRAINING Although the system is userfriendly and flexible enough to operate without any special and tough training, we have provided a comprihensive user guide to communicate with exeptional results. Following sources can be used for users training. 1) User Guide (Chapter No # 8 of this documentation booklet) 2) Training lectures can also be arranged on the requirement of Reservation Staff or Management. For our lecture-based training program, visual aid and projection equipment is a must.

3) In a parallel way, technical support manuals will be written as and when required especially on enhancement of the Reservation System PIA Lahore.

77

PIA RESERVATION SYSTEM

INSTALLATION It is the process during which the current system is replaced/ supported by the new system. This includes conversion of existing data, software, and documentation and work procedures to those consistent with the new system.

DIRECT INSTALLATION It is the changing over from the old information system to new one by turning off the old system as the new one is turned on.

PARALLEL INSTALLATION Running the old information system and the new one at the time until management decides the old system can be turned off.

SINGLE LOCATION INSTALLATION Trying out a new information system, at one site and using the experience to decide if and how the new system should be deployed throughout the organization.

PHASED INSTALLATION It is the changing over from the old information system to a new one incrementally, starting with one or a few functional component and then gradually extending the installation to cover the whole new system.

DOCUMENTATION Documentation includes reviewing project dictionary for completeness as well finalizing all user documentation, such as user guides, reference card and tutorials. Although the process of documentation proceeds throughout the life cycle but it receives formal attention during implementation phase.

78

PIA RESERVATION SYSTEM

SYSTEM DOCUMENTATION It is the detail information about a system’s design specification, its internal workings, and its functionality.

INTERNAL DOCUMENTATION The system documentation that is part of the program source code or is generated at compile time.

EXTERNAL DOCUMENTATION The system documentation that includes the outcome of such structured diagramming techniques as data flow and entity-relational diagrams.

USER DOCUMENTATION It is the written or other visual information about an application system, i. e; how it work, and how to use it.

USER TRANNING Training of the user like Database Administrator (DBA) and Data Entry Operator (DEO) is vet essential for the successful operation of the computer based information system. Different method that is used mostly for information System is categorized as follows: 1. 2. 3. 4. 5.

Tutorial Course Computer Interactive Training Manuals Software Help Components

SUPPORT

Support of the system provides on-going educational and problem-solving assistance to information system users. For in-house developed system, support materials and jobs will have to be prepared or designed as part of the implementation process.

79

PIA RESERVATION SYSTEM

Once the information system is placed into operation i.e., implemented, the system support phase of the project starts. This may include: 1. Installation of new hardware and software. 2. Setup user accounts. 3. Answering of basic on-demand question. 4. Correction of software bugs that are not caught during the test phase. 5. Improvement in system like generation of more new reports or addition of user from or change in the report layout. 6. Reviewing the system the documentation and manuals for improvements, typing mistakes, etc.

CONCLUSION Under these circumstances mentioned in this project, the decision making is very difficult for the Administration from the existing system can handle only a limited number of employee records and their concerned information. The proposed system compiles with all requirements of the PAKISTAN INTERNATIAL AIRLINE. The system is developed using VB .NET, access and crystal report and has been tested efficiently under window 2000 Professional Edition on 933 MHZ Pentium – III computer Following are the salient feature of the new system 1. 2. 3. 4.

The system can handle flights records in Gigabytes. Presently, the new system is developed, by keeping in view past, current and future requirements of PIA. The system can be easily accessible due to desk top implementation. The usage of latest software ensures that no up gradation of software is required in near future.

80

PIA RESERVATION SYSTEM

CHAPTER # 7



FUTURE EXTENTION

FUTURE EXTENTION

81

PIA RESERVATION SYSTEM

FUTUER EXTINSION Our future extension is to develop or modify this project in advance level. We will try to develop it in ASP. ASP, SQL server Centralized Database System in future. System will work on Intranet Environment .Therefore the durability of the data increases as the data can be stored on different hardware devices.

82

PIA RESERVATION SYSTEM

CHAPTER # 8

USER GUIDE



USER HELP TOPICS AND TECHNICAL SUPPORT

83

PIA RESERVATION SYSTEM

GETTING STARTED System is initiated with a Login Form.After logging in successfully, a maximized window appears before you. This window contains the basic operational menus including File,Reservation, Tools and Help Menu.Each of these menus has further submenus and lower level menus, including relevent commands and options.

CHECKING SEAT AVAILABLE STATUS To check the status of Occupied seats, follow the following command: Choose Reservation > go to add reservation > check the available seats. A status sheet will be opened that shows the seats Occupation

84

PIA RESERVATION SYSTEM

SPLASH FORM

CHECKING SEAT AVAILABLE STATUS To check the status of Occupied seats, follow the following command: Choose Reservation > go to add reservation > check the available seats. A status sheet will be opened that shows the seats Occupation Situations.

85

PIA RESERVATION SYSTEM

SAVING A SEATS RECORD In order to save a seats reservation record follow thses steps: 1) Choose Resrvation > Plan information > Add Seats Record. A Seat Reservation Entry Form will be opened. 2) After entering the required and valid data, click the Save button to save the record. If you don't want to save the record and get the control out of the Reservation Form, Then click the Cancel button.

86

PIA RESERVATION SYSTEM

DELETING A SEAT RECORD In order to delete a seat reservation record follow thses steps: 1) Choose Add Resrvation >Cancle > Delete Seat Record A Seat Reservation Deletion Form will be opened. 2) Retrieve the records sequentially (by using the button of Next, Previos, First and Last) or directly (by using the button of search).Now click Delete button. System will show a confirmation message. Click ' Yes ' on the message box to actally delete the existing record.

87

PIA RESERVATION SYSTEM

MODIFYING A SEAT RECORD In order to modify an existing seat reservation record follow thses steps: 1) Choose Resrvation > flight schedule > Modify Seats Record A Seat Reservation Modification Form will be opened. 2) Retrieve the records sequentially (by using the button of Next, Previos, First and Last) or directly (by using the button of search).Now click the Modify button.

SEARCHING A SEAT RECORD In order to search an existing seat reservation record follow these steps: 1) Choose Resrvation > Totle Seats > Search Seat Record A flight- schedule Search Form will be opened. 2) Retrieve the records sequentially (by using the button of Next, Previos, First and Last) or directly (by using the button of search).

88

PIA RESERVATION SYSTEM

VIEWING SEATS REPORTS Different types of Seat Reservation Reports can be viewed from Report submenu. Standard reports include: 1) Seats Availability Report 2) Up-to-Date Seat Reservation Report 3) Airport Information report 4) New Schedule Report 5) Delete Report 6) Search Report

89

PIA RESERVATION SYSTEM

90

PIA RESERVATION SYSTEM

USING TOOLS In order to use tools like Calander, Calculator and Bill Printing, choose the relevant command from Tools Menu.

91

PIA RESERVATION SYSTEM

GETTING EXIT FROM THE SYSTEM In order to close the System windows and get the control out of the System adopt one of the following ways: 1) Choose Exit 2) Press Alt + F4 3) Use the Close Button from the Control Box located on the right top corner of the Main System Window.

92