Online Airline Reservation Systemdocshare02.docshare.tips/files/30520/305206296.pdf · TheAirline...

Online Airline Reservation System

PROJECT SUPERVISOR:Mr. Faisal Shahzad

UNDERTAKEN BY: Roll No# 25

MCS SESSION 2012-2014

DEPARTMENT OF COMPUTER SCIENCETHE ISLAMIA UNIVERSITY OF BAHAWALPUR

All Praised Are For

The most beneficent, who guides us in the darkness and helps in difficulties,Without this help one can never achieve destination.

All Respects Are For His HOLLY PROPHET HAZRAT MUHAMMAD (P.B.U.H)

Who enlighten out the minds to recognize our creature.FINAL APPROVEL

It is to certify, that we have gone through this project report that is submitted by So, Roll # 25, Session 2012-2014. Our judgment is that this Project is up to the standard to warrant its acceptance by the Islamia University Bahawalpur for the MCS Degree Computer Science.

External examiner:

Supervisor:

Chairman: DR. Doast Muhammad KhanDepartment Of Computer Science,Islamia University Bahawalpur.

Dedication:

This project is dedicated to The Planner, The Creator of the entire Universe; TheMerciful ALLAH, and his loving messenger Hazrat Muhammad (Peace Be upon Him).ALLAH has given me the power to perform this task and facilitating every possible

means to complete this project.

In last this project is dedicated to my beloved Parents.

PROJECT BRIEFPROJECT NAME Online Airline Reservation System

OBJECTIVE The main objective of this project is to design an airline reservation System which enables the customers to search and book flights Project Started _ _ _ _ _ _ _ _ _ _ _ _ _ _ Project Finished _ _ _ _ _ _ _ _ _ _ _ _ _ _

Source Language Adobe Dreamweaver CS6, My SQL

Operating System Windows 8

Chp# TABLE OF CONTENTS Page

1 Vision Document 9

1. Introduction 10 1.1 Purpose And Motivation 10 1.2 Project Overview 10 2. Overall Product Description 10 2.1 Product Perspective 10 2.2 Product Features 17 2.3 User Characteristics 20 2.4 Constraints 20 1. Introduction 27

2. Architecture Of The Airline Reservation System 273 Component Design 31

1. Introduction And Purpose 32 2. Class Diagram 32

4 Test Plan 37 1. Test Plan Identifier 38 2. Introduction 38 2.2 Objectives 41 2.3 Definitions 42 3. Test Items 42 4. Approach 42 5. Test Cases 44 6. Pass Or Fail Criteria 45 7. Suspension Criteria And Resumption Requirements 45 7.1 Suspension Criteria 45

7.2 Resumption Requirements 45 8. Test Deliverables 46

5 Assessment Evaluation 47 1. Introduction 48 2. Test Case Result Summary 48 3. Detailed Test Result 48

6 User Manual 52 1. Introduction 53 1. Required Software 53

Chapter: 01

Vision Product

INTRODUCTION

1.1 PURPOSE AND MOTIVATION

The main purpose of this vision document is to list the requirements of the AirlineReservation System project. This document also helps us to collect and analyze the ideasgathered for the project. This vision document will be subject to change, if more requirements are added to the project. This document is mainly prepared to set stage for the design phase of the project. The document being prepared is the first version of vision document for the Airline Reservation System project.Web Programming is a new technology which is being used a lot in the IT field. My interest to learn this new technology has prompted me to take up this project, which would set the stage for the applications I would be developing in the future.

1.2 PROJECT OVERVIEW

The Airline Reservation System project is an implementation of a general AirlineTicketing application, which helps the customers to search the availability of various airline tickets. This project also covers various features like registration of the users, modifying the details of the application by the management staff or administrator, by adding, deleting or modifying the customer details, flights information.

2. OVERALL PRODUCT DESCRIPTION

2.1 PRODUCT PERSPECTIVE

The Airline Reservation System project uses the DreamWeaver CS6 and is completelyIndependent. The project itself is a bigger product and does not need to be introduced into a larger system. The application would be running on a Windows 8 Operating system.

3. TECHNOLOGIES USED3.1. PHP: Hypertext Preprocessor

PHP is a widely used, general-purpose scripting language that was originally designed for web development to produce dynamic web pages. For this purpose, PHP code is embedded into the HTML source document and interpreted by a web server with a PHP processor module, which generates the web page document.

PHP Advantages:PHP source code is compiled on-the-fly to an internal format that can be executed by the PHP engine. In order to speed up execution time and not have to compile the PHP source code every time the webpage is accessed, PHP scripts can also be deployed in executable format using a PHP compiler.

