Académique Documents
Professionnel Documents
Culture Documents
1. INTRODUCTION
1.1. PURPOSE
The main purpose of this software is to reduce the manual errors involved in the airline
reservation process and make it convenient for the customers to book the flights as when they
require such that they can utilize this software to make reservations, modify reservations or
cancel a particular reservation.
1
1.2 SCOPE
OS-Operating System
RAM-Random Access Memory
MB-Mega Bytes
GB-Giga Bytes
Mbps-Mega bits per second
1.4 REFERENCES
The books and materials referred during the pre-development stages of the project include
2
1.5 OVERVIEW
The rest of the document deals about all the main features of this software each will its purpose
and its main functions. It also gives details about the interface with other products and related
functionality of each product.
2. OVERALL DESCRIPTION
The client systems should be able to share the data available in the data base through the
network connection.
3
2.1.5 Communication Interfaces
There is an LAN used for communication among the different client systems to be used.
The system would require disk space of 10 GB and a 256 MB HDD and 64 MB RAM for client
systems.
2.1.7 Operation
The users can first make a reservation in a particular flight for a particular date and time. The
system provides the customer with a pin code which gives him access to either make any
changes in his reservation or cancel a reservation. These must also be back up of data to enable
any easy recovery from any features.
The “ARS” software is an independent and self-contained product and no modification are
required to adapt to a particular installation.
4
2.4 CONSTRAINTS
Regulatory policies: It is a mandatory that no text book must be left empty or contains
insufficient data.
Hardware limitations: There must be a 64 MB on board memory
Control functions: The software must be very user-friendly and display appropriate
error messages.
Interfaces to other applications: Not applicable.
Parallel operations: It must support many users simultaneously.
Reliability requirements: Data redundancy and use of special/blank characters must be
avoided.
Safety/security considerations: The application must be exited always normally.
Higher order language requirements: VB
It is assumed that the details of the cost of ticket are already known to the customer. Future
changes like providing different types of flights with different classes like business class,
economic class will allow the customers to benefit from one facility.
The necessity of providing options to customer to choose their seat or to choose for economic
or business class can be delayed until future versions of the software are developed.
5
3. SPECIFIC REQUIREMENTS
The system must basically support certain input and output devices. Their descriptions are as
follows.
6
Printer To print the bookings mode Destination of Output
E.g.: Destination chosen
with date and timings
3.2.1 FEATURE 1
The ability of the software is to provide the details of the flights available and allow the
customers to choose a particular destination and make a reservation.
3.2.1.1 PURPOSE
The purpose of this is to enable the users to view the different flights available so as to
make it convenient for him to make a reservation.
3.2.1.2 STIMULUS/RESPONSE
Once the user chooses the particular option, the web pages corresponding to that are to
be displayed on the screen i.e., it will display the different flights available to their
respective destinations and allow the customer to book a ticket.
7
3.2.1.3.1 FUNCTIONAL REQUIREMENTS
Once the user makes a reservation, he must be provided with a pin code.
3.2.1.3.1.1 INTRODUCTION
The user must be provided with the required information within 10 seconds.
3.2.1.3.1.2 INPUTS
The user must enter the destination with date and timings and must make
reservation by giving his personal details like name, address, age, gender,
nationality.
3.2.1.3.1.3 PROCESSING
3.2.2 FEATURE 2
The software allows the user to modify an already existing reservation made by the
customer if in case there are any changes that are to be modified in the reservations of
the ticket.
3.2.2.1 PURPOSE
The purpose is to allow the customer to make any changes in his personal details or
flight booking details.
3.2.2.2 STIMULUS/RESPONSE
Once the user requests for changing his reservation, it must be displayed on the screen
prompting the customer to enter his pin code.
8
If the pin code provided by the customer does not match, then would notify the
person by displaying error messages.
3.2.2.3.1.1 INTRODUCTION
The system will allow the customer to modify his reservation provided correct
pin code has been entered by him.
3.2.2.3.1.2 INPUT
The user should enter his pin code which gives him access to modify his
reservation.
3.2.2.3.1.3 PROCESSING
The pin code is processed and checked for his validity. If it is correct then the
user can modify his reservation else an error message will be displayed asking
the user to enter the correct pin code number.
3.2.2.3.1.4 OUTPUT
Given the correct pin code, the user can now modify his reservation. A new pin
code will be generated for the customers.
3.2.3 FEATURE 3
The software allows the user to cancel an already existing reservation made by the customer
who has booked the ticket.
3.2.3.1 PURPOSE
The purpose is to allow the customer to cancel his reservation if not required.
3.2.3.1 STIMULUS/RESPONSE
Once the user requests for canceling his reservation, it must be displayed on the screen
prompting the customer to enter his pin code.
9
3.2.3.3 ASSOCIATED FUNCTIONAL REQUIREMENTS
If the pin code provided by the customer does not match, then it would notify
the person by displaying error messages.
3.2.3.3.1.1 INTRODUCTION
The system will allow the customer to cancel his reservation provided correct
pin code has been entered by the customer.
3.2.3.3.1.2 INPUT
The user should enter his pin code which gives him access to cancel his
reservation.
3.2.3.3.1.3 PROCESSING
The pin code is processed and checked for its validity. If it is correct, then the
user can cancel his reservation else an error message will be displayed asking
the user to enter the correct pin code number.
3.2.3.3.1.4 OUTPUT
Given the correct pin code, the user can now cancel his reservation.
3.2.4 FEATURE 4
The software must also give a report on the number of reservations made for a particular flight.
10
3.2.4.1 PURPOSE
The purpose is to enable the administrator to view the number of people in a particular
flight.
3.2.4.2 STIMULUS/RESPONSE
Once the user requests for this option, all the details of the customers who have made
reservation will be displayed.
3.2.4.3.1.1 INTRODUCTION
The system will allow the administrator to view all the details of the customer
who have made reservations.
3.2.4.3.1.2 INPUT
The administrator must enter the password so that access is given only to him
to view the details of all the customers.
3.2.4.3.1.3 PROCESSING
The password is processed and checked for its validity. If it is not correct, then
the administrator is asked to enter the correct password.
3.2.4.3.1.4 OUTPUT
Given the correct password, the administrator can view all the details of
customers with date and time of their bookings made.
11
3.3 PERFORMANCE REQUIREMENTS
At any instant, a maximum of four nodes or users will be given access simultaneously.
Since the program handles multiple users, if more than one person attempts to same
date to the files stored in the data base, the program will lock the data file using a 2-
phase commit protocol to prevent simultaneous access.
3.5.2 Reliability
The factors needed to establish the software expected reliability are
The user inputs should be valid and within the given range.
Normal termination of the program.
3.5.2 Availability
The factors guarantee the software’s availability includes proper termination and correct input
details. Also the resources used for the project development are Microsoft Certified which
speaks of its high quality standards.
3.5.3 Security
It must be ensured that access will be provided to the authorized persons through user
ID and password.
Network security will be provided by the use of firewalls.
12
Checks can be performed at regular internals to ensure data integrity.
3.5.4 Maintainability
The software will be developed by implementing the concept of modularity which in turn
reduces the complexity involved in maintaining it. The administrator should have a sound
technical knowledge about maintaining the software and further enhancements will be
undertaken by the developer.
3.5.5 Portability
The application is portable which ensures its adaptability for use on different computer
terminals with different operating systems and standards.
The system requires the use of text files to maintain the customers personal details and his
booking details. An entity must be used to specify the various departments and the seats
available in them. This information will be used frequently by the authorities for verification.
TESTCASE
We have two type of test case techniques
1. Test Scenarios
2. Test Case.
1. Test Scenarios :
1. Verify that there is portal to add new flights in the sytem.
2. Verify that on filling flight details like flight name, code, from and to destinations, capacity,
timings and frequency etc, new filghts get successfully added in the system.
13
3. Verify that user can search for flights by name, from-to airports or flight code for checking
their status and timings.
4. Verify that search results have flight details, timings and availability.
5. Verify that clicking the search results open complete details for flight.
6. Verify that user should see realtime flight status of availability of seats.
7. Verify that user is presented with graphical view of the airline's sitting arrangement along
with seat number and availability status.
8. Verify that pricing of different types of seats is displayed to the users.
9. Verify that user can successfuly select single or more than one seat.
10. Verfiy that user cannnot select or is not permitted to select seats that are already booked or
not allowed for booking.
11. Verify that after selecting seats, entering passenger details and making payment the selected
seats get booked.
12. Verify that on successful booking the ticket should be visible and downloadable.
13. Verify that after successful booking the seat's stuatus is updated to booked.
14. Verify that user also receive confirmation mail along with tickets on the emailIds provided
while filling the details.
15. Verify the maximum limit of seats that a user can book, selecting more seats than permiited
results in error message.
16. Verify that all the different types of payment methods work fine.
17. Verify that user is presented with additional options like- luggage, extra leg room,
foods/beverages etc and selecting the same results in additional cost with the booking
amount.
18. Verify that user can also cancel the tickets booked by entering the mandatory details and
the amount after deducting the cancellation fee gets refunded back to user.
19. Verify that after cancellation the seat's status is updated to available.
2. TEST-CASE:
The summary of the test case result has been depicted in the table shown below:
14
These are the test cases for the User/Customer pages. The major part of testing has
been concentrated 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.
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. This
testing strategy gives the best opportunity 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:
15
16
17