PHP is one of the most popular server side scripting languages running today. It is used for creating dynamic webpages that interact with the user offering customized information. PHP offers many advantages; it is fast, stable, secure, easy to use and open source (free).

PHP code is inserted directly into the HTML that makes up a website. When a visitor comes to the website, the code is executed. Because PHP is a server side technology, the user does not need any special browser or plug-ins to see the PHP in action.

The beauty of PHP lies in its simplicity. It is easy to understand and learn, especially for those with backgrounds in programming such as C, JavaScript and HTML. The language is similar to C and Perl so that anyone with a background in either C or Perl programming will feel comfortable using and understanding PHP. PHP also runs on just about every platform including most UNIX, Macs and Windows versions.

Another key advantage of PHP is its connective abilities. PHP uses a modular system of extensions to interface with a variety of libraries such as graphics, XML, encryption, etc. In addition, programmers can extend PHP by writing their own extensions and compiling them into the executable or they can create their own executable and load it using PHP's dynamic loading mechanism.

A huge advantage that PHP offers is its community. Since PHP is an A huge advantage that PHP offers is its community. Since PHP is an open source project, the PHP community is willing to share. If you'relooking for a particular script, chances are another user has already created something similar. Check within the PHP community for availability. Likewise, if you have created a function that others might enjoy, be sure to post the code for others.

A PHP scripting block always starts with <? php and ends with ?>. A PHP scripting block can be placedanywhere in the document.On servers with shorthand support enabled you can start a scripting block with <? and end with ?>.For maximum compatibility, we recommend that you use the standard form (<?php) rather than the shorthand form.<? php?> A PHP file normally contains HTML tags, just like an HTML file, and some PHP scripting code.Below, we have an example of a simple PHP script which sends the text "Hello World" to the browser:<html><body>

<? phpecho "Hello World";?>

</body></html> Each code line in PHP must end with a semicolon. The semicolon is a separator and is used to distinguish one set of instructions from another.There are two basic statements to output text with PHP: echo and print. In the example above we have used the echo statement to output the text "Hello World".Note: The file must have a .php extension. If the file has a .html extension, the PHP code will not be executed.________________________________________

Comments in PHPIn PHP, we use // to make a single-line comment or /* and */ to make a large comment block.<html><body>

<?php//This is a comment

/*This isa commentblock*/?>

</body></html>

Variables in PHPVariables are used for storing a values, like text strings, numbers or arrays.When a variable is declared, it can be used over and over again in your script.All variables in PHP start with a $ sign symbol.The correct way of declaring a variable in PHP:$var_name = value;

________________________________________

PHP is a Loosely Typed LanguageIn PHP, a variable does not need to be declared before adding a value to it.In the example above, you see that you do not have to tell PHP which data type the variable is.PHP automatically converts the variable to the correct data type, depending on its value.In a strongly typed programming language, you have to declare (define) the type and name of the variable before using it.In PHP, the variable is declared automatically when you use it.

3.2 SessionsA PHP session variable is used to store information about, or change settings for a user session. Sessionvariables hold information about one single user, and are available to all pages in one application.________________________________________PHP Session VariablesWhen you are working with an application, you open it, do some changes and then you close it. This is much like a Session. The computer knows who you are. It knows when you start the application and when you end. But on the internet there is one problem: the web server does not know who you are andwhat you do because the HTTP address doesn't maintain state.A PHP session solves this problem by allowing you to store user information on the server for later use (i.e. username, shopping items, etc). However, session information is temporary and will be deleted after the user has left the website. If you need a permanent storage you may want to store the data in a database.Sessions work by creating a unique id (UID) for each visitor and store variables based on this UID. TheUID is either stored in a cookie or is propagated in the URL.________________________________________Starting a PHP SessionBefore you can store user information in your PHP session, you must first start up the session.Note: The session_start() function must appear BEFORE the <html> tag:<? php session_start(); ?>

<html><body>

</body>

</html> The code above will register the user's session with the server, allow you to start saving user information, and assign a UID for that user's session.

________________________________________

Storing a Session VariableThe correct way to store and retrieve session variables is to use the PHP $_SESSION variable:<?phpsession_start();// store session data$_SESSION['views']=1;?>

<html><body>

<?php//retrieve session dataecho "Pageviews=". $_SESSION['views'];?>

</body></html> Output:Pageviews=1 In the example below, we create a simple page-views counter. The isset() function checks if the "views"variable has already been set. If "views" has been set, we can increment our counter. If "views" doesn't exist, we create a "views" variable, and set it to 1:<?phpsession_start();

if(isset($_SESSION['views']))$_SESSION['views']=$_SESSION['views']+1;else$_SESSION['views']=1;echo "Views=". $_SESSION['views'];?>

________________________________________Destroying a SessionIf you wish to delete some session data, you can use the unset() or the session_destroy() function.The unset() function is used to free the specified session variable:<?phpunset($_SESSION['views']);?>

You can also completely destroy the session by calling the session_destroy() function:<?php session destroy(); ?> Note: session destroy() will reset your session and you will lose all your stored session data.

PHP Form Handling

The most important thing to notice when dealing with HTML forms and PHP is that any form element in an HTML page will automatically be available to your PHP scripts.ExampleThe example below contains an HTML form with two input fields and a submit button:<html><body>

<form action="welcome.php" method="post">Name: <input type="text" name="fname" />Age: <input type="text" name="age" /><input type="submit" /></form>

</body></html>

The PHP $_GET and $_POST variables are used to retrieve information from forms, like user input.When a user fills out the form above and click on the submit button, the form data is sent to a PHP file, called "welcome.php":"welcome.php" looks like this:<html><body>

Welcome <?php echo $_POST["fname"]; ?>!<br />You are <?php echo $_POST["age"]; ?> years old.

</body></html>

Output could be something like this:Welcome John!You are 28 years old.The PHP $_GET and $_POST functions will be explained in the next chapters.________________________________________

Form ValidationUser input should be validated on the browser whenever possible (by client scripts). Browser validationis faster and reduces the server load.You should consider server validation if the user input will be inserted into a database. A good way to validate a form on the server is to post the form to itself, instead of jumping to a different page. The

user will then get the error messages on the same page as the form. This makes it easier to discover the error.

3.3 History of MySQLWe started out with the intention of using the MySQL database system to connect to our

3.3.1. MySQL StabilityThis section addresses the questions, “How stable is MySQL Server?” and, “Can I depend on MySQL Server in this project?”. The information in this section is based on data gathered from the mailing lists,which are very active in identifying problems as well as reporting types of use. Each release of the MySQL Server has been usable. Problems have occurred only when users try code from the “grey zones.” The descriptions mostly deal with Versions 3.23 and later of MySQL Server. The MySQL Server design is multi-layered with independent modules. Some of the newer modules are listed here with an indication of how well-tested each of them is: • Replication (Stable)Large groups of servers using replication are in production use, with good results work on enhanced replication feature is continuing• In no DB tables (Stable)The in no DB transactional storage engine has been stable since version 3.23.49. In no DB is being using in large, heavy-load production systems. • BDB Tables (Stable)The Berkeley DB code is very stable, but we are still improving the BDB transactional storage engine interface in My SQL Server.• Full text searches (Stable)Full-text searching is widely used. Important feature enhancements were added in MySQL 4.0 and 4.1. • My ODBC 3.51 (Stable) My ODBC 3.51 uses ODBC SDK 3.51 and is in wide production use. Some issues brought up appear to be application-related and independent of the ODBC driver or underlying database server. The In no DB storage engine maintains In no DB tables within a table space that can be created from several files. This allows a table to exceed the maximum individual file size. The table space can include raw disk partitions, which allows extremely large tables. The maximum table space size is 64TB. The following table lists some examples of operating system file-size limits. This is only a rough guide and is not intended to be definitive. For the most up-to-date information, be sure to check the documentation specific to your operating system.

2.2 PRODUCT FEATURES

The Airline Reservation System has the following features:This project is mainly intended for two types of audiences. One is the customer or the end-user and the other is the administrator of the application. Some of the major functions of the product can be categorized under two different categories that are for the administrator and the user.

2.2.1 Customer / End user activities

Figure 1 - Customer use case diagram

The above use case diagram depicts all the functions or activities that a user or aCustomer can perform on the application. They can be discussed in detail as follows:

Home Page: Like all the other airline websites available online, the user can access the user home page of the Airline Reservation System, after he logs into the system. Here, he can look up information regarding flights.

Login and Register: The Airline Reservation System also comes with the customer registration details page, where the customer can enter his details and register.

Booking Flights: The customer can also search for the flights available and reserve his place onthe flight by purchasing a ticket..

Some of the functions of the Airline Reservation System, such as creating, maintainingand updating the database are available only to the administrator. The functions of theadministrator, explained in detail are as follows:

2.2.2 Administrator Activities

Login: The administrator has to login first in order to be able to make changes to the Airline Reservation System, by adding, deleting or modifying the data in the Airline Reservation System database.

Add/Modify Customer Information: Daily the Airline Reservation System will have many customers registering with the application and many of them unsubscribing. Only the administrator will have the sole rights to modify the database accordingly.

Add/Modify Flight Information: The Administrator also has the sole rights to add, delete or modify the flight information. Sometimes any flight information has to be modified or if any new flights need to be added to the database, these operations are performed by the administrator.

Figure 2 - administrator use case diagram

2.3 USER CHARACTERISTICS

There are two kinds of users for the Airline Reservation System. One is the customer andthe other is the administrator. The customers do not need to have any prior training to use the application. However, instructions for making flight reservations would be provided to them through application. The administrators would however need to be trained in order to use the application.

2.4 CONSTRAINTS

In case of changes made to the database, the application should be able to show theUpdated information without much delay. The database for the project is designed to be of moderate size.

The Airline Reservation system will be designed in such a way that, it can be run on a Windows 8 and its older versions. The Web Programming technology will be used to code the project and My SQL willact as the database for the project.

3. SPECIFIC REQUIREMENTS

3.1 EXTERNAL INTERFACES

The different types of interfaces that we would come across while developing the AirlineReservation System application are as follows:

• User Interface• Hardware Interface• Software Interface

3.1.1 USER INTERFACE

There are two types of users for the Airline Reservation System project. One is theCustomer and the other is the administrator. Both the customer and administrator user interface would be a graphical user interface. The graphical user interface for the customer home page would be as follows:

Figure 1

The Graphical User Interface would mainly consist of Hyperlinks Navigation Bar like the About Link etc.

3.1.2 ADMINISTRATOR INTERFACE

The administrator of the website would also have a similar Graphical User Interface.After an administrator logs onto the system, the home page for the administrator would be as follows:

3.1.3 SOFTWARE INTERFACE

The application should run on a Windows 8 and its older versions Operating System. Since the application needs a database to store all the customer details, airline My SQL server would be used.

DreamWeaver CS6 would be used for creating the application. All the coding willbe done in PHP,Java Script, CSS and HTML .

4. FUNCTIONAL REQUIREMENTS:

The functional requirements of the Airline Reservation System are divided among theCustomer and the administrator of the application.

These functional requirements can be explained in detail as follows:

4.1 Use Case name: User Registration

• Description: This use case describes the scenario where the user registers with theApplication by providing all the necessary details, in order to make reservations orBookings for flights.

• Actor: User or the Customer.

• Input: The user or the customer will have to provide all the necessary details present inthe customer registration form of the application.

4.2 Use Case name: User Login

• Description: This use case describes the scenario where the user logs into the application, with the username and password• Actor: User or the Customer• Input: The user or the customer creates a username and password He then uses them to logon tothe system and make reservations or view any information.

4.3 Use Case name: Book Flights

• Description: This use case describes the scenario where the user books airline tickets.• Actor: User or the Customer• Input: After logging into the application, the customer looks up the information relatedto various airlines and checks the availability of seats on flights. If he finds that there areany available tickets, he then purchases them.

4.4 Use Case name: Login/Logout

• Description: This use case describes the scenario where the administrator of the Application , logs into the system and logs out after the work is done.• Actor: Administrator• Input: The administrator logs into the application with the username and password provided to him.• Output: The application verifies the authenticity and displays the home page of theAdministrator.

4.5 Use Case name: Add/Delete or Modify Customer information

• Description: This use case describes the scenario where the administrator adds, deletes or modifies customer information in the system database

• Actor: Administrator• Input: The administrator of the applications logs onto the system with his username and password.• Output: The application authenticates the administrator, and then displays the page where the administrator can add new customers to the database, or delete existing customers or modify details of customers in the database.

4.6 Use Case name: Add/Delete or Modify flight information

• Description: This use case describes the scenario where the administrator adds, deletes or modifies flight information in the application database• Actor: Administrator• Input: The administrator logs onto the system with the username and password provided to him.• Output: The application authenticates the administrator, by verifying the username and password. Then the application displays the page where the administrator can add new flights to the database, delete the flights or modify information for the flights.

5. PERFORMANCE REQUIREMENTS

The Airline Reservation System application should be able to respond to the queries submitted by the customer without much delay. When a user searches for a flight leaving from a particular place to another place, the application should not take much time to return the results. Considering that the application is of moderate size, it should be able to display the results at a time on a page, when the customer looks up for any particular data.

Chapter: 02

Architectural Design

1. INTRODUCTION

The main purpose of the Architecture Design document is to discuss the architecturaldesign for the Airline Reservation System project in a clear and concise form. This design document will give a detailed description of the presentation tier, the middle tierwhich consists of the class diagrams, sequence diagrams for the Airline Reservation System and finally the data tier.

2. ARCHITECTURE OF THE AIRLINE RESERVATION SYSTEM

The architecture of the Airline Reservation System is based on the three-tier architecture.This three-tier architecture mainly consists of three layers namely:• Presentation Tier• Business Tier• Data Access Tier

The Presentation Tier converts and displays information into a human legible form. This tier displays information related to services such as browsing the Airline, purchasingtickets etc. It communicates with the other tiers by outputting results to the client tierand all the other tiers. The Business Logic tier is mainly responsible for information exchange between the user interface and the database of the project. The final layer of the three tiered architecture is the Data Access tier, which mainly consists of the Database servers. The information related to the Airline Reservation System is stored and retrieved from here.A simple representation of the three-tier architecture would be as follows:

PRESENTATION TIER

The presentation tier is the top most layer of the Airline-Reservation system application.The presentation tier is mainly responsible for the user interface of the application which deals with thepresentation of data to the user. The presentation tier of the Airline Reservation System is mainly formed by the HTML Pages. In the case of the Airline Reservation system project, I have used the PHP and ATML to create the pages. There are several Pages created for the user and the administrator.

BUSINESS LOGIC TIER

The Business Logic Tier is the middle tier of the three-tier architecture. The businesslogic for the Airline Reservation System would be present here. In the case of my project, the HTML classes would be performing the duty of the business logic. This is the layer which is responsible for the information exchange between the user interface and the database. The Airline Reservation system mainly consists of the Users, which can be further

classified into the customer and administrator of the Airline Reservation System.The class diagram for the Airline Reservation System would be as follows:

4.1) CLASS DIAGRAm

4.2) SEQUENCE DIAGRAM The sequence diagram for the Customer of the Airline Reservation System would be as follows:

DATABASE TIER

The database tier is the final and last tier of the three-tier architecture. All the data relatedto the Airline Reservation System project is stored and retrieved from here. For this project I have used the My SQL server to create the database. To be specific,My SQL server is being used. It is very easy to work with and makes creation and maintaining of tables very easy.

Chapter: 03

Component Design

1. INTRODUCTION AND PURPOSE

The main purpose of the Component Design document is to provide and explain thecomponent design for the Airline Reservation System project in detail.

2. CLASS DIAGRAM

The class diagram of the Airline Reservation System project would be as follows:

2.1 CLASS DESCRIPTION

2.1.1 CUSTOMERS

The attributes for the customers are Customer ID which is unique,Customer Name, Gender, Date of Birth, Address, State, Country, Contact number and Email- id.

The functions that the customer would be able to perform are :

Register – the customer would be able to register onto the systemLogin- the customer can login with the email id and passwordSearch flights and book flights – the customer would be able to search and book the flights available

2.1.2 COMPANY

The attributes for the customers are Companyid which is unique,Company Name, Address and Company URL.

The functions that the Administrator would be able to perform are Login- the Administrator can login with the email id and passwordRegister – the Administrator would be able to register new company.

2.1.3 FLIGHTS

The attributes for the flights are Flightid which is unique,Company Name, Companyid (referring tblcompany table) and status id.

The functions that the Administrator would be able to perform are:Login- the Administrator can login with the email id and passwordRegister – the Administrator would be able to register new flights depending upon the respective company.Flight status id- It depicts whether the flight is of domestic or international type.

2.1.4 FLIGHT FARE

The attributes for the flight fare are Flight fare id which is unique, Flight class status id (referring table tblflightclass status), customer status id (referring tblcustomerstatus table) ,fare id (referring table tblfare) and flight id(referring table tblfllights).

The functions that the Administrator would be able to perform are:Login- the Administrator can login with the email id and passwordAdd – the Administrator would be able to add flight fare depending upon the respective company and its class i.e. business or economy and customer status i.e. whether the customer is infant, child, adult or senior citizen.

2.1.5 FLIGHT SEATS

The attributes for the flight seats are Flight seat id which is unique, Flight class status id (referring table tblflightclass status), flight route id (referring table tblroutes), seatno.

The functions that the Administrator would be able to perform are :Login- the Administrator can login with the email id and passwordAdd – the Administrator would be able to add flight seats depending upon the respective company and its class i.e. business or economy accordingly to Source and Destination.

2.1.6 FLIGHT ROUTES

The attributes for the flight route are Flight route id which is unique, Departure time, Arrival time, Flight Days, route id (referring table tblroutes) and Flight id (referring table tblflights).

The functions that the Administrator would be able to perform are:Login- the Administrator can login with the email id and passwordAdd – the Administrator would be able to add flight routes depending upon the respective company flights and accordingly to Source and Destination along with their departure and arrival time.

2.1.7 FLIGHT BOOKING

The attributes for the flight route are PNR status id which is unique, customer id (referring table tblcustomers), flight seat id (referring table tblflightseats) , flight fare id (referring table tblflightfare), flight route id (referring table tblflightroutes) and Date of Booking of flight.

The functions that the Customer would be able to perform are:Login- the Customer can login with the email id and passwordBook – the Customer would be able to book flight depending upon the respective company flights available and accordingly to Source and Destination along with their departure and arrival time and accordingly to class type i.e. business or economy and availability of flight on that booking date.

Chapter: 04

Test Plan

1. TEST PLAN IDENTIFIER

Airline Reservation System

2. INTRODUCTION

The main purpose of the test plan for the Airline Reservation System is to discuss thetesting details of the use cases of the Airline Reservation System. The software project test plan also describes the objective, scope and approach of the software testing effort for the Airline Reservation System project. The test plan for the Airline Reservation System also indicates the personnel responsible for each task and also specifies the risks associated with the test plan.2.1SYSTEM TESTING AND IMPLEMENTATION.

System testing: Theoretically, a new designed system should have all the pieces in working order, but in reality, each piece works independently. Now is the time to put all pieces into one

system and test it to determine whether it meets the user’s requirements. The purpose of the system is to consider all the likely variations to which it will be subjected and then push the system to its limits. It is tedious but necessary step in system development. One needs to be familiar with the following basic terms.

UNIT TESTING: Unit Testing is testing changes made in an existing or a new program.

SEQUENTIAL OR SERIES TESTING: Sequential or Series Testing is checking the logic of one or more programs in the candidate system, where the output of one program will affect the processing done by another Program.

SYSTEM TESTING: System Testing is executing a program to check logic changes made in it and withthe intention of finding errors making the program fail.

ACCEPTANCE TESTING: Acceptance Testing is running the system with live data by the actual user of the system. Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. In adequate testing or no-testing leads to errors that may not appear until months later. Another reason for system testing is its utility as a user-oriented vehicle beforeimplementation. The best program and the user have communication barriers due to different backgrounds.

The system tester (designer, programmer, or user) who has developed some computer mastery can bridge this barrier. Unit Testing: This focuses on the smallest unit of software design. The module using the details designdescription as a guide; important control paths are tested to uncover errors within the boundary of the module. Unit test consideration: The module interface id tested to ensure that information properly flows into and out of the program unit under test. The local data structures are examined to ensure that the data stored temporarily maintains it integrity during all steps in an algorithm execution. Boundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing. The test of data flow across a module interface is required before any other test. If data do not enter and exit properly, all other tests are moot.Unit Procedure: Unit test is normally considered adjunct to the coding style.After source level code has been developed, reviewed and verified for correct syntax, unit test case design begins. Each test case should be coupled with a set of expected results.

Normally, a driver is a “main program” that accepts test case data, passes such data to the module to betested and prints the relevant results. Stubs serve to replace modules that are subroutines called by the

module to be tested. A Stub or ‘dummy stub program’ uses the subroutine module’s interface to do minimal data manipulation and returns.

On the completion of each set of test, another stub is replaced with the real module.

Registration Testing: Registration Testing is conducted to ensure that new errors have not been introduced. During the implementation phase it is important that all staff concerned be apprised of the objectives of overall operation of the system. They will need shinning on how computerization will change their duties and need to understand how their role relates to the system as a whole. An organization-training program is advisable; this can include demonstrations, newsletters, seminars etc. The department should allocate a member of staff, who understands the system and the equipment, and should be made responsible for the smooth operation of the system. An administrator should coordinate the users to the system. Users should be informed about new aspects of the system that will, affect them. The features of the system explained with the adequate documentation. New services such as security, on-line application from the back-ups must be advertise on the staff when the time is ripe. Existing documents such as employee loan details should be entered intothe new system. Since these files are very large, conversion of these may continue long after the systembased on current files has been implemented. Hence we need to assign responsibility for each activity. The system may come into full operation via number of possible routes. Complete change over at one point time is conceptually the most tidy. But this approach requires careful planning and coordination, particularly during the changeover. A phased approach, possible implementing the system of the section relating to one operation or procedure first and processing to more no velor complex subsystems in the fullness of time. These likely to be less traumatic .A phased approach gives the staff time to adjust to the new system. But depends on being able to split the system, without reliance on it. Thus approach is sensible when the consequences of failure are disastrous, but will require extra staff time. The fourth angle, is pilot operation permits any problems to be tackled on a smaller scale operation. Pilot operation generally means the implementation of the complete system.

2.2 OBJECTIVES

The main objectives of the test plan for the Airline Reservation System are as follows:• To identify the features of the system that will be tested.• To identify and define all the activities necessary to prepare for and conduct the testingprocess on the Airline Reservation System• To discuss the testing techniques being used to test the Airline Reservation System.

2.3DEFINITIONS

The following are some of the terms and definitions that are related to the test plan of theAirline Reservation System:• Pass/Fail criteria:

Decision rules that are used to determine whether a software itempasses or fails a test.• Test: A collection of one or more test cases• Test Item: A software item that is an objective of testing.• Test Plan: A document describing the scope, approach, resources and schedule of theintended testing activities.• Test Summary Report: A document summarizing the testing activities and results.• Testing: The process of analyzing a software item to detect the differences between the existing and required conditions.

3. TEST ITEMS

This section of the test plan lists all the items of the Airline Reservation System projectthat will be tested:• Login• Search and book flights• Register

4. APPROACH

This section of the test plan describes the overall approach for testing the AirlineReservation System project. The approach followed for testing the Airline Reservation System ensures that the major features of the project are adequately tested. The testing would be carried out on the Airline Reservation System while logging into the system as a customer or a normal user of the system.

4.1 UNIT TESTING

The Unit Testing is a test that tests each single module of the software to check for errors.This is mainly done to discover errors in the code of the Airline Reservation System. The main goal of the unit testing would be to isolate each part of the program and to check the correctness of the code. In the case of the Airline Reservation System, all the pages will be tested. There are many benefits for this unit testing:• The unit testing facilitates change in the code.• It allows testing to be done in a bottom up fashion.At the same time, unit testing has some disadvantages such as, it might not identify eachand every error in the system.

4.2 INTEGRATION TESTING

In Integration Testing, the individual software modules are combined and tested as awhole unit. The integration testing generally follows unit testing where each module is tested as a separate unit. The main purpose of the integration testing is to test the functional and performance requirements on the major items of the project.All the modules of the project developed individually would be combined together andtested as a whole system in the integration testing.

4.3 REGRESSION TESTING

The Regression Testing is generally done whenever modifications are made to the sourcecode of a project. The Regression Testing can also be defined as the process of testing changes made to the computer program and also makes sure that the older programming still works with the new changes.

So, before any new version of a software product is released, the old test cases for the project willbe run against the software with the changes made, to make sure that the old functionalities of the project still work.

4.4 ACCEPTANCE TESTING

This testing is generally performed when the project is nearing its end. This test mainlyqualifies the project and decides if it will be accepted by the users of the system. The users or the customers of the project are responsible for the test.

4.5 SYSTEM TESTING

The system testing is mainly done on the whole integrated system to make sure that theproject that has been developed meets all the requirements. The test cases for the system testing will be the combination of unit and integration tests.

5. TEST CASES

The following are the test cases for the Airline Reservation System:

5.1TEST CASE 1 – USER LOGIN

• Incorrect Input: Incorrect username, which is the email-id in the case of the AirlineReservation System.• Pass Criteria:

An appropriate message should be generated to indicate that an invalid username has been typed.• Correct Input: The correct input would be a valid e-mail id of the user and a correctpassword associated with the email-id which he uses to log in.

5.2 TEST CASE 2 – USER REGISTRATION

• Incorrect Input: Wrong format entered in the input fields for the registration page.• Pass Criteria: An appropriate message should be generated to the user saying that he has entered the wrong format in the specific input field.• Correct Input: The correct input would a correct format entered by the customer into the input fields of the registration page.• Pass Criteria: The pass criteria for this test case would be a successful registration of the customer into the Airline Reservation System.

5.3 TEST CASE 3 – USER REGISTRATION

• Incorrect Input: The data fields left out empty in the registration page.• Pass Criteria: An error message should be generated to the user saying that he has to fill out those fieldsin order to be registered into the system.• Correct Input: The correct input in this case, would be that the customer would enter the data in all the fields in the registration form.• Pass Criteria: The pass criteria for the system would be that it accepts all the customerdetails and then registers the customer and helps him log into the system.

5.4 TEST CASE 4 – SEARCH AND BOOK FLIGHTS

• Incorrect Input: Incorrect input in this case, would be incorrect search criteria entered or incorrect format of data entered into the data entry fields of the flight search and booking page.• Pass criteria: A message has to be generated to the user indicating the wrong entry thathe has made in the fields.• Correct Input:

A correct input would be entering the data into the data entry fields in acorrect format.• Pass Criteria: The pass criteria for this test case would be that the search would returnvalid results and then when the customer made the booking, the system has to generate aConfirmation to the customer by displaying the message.

6. PASS OR FAIL CRITERIA

The test cases executed on the Airline Reservation System will pass if they meet thespecific requirements mentioned in the Vision document of the project. A test case is said to fail, if the desired functionality is not satisfied by the system.

7. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS

7.1 SUSPENSION CRITERIA

Testing for all the dependant features will be suspended if a test case fails. The failed testcase will be logged onto the test log which contains the description for the error.

7.2 RESUMPTION REQUIREMENT

The test cases which are not dependant on the case where the bug is reported will beexecuted in parallel with the bug fixing. Once the failed test case has been taken note of and has been identified and fixed then the testing for the failed test case will resume.

8. TEST DELIVERABLES

The following documents will be produced after the testing phase for the AirlineReservation System has been completed.• Test Plan• Test Cases• Test Log

Chapter: 05

Assessment Evaluation

1. INTRODUCTION

The Assessment Evaluation document presents the results obtained by testing the AirlineReservation System. The test cases are in reference to the test cases defined in the Test Plan document from the Phase II.

2. TEST CASE RESULT SUMMARY

The summary of the test case result has been depicted in the table shown below:These are the test cases for the User/Customer pages. The major part of testing has beenconcentrated on the customer pages, as they would be the main clients of the Airline Reservation System.

The below table represents the summary of results of testing on the Administrator pages.The results have been explained in detail later in the document.

3. DETAILED TEST RESULTS

3.1MANUAL TESTING

To start with, I have performed manual testing on the Airline Reservation System Manual Testing is one of the oldest and rigorous methods of software testing. Thistesting strategy gives the bestopportunity to check every page thoroughly and make sure it works in the expected manner. Due to the complexity of the various automation tools and the time available for testing the entire application, I preferred to use manual testing based on the fact that it is one of the best methods of testing suggested for a beginner.All the test cases mentioned in the Test Plan document of Phase II were tested here. Theresults of the manual testing are represented in the following tables:

3.1.1 TC # 1 – USER LOGIN

3.1.2 TC # 2 - USER REGISTRATION

3.1.3 TC # 3 – SEARCH AND BOOK FLIGHTS

3.1.4 TC # 6 - ADMINISTRATOR SIGN IN

3.1.5 TC # 7 – NEW FLIGHT ADDITION

3.1.6 TC # 8 – UPDATING FLIGHT DETAILS

Thus, the Administrator forms have also passed the manual testing phase and thusthe above results have been produce

Chapter: 06

User Manual

1. INTRODUCTION

The User Manual explains us the step by step procedure to use the Airline Reservation System application.

2 REQUIRED SOFTWARE

The required software for the Airline Reservation System project would be as follows:

• Operating System: Microsoft Windows 8 or lower.• .Dreamweaver CS6:

It can be downloaded from Microsoft website (http://www.microsoft.com/en-in/download/details.aspx?id=3324).• Microsoft My SQL server: It can be downloaded from Microsoft website (http://www.microsoft.com/en-in/download/details.aspx?id=35575).

2 AIRLINE RESERVATION SYSTEM DETAILED VIEW

Administrator Login Page

Customer Login Page

http://www.microsoft.com/en-in/download/details.aspx?id=3324




Administrator Main Page

The administrator can perform the following functions likeAddition of new companiesAdd new flightsCan modify the customers Add flight seatsAdd flight routesAdd flight fare

Add New Company Pany

Add Customer page

Flight Routes Page

Customer Main Page Flight Book Page

The customer can perform the following functions like

Can register it. Add flight according to its need

Appendix A: List of Tools:• Microsoft Windows 8• HTML• Js• Adobe Photo Shop CS6

• CSS• Microsoft Paint• PHP web development platform: Adobe Dreamweaver CS6• MySQL as relational database• XAMPP 1.8.3• PhpMyAdmin5.5.1

Appendix B: Referenceshttp://en.wikipedia.org

Wikipedia is a free encyclopedia, written collaboratively by the people who use it. It is a special type ofwebsite designed to make collaboration easy, called a wiki.

http://msdn.microsoft.com

The Microsoft Developer Network (MSDN) is the portion of Microsoft responsible for managing the firm's relationship with developers and testers, such as: software developers standing on the various OS platforms or using the API languages of applications.

http://www.oracle.com

An Oracle is a large corporative website. We used this website for learning tutorials and download development products from there in order to use it in the game development.

Online Airline Reservation Systemdocshare02.docshare.tips/files/30520/305206296.pdf · TheAirline...

Documents

Transcript of Online Airline Reservation Systemdocshare02.docshare.tips/files/30520/305206296.pdf · TheAirline...