Amrita School of Computing, Chennai

19CSE314 – Software Engineering

Lab Manual

Prepared By
Dr.P.DHAVAKUMAR
 LIST OF EXPERIMENTS

1. Feasibility study for any application.

2. Project Planning for the above application.

3. Software requirement analysis for the above application.

4. Write SRS for any the above application.

5. Create traceability matrix for the above application.

6. Draw use-case, class for the above application.

7. Draw sequence and collaboration diagram for the above application.

8. Draw activity and state chart for the above application.

9. Component, package and deployment diagram for the above application.

10. Generate and Implementation of skeleton code for the above application

11. Writing test cases for the above application.

12. Testing process for the above application

 AIRLINE RESERVATION SYSTEM

Feasibility Study Report

Ex.No. 1
Date :
Aim : To write feasibility study report for Airline Reservation System.

Need of Airlines system

A few factors that directs us to develop a new system are given Below:
1) Faster System
2) Accuracy
3) Reliability
4) Informative
5) Reservations and cancellations from anywhere to any place.

FEASIBILITY STUDY
Feasibility study is to check the viability of the project under consideration. Theoretically
various types of feasibilities are conducted, but we have conducted three type of feasibilities
explained as under.

ECONOMIC FEASIBILITY
With the manual system the operating cost of the system is about 60 Lacks P.A... This cost
comprises salary of 25 people, stationary, building rent, electricity, water, telephone etc. But with the
new system this reoccurring cost comes out to be about 20 lacks P.A. Hence the new system is
economically feasible.

TECHNICAL FEASIBILITY
The new application requires only 6 trained people to work with the system and in
overall 10 people per office is sufficient. So we will identify 6 best people from existing system and
train them. As our existing system is purely manual, so we need a onetime investment of Rs 4 Lacks
for the purchase of 7 computers, 5 Ticket printers, a laser printer, AC and networking etc. It requires
20 Lacks PA as a operating cost. With the above details our system is technically feasible as after
investing 24 lacks in a year, the company is still saving Rs 25 Lacks PA.

OPERATIONAL FEASIBILITY
The new solution is feasible in all sence but operationally it is not. The new system
demands the expulsion of at least 15 people from the company. It creates an environment of
joblessness and fear among the employees. It can lead to an indefinite strike in the company also. So
the management must take corrective actions prior in advance in order to start the further
proceedings.
Result : Thus the feasibility study report prepared.
 Project Planning
Ex.No. 2

Date :

Aim : To prepare Gantt chart (project planning) for Airline reservation systems.

Project Planning:
Computer hardware and software project planning within an enterprise is often done using a
project planning guide that describes the process that the enterprise feels has been successful in the
past.

Procedure :

Step 1: Identify & Meet with Stakeholders

Step 2: Set & Prioritize Goals.
Step 3: Define Deliverables.
Step 4: Create the Project Schedule.
Step 5: Identify Issues and Complete a Risk Assessment.
Step 6: Present the Project Plan to Stakeholders.

Result :
Thus we developed project plan successfully.
 Requirement Analysis
Ex.No. 3
Date :

Aim : To analyze software and hardware analysis in the airline reservation systems.

Hardware requirement :

The airline reservation system needs the following hardware

1. Windows.
2. A browser which supports CGI, HTML & Javascript.

Software requirement :

The airline reservation system needs the following software

1. Front-end software: Vb.net version

2. Back-end software: SQL+

Software Interfaces :

Following are the software used for the flight management online application. <<Include the
software details as per the project >>
Software used Description

We have chosen Windows operating system for its best

Operating system support and user-friendliness.

To save the flight records, passengers records we have chosen

Database SQL+ database.

To implement the project we have chosen Vb.Net language for

VB.Net its more interactive support.

Result :
Thus, the software and hardware requirements are analyzed.

SOFTWARE REQUIREMENTS SPECIFICATION

Ex.No. 4

Date :

Aim : To design the software requirement specification for Airline Reservation System.

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.2 SCOPE
The name of the software is “AIRLINE RESERVATION SYSTEM”. This software provides
options for viewing different flights available with different timings for a particular date and
provides customers with the facility to book a ticket, modify or cancel a particular reservation but it
does not provide the customers with details of cost of the ticket and it does not allow the customer to
modify a particular part of his reservation and he/she can modify all his details.

1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

 ARS-Airline Reservation System

 LAN-Local Area Network
 GUI-Graphical User Interface
 OS-Operating System
 RAM-Random Access Memory
 MB-Mega Bytes
 GB-Giga Bytes
 Mbps-Mega bits per second
 HDD-Hard Disk Drive

1.4 REFERENCES

The books and materials referred during the pre-development stages of the project include
1. Software Engineering-A Practitioner’s Approach by Roger S. Pressman
2. Software Engineering-By James Peters
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

2.1 PRODUCT PERSPECTIVE

The “ARS” software is an independent application. It is a self-contained product. The
system interfaces, user interfaces and hardware interfaces related with this software are defined as
follows.

2.1.1 System Interfaces

The client systems should be able to share the data available in the data base through the
network connection.

2.1.2 User Interfaces

The screen formats and menu structure should be in such a way that even have users will
find it easy to use. The product must be use-friendly and very inter-active. The functionality
provided by the system like displaying error messages should adapt itself to the different users of the
software.

2.1.3 Hardware Interfaces

Nil

2.1.4 Software Interfaces

Name of the language: Visual Basics

2.1.5 Communication Interfaces

There is an LAN used for communication among the different client systems to be
used.

2.1.6 Memory Constraints

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.
2.1.8 Site Adaptive Requirements
The “ARS” software is an independent and self-contained product and no modification
are required to adapt to a particular installation.

2.2 PRODUCT FUNCTIONALITY

The major functions include
 Providing flight details
 Flight bookings for a particular destination, date and time and also providing with a pin code.
 Allowing the customer to modify or cancel his reservation provided the correct pin code is
given.
 Displaying a report of the number of people flying in a particular flight.

2.3 USER CHARACTERISTICS

No technical experience is required basic knowledge of handling system is sufficient.

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

2.5 ASSUMPTIONS AND DEPENDENCIES

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.

2.6 APPORTIONING OF REQUIREMENTS

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.

3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENTS
3.1.1 User Interfaces
The interface must be easy to understand. The user interface includes
 SCREEN FORMATS/ORGANIZATION: The introductory screen will be the first to be
displayed which will allow the users to choose either of the two options, viewing flight detail
or booking a ticket.
 WINDOW FORMAT/ORGANIZATION: When the user chooses some other option, then
the information pertaining to that choice will be displayed in a new window which ensures
multiple windows to be visible on the screen and the users can switch between them.
 DATA FORMAT: The data entered by the users will be alpha numeric.
 END MESSAGES: When there are some exceptions raising error like entering invalid
details, then error messages will be displayed prompting the users to re-enter the details.

3.1.2 Hardware Interfaces

The system must basically support certain input and output devices. Their descriptions
are as follows.
Name of Item Description of Purpose Source of Input/
Description of output
Key board To accept data from user like pin code, Source of Input
personal details, flight details
Printer To print the bookings mode E.g.: Destination of Output
Destination chosen with date and timings

3.1.3 Software Interfaces

Not applicable since the product under considerations is an independent one.

3.1.4 Communication Interfaces

Every client system connected through LAN establishes a communication only with the
server and not with any client system. An LAN of 10 Mbps is used.

3.2 SOFTWARE PRODUCT FEATURES

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.

3.2.1.3 Associated Functional Requirements

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
Recognizing the correct details are entered that a message is displayed confirming his
reservation and displays the pin code.

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.
3.2.2.3 Associated Functionality Requirements

3.2.2.3.1 Functional Requirements

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.

3.2.3.3 Associated Functional Requirements

3.2.3.3.1 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.

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 Associated Functional Requirements

3.2.4.3.1 Functional Requirements
If no reservations are made, then a message is displayed that no bookings have been made.

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.

3.3 NON-FUNCTIONAL REQUIREMENTS

3.3.1 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.3.2 LOGICAL DATABASE REQUIREMENTS

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.
3.3.3 DESIGN CONSTRAINTS
 Requires 256 MB on-board memory.
 Based completely on Windows functionality platform.
 The software should be portable and must be inaccessible to unauthorized users.

3.3.4 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.3.5 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.3.5 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.
 Checks can be performed at regular intervals 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.

4. FUTURE REQUIREMENTS

Support for waiting list functionality and ARS shall be made more flexible in ticket
reservation handling, and shall accept waiting list for reservation. The waiting list handling
capability of ARS 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. The telephonic interface of the ARS shall be improved
to support more functionality like allowing the customers to cancel a ticket etc., by incorporating
security measures.
ARS 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. Information
about the kind of meals served in a flight and the type of detrainment offered on a flight should be
incorporated into the system.

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 ARS shall be able to handle
the situation where flight services are available to multiple airports in a single city.

Ex.No. 5
Date :
Aim: To create and clear traceability relationship from a matrix view.

Steps:

Step 1: First create a project in the MS office Excel.

Step 2: Type Business Requirement Document (BRD) in one sheet.

Step 3: Type Functional Specification Document (FSD) in another sheet

Step 4: In third sheet fill needed requirements with a parent node and is respective child.

Step 5: Relate BRD and FSD to form traceability matrix screen.

Step 6: Now the traceability matrix is created.

 Traceability Matrix
Business Requirement Document (BRD)

Functional Specification Document (FSD)

Result :

Thus, the traceability matrix created successfully.

 UML DIAGRAMS
Ex.No. 6

Date :

Aim : To identify the use-case and actor and to draw class diagram for Airline Reservation System.

USE CASE DIAGRAM

Microsoft visual basic 6.0 is used as the front-end for our project and ms-access is used as the
back-end.
Use-case diagram
The online ticket reservation system uses the following use cases:
1. Login
2. Book ticket
3. Print ticket
4. Cancel ticket
5. View flight
6. Add flight
7. Delete flight
8. Logout
Actors involved
1) Administrator
2) Passenger
 Login

Date
Enquiry

Reservation Type Administrator

Reserve Ticket
Required Flights
Passenger Update Flight Details
Cancel Ticket
issue Ticket

Print Ticket

Data Base

Logout

Aim : To design class diagram for Airline Reservation System.

CLASS DIAGRAM:

The class diagram is a graphical representation of all the classes used in the system and their
operations, attributes and relationships.
 Flight no
Flight Status
flight name : string
Flight capacity : integer
Flight company : string
available seats : integer
add()
view()
delete()

Availability
Flight Details flight name : string
Ticket System flight name : string flight no : integer
flight company : string available seats : integer
user name : string
Flight cost : integer class : string
Password : string
flight Capacity : integer cost : integer
login() date : date
add()
logout()
view() add()
delete() view()

Ticket
ticket no : integer
passenger name : string reservation cancellation
flight no : integer Passenger Details
from : string name : string Flight no : integer flight no : integer
to : string gender : string date : date date : date
date : date address : string from : string from : string
departure time : integer contact no : integer to : string to : string
arrival time : integer email id : string
cost : integer view() view()
get data() book ticket() cancel ticket()
add() view()
view()
delete()
print()

Result :

Thus the use-cases are identified and class diagram generated successfully.
 SEQUENCE & COLLABORATION DIAGRAM:
Ex.No. 7

Date :

Aim : To design sequence, collaboration diagrams of Airline Reservation System.

A sequence diagram represents the sequence and interactions of a given usecase or scenario.
Sequence diagrams can capture most of the information about the system. Most object-to-object
interactions and operations are considered events and events include signals, inputs, decisions,
interrupts, transitions and actions to or from users or external devices.

Passenger Ticket Availability Flight Details Ticket issue database

System

Login(Enter ID or pwd)

check valid user or not

Login success or error

check availability
view flight details

view flightdetails acknowledgement

select reservation details add()

print acknowledgement tickets

modify reservation details

send acknowledgement details

transfer relevant information

store & update details

acknowledgement report

cancel or delete ticket

send cancelled acknowledgement

Log out system

COLLABORATION DIAGRAM:

2: check valid user or not

Passenger 1: Login(Enter ID or pwd)

Ticket
3: Login success or error System
6: view flightdetails acknowledgement
4: check availability

5: view flight details

Flight
Details 8: print acknowledgement tickets
10: send acknowledgement details
15: send cancelled acknowledgement Availability

16: Log out system

7: select reservation details add()

9: modify reservation details
14: cancel or delete ticket
12: store & update details

11: transfer relevant information

Ticket database
issue
13: acknowledgement report

Result :
Thus the class diagram designed and collaboration diagram generated.
 ACTIVITY & STATE CHART DIAGRAM:
Ex.No. 8
Date :

Aim : To design activity and state diagrams of Airline Reservation System.

Activity Diagram :

Activity diagram is to describe the dynamic aspects of the system. Activity diagram is

basically a flowchart to represent the flow from one activity to another activity. The activity can be
described as an operation of the system.

ACTIVITY DIAGRAM:

Login

NO check
yes valid user
Enquiry about
Login Flight Details
Failure

View Flight Cancell

Reservation
Deatils ation

View Ticket Cancel

detail Reservation Ticket
State diagram:

State diagram is an illustration of the states an object can attain as well as the transitions
between those states in the Unified Modeling Language (UML)

Login

Enquiry

Flight source Destination Date Availability

Name

Request
Ticket

Enter Passenger
Details

Name Age Gender Source destination

Ticket
issuse

Logout

Result :

Thus, the activity and state diagram was successfully completed.

 COMPONENT, PACKAGE AND DEPLOYMENT DIAGRAM
Ex.No. 9
Date :

Aim : To draw Component, package and deployment diagram for Airline Reservation System.

Component Diagram :

A component diagram depicts how components are wired together to form

larger components or software systems. They are used to illustrate the structure of arbitrarily
complex systems.

COMPONENT DIAGRAM:

Passenger
Data Access Enquiry Access ctrl Security
Enquiry Encryption

Data Access Flight

Details
Administrator Persistence
Update
Main Persistence
Server

Data Access
Resevation and
Cancellation
Package Diagram :
Package diagrams are used to reflect the organization of packages and their elements. When
used to represent class elements, package diagrams provide a visualization of the namespaces.

PACKAGE DIAGRAM:

AIR LINE
RESERVATION
SYSTEM
Plane Depends on Air Craft
Depends on TrackingSystem Maintenance

Flight Reservation and

Cancellation System

Accounting Personel
Depends on system
Deployment Diagram
Deployment diagrams are a kind of structure diagram used in modeling the physical aspects
of an object-oriented system. They are often be used to model the static deployment view of a
system.

DEPLOYMENT DIAGRAM:

Data
BaseServer

Administrator

Enquiry for Reservation and

Flight Details cancellation

Result :
Thus the component, package and deployment diagram are drawn successfully.
 IMPLEMENTATION

Ex.No. 10
Date :
Aim :
To Implement the Airline Reservation System using any specified language.
Result :

Thus the online Airline Reservations System was implemented using the specified front end and
back end using visual basic.
 Testing
Ex.No. 11
Date :

Aim : To write test cases for Airline Reservation System.

Test cases : A Test Case is a set of actions executed to verify a particular feature or functionality of
Airline Reservation software

Test Test Test Steps Test Data Expected Actual Pass/Fail

Case ID Scenario Results Results

TC01 Check 1. Go to Userid = User should As Pass

Customer site http://demo.co aaaa Login into Expected
Login with m Password application
valid Data 2. Enter UserId = aaaa
3. Enter
Password

4. Click Submit

TC02 Check 1.Go to Userid = User should As Pass

Customer site http://demo.co aaaa not Login into Expected
Login with m Password application
invalid Data 2.Enter UserId = aaaa
3.Enter Password

4.Click Submit

TC3 Check ticket 1. Click ticket Only click Corresponding As Pass

availability availability event page display Expected

TC4 Check 1.Fill All Details of Only Availability As Pass

Ticket Passenger click of the Airline Expected
Availability event will be
displayed

TC5 Check 1.Fill All Details of Only Ticket is As Pass

Ticket Passenger Submit Generated Expected
Reservation event for Passenger

TC6 Cancellation 1.Enter Ticket Only Ticket Will As Pass

Number Submit Be Cancelled Expected
event
.

Result :
Thus, the Airline Reservation System, test cases written sucessfully.
 Testing Process
Ex. No. 12
Date :
Aim : To learn the testing process of winrunner and also learn how to use winrunner.

Procedure:

There are 6 steps in testing process:

1. GUI map file creation: By creating GUI map file the win runner can identify the GUI
objects in the application going to be created.
2. Test scripts creation: This process involves recording, programming or both. During
the process of recording tests, insert checkpoints when the responses of the application
need to be tested.
3. Debug The Test: Run the tests in debug mode to make sure whether they run
smoothly.
4. Run Tests: Run tests in verify mode to test the application.
5. View Results: This determines the success or failures of the test.

6. Report Defects: If a particular test run fails due to the defect in the application being
tested, defects can be directly reported through the test results window.
Two types of recording modes :
 Context Sensitive Mode
 Analog Recording Mode
Context Sensitive Mode: Win runner captures and records the GUI objects, windows, keyboards
inputs and mouse click activities through context sensitive recording.

Analog Recording Mode: It captures and records the keywords inputs, mouse movement. It does
not capture the GUI object and windows. GUI map files the stored information, it learns about the
GUI objects and windows. A checkpoint enables you to check your application by comparing its
expected results of application to actual results.

By default Win Runner starts recording in context sensitive mode. If we want to change
it into analog mode we can follow below navigations.
Click Start recording
twice or Create
Menu->record-
analog or
F2 is the short key to change from one mode to another mode.

Exploring the WinRunner Window:

Before you begin creating tests, you should familiarize yourself with the Win Runner main window.

To start WinRunner:
Choose Programs > WinRunner > WinRunner on the Start menu.
The first time you start WinRunner, the Welcome to WinRunner window opens. From the welcome
window you can create a new test, open an existing test, or View an overview of WinRunner in your
default browser.

The first time you select one of these options, the WinRunner main screen opens with the
“What’s New in WinRunner” section of the help file on top. If you do not want the welcome
window to appear the next time you start WinRunner, clear the show on start-up check box.
Each test you create or run is displayed by WinRunner in a test window. You can open many
tests at one time.
 1. The Win Runner window displays all open tests.
2. Each test appears in its own test window. You use this window to record, program,
and edit test scripts.
3. Buttons on the Standard toolbar help you quickly open, run, and save tests.
4. The User toolbar (right side) provides easy access to test creation tools.
5. The status bar (Run Name) displays information about selected commands and
the current.

The Standard toolbar provides easy access to frequently performed tasks, such as opening,
executing, and saving tests, and viewing test results.

1. New Test
2. Open
3. Save
4. Run mode
5. Context sensitive mode
6. Run from top
7. Stop
8. Pause
9. Step
10. Step into
11. Toggle breakpoint
 12. Break in function
13. Add watch
14. Test results
15. Help
The User toolbar displays the tools you frequently use to create test scripts. By default, the
User toolbar is hidden.

To display the User toolbar choose Window > User Toolbar. When you create Tests, you can
minimize the WinRunner window and work exclusively from the Toolbar.
1. Record - Context Sensitive
2. Stop
3. GUI Checkpoint for Single Property
4. GUI Checkpoint for Object/Window
5. GUI Checkpoint for Multiple Objects
6. Bitmap Checkpoint for Object/Window
7. Bitmap Checkpoint for Screen Area
8. Default Database Checkpoint
9. Custom Database Checkpoint
10. Synchronization Point for Object/Window Property
11. Synchronization Point for Object/Window Bitmap
12. Synchronization Point for Screen Area Bitmap
13. Edit GUI Checklist
14. Edit Database Checklist
15. Get Text from Object/Window
16. Get Text from Screen Area
17. Insert Function from object window
18. Insert Function from Function generator

The User toolbar is customizable. You choose to add or remove buttons using the Settings
> Customize User Toolbar menu option. When you re-open Win Runner, the User toolbar appears
as it was when you last closed it.

Note that you can also execute many commands using soft keys. Soft keys are Key board
shortcuts for carrying out menu commands. You can configure the Soft key combinations for your
keyboard using the Soft key Configuration utility in Your WinRunner program group. For more
information, see the “WinRunner at a Glance” chapter in your WinRunner User’s Guide.
 How Does Win Runner Identify GUI Objects?
GUI applications are made up of GUI objects such as windows, buttons, lists, and Menus.
When Win Runner learns the description of a GUI object, it looks at the object’s Physical properties.
Each GUI object has many physical properties such as “Class,” “label,” “width,” “height”,
“handle,” and “enabled” to name a few. Win Runner, however, only learns the properties that
uniquely distinguish an Object from all other objects in the application. For more information
regarding Properties, refer to the “Configuring the GUI Map” chapter in the WinRunner User’s
Guide.

Choosing a GUI Map Mode:

Before you start teaching Win Runner the GUI of an application, you should consider
whether you want to organize your GUI map files in the GUI Map File per Test mode or the
Global GUI Map File mode

The GUI Map File per Test Mode:

In the GUI Map File per Test mode, Win Runner automatically creates a new GUI map file for
every new test you create. WinRunner automatically saves and opens the GUI map file that
corresponds to your test.
If you are new to WinRunner or to testing, you may want to consider working in the GUI
Map File per Test mode. In this mode, a GUI map file is created automatically every time you
create a new test. The GUI map file that corresponds to your test is automatically saved whenever
you save your test and automatically loaded whenever you open your test. This is the simplest
mode for inexperienced testers and for ensuring that updated GUI Map files are saved and loaded.

The Global GUI Map File Mode:

In the Global GUI Map File mode, you can use a single GUI map for a group of tests.
When you work in the Global GUI Map File mode, you need to save the information that
WinRunner learns about the properties into a GUI map file. When you run a test, you must load
the appropriate GUI map file. If you are familiar with WinRunner or with testing, it is probably
most efficient to work in the Global GUI Map File mode.

By default, WinRunner is set to the Global GUI Map File mode.

To change the mode to the GUI Map File per Test mode
choose Settings > General Options,
click the Environment tab, and select GUI Map File per Test. Click OK to close the dialog box.
 Note: 1) If you change the GUI Map File mode, you must restart WinRunner for the changes to
take effect.

2)If you choose to work in the Global GUI Map File mode, proceed to the section below on
Using the Rapid Test Script Wizard.

Using the Rapid Test Script Wizard

If you choose the Global GUI Map File mode, the Rapid Test Script wizard is usually the easiest
and quickest way to start the testing process.

Note: The Rapid Test Script Wizard is not available when you work in
GUI Map File per Test mode.
The Rapid Test Script Wizard systematically opens the windows in your application and learns
the description of every GUI object. The wizard stores this information in a GUI map file. To
observe Win Runner’s learning process, use the Rapid Test Script Wizard on the Flight
Reservation application.

Note: The Rapid Test Script Wizard is not available when the Terminal Emulator, the Web
Test or the Java add-in is loaded.

Result :

Thus the testing process and testing procedure for winrunner software testing tool
sucessfully.
Ex.No. 13
Date :
Aim : To check verification and validation of Airline Reservation System using Winrunner software
testing tool.

Procedure :

1. Log in to the Flight Reservation application.

If the Login window is open, type your name in the Agent Name field and mercury in the
Password field and click OK. The name you type must be at least four characters long.
If the Login window is not already open on your desktop,
choose Programs > WinRunner > Sample Applications > Flight 1A on the Start menu
and then log in, as described in the previous paragraph.
2. Start Win Runner.
If Win Runner is not already open, choose Programs >
WinRunner > Win Runner on the Start menu.
3. Open a new test.
If the Welcome window is open, click the New Test button. Otherwise, choose
File > New. A new test window opens in WinRunner
4. Start the Rapid Test Script wizard.
Choose Create > Rapid Test Script Wizard. Click Next in the wizard’s Welcome Screen to
advance to the next screen.

5. Point to the application you want to test.

 Click the hand button and then click anywhere in the Flight Reservation application. The
application’s window name appears in the wizard’s Window
Name box. Click Next
6. Make sure that all the check boxes are cleared.
For the purposes of this exercise, confirm that all the check boxes are cleared.
You will use the wizard only to learn the GUI of the Flight Reservation application. Click Next.
Note: A regression test is performed when the tester wishes to see the progress of the testing
process by performing identical tests before and after a bug has been fixed. A regression test
allows the tester to compare expected test results with the actual results.

7. Accept the default navigation controls.

Navigation controls tell WinRunner which GUI objects are used to open windows. The Flight
Reservation application uses the default navigation controls (... and > >) so you do not need to
define additional controls. Click Next.

8. Set the learning flow to “Express.”

The learning flow determines how WinRunner walks through your application.
Two modes are available: Express and Comprehensive. Comprehensive mode lets you
customize how the wizard learns GUI object descriptions. First-time WinRunner users should use
Express mode. Click the Learn button. The wizard begins walking through the application, pulling
down menus, opening windows, and learning object descriptions. This process takes a few
minutes. If a pop-up message notifies you that an interface element is disabled, click the Continue
button in the message box. If the wizard cannot close a window, it will ask you to show it how to
close the window. Follow the directions on the screen.

9. Accept “No” in the Start Application screen.

You can choose to have WinRunner automatically open the Flight Reservation application each
time you start WinRunner. Accept the default “No.” Click Next.

10. Save the GUI information and a start up script.

The wizard saves the GUI information in a GUI map file. The wizard also creates a start up
script. This script runs automatically each time you start WinRunner. It contains a command which
loads the GUI map file so that WinRunner will be ready to test your application. Accept the default
paths and file names or define different ones. Make sure that you have write permission for the
selected folders. Click Next.

11. Click OK in the Congratulations screen.

The information WinRunner learned about the application is stored in a GUI map file.
Running the Test:
You are now ready to run your recorded test script and to analyze the test
results. WinRunner provides three modes for running tests. You select a
mode from the toolbar.

 Use Verify mode when running a test to check the behavior of your application, and
when you want to save the test results.

 UseDebug mode when you want to check that the test script runs smoothly without errors
in syntax.

 Use Update mode when you want to create new expected results for a GUI checkpoint or
checkpoint.

To Run the test:

1. Check that WinRunner and the main window of the Flight Reservation application are
open on your desktop.

2. Make sure that the test window is active in WinRunner. Click the title bar of the
lesson3 test window. If the test is not already open, choose File > Open and select the
 test.
3. Make sure the main window of the Flight Reservation application is active.
If any dialog boxes are open, close them.
4. Make sure that Verify mode is selected in
the toolbar. 5 Choose Run from Top.
5. Choose Run > Run from Top or click the Run from Top button. The Run Test
dialog box opens

6. Choose a Test Run name.

Define the name of the folder in which WinRunner will store the results of the test. Accept the
default folder name “res1.” The results folder will be stored within the test’s folder.

Note the Display Test Results at end of run check box at the bottom of the dialog box. When
this check box is selected, WinRunner automatically displays the test results when the test run is
completed. Make sure that this check box is selected.

7. Run the test.

Click OK in the Run Test dialog box. WinRunner immediately begins running the test. Watch
how WinRunner opens each window in the Flight Reservation application.

8. Review the test results.

When the test run is completed, the test results automatically appear in the WinRunner Test Results
window.
Analyzing Test Results:
Once a test run is completed, you can immediately review the test results in the WinRunner
Test Results window. WinRunner color-codes results (green indicates passed and red indicates
failed) so that you can quickly draw conclusions about the success or failure of the test.
1. Make sure that the WinRunner Test Results window is open and displays the test results.
If the WinRunner Test Results window is not currently open, first click the test window to
activate it, and then choose Tools > Test Results or click the Test Results button.
 1. Displays the name of the current test.
2. Shows the current results directory name.
3. Shows whether a test run passed or failed.
4. Includes general information about the test run such as date, operator name,
and total run time. To view these details, double click the Information icon.

5. The test log section lists the major events that occurred during the test run. It
also lists the test script line at which each event occurred

2. Review the results.

3. Close the Test Results window.
Choose File > Exit in the WinRunner Test Results window.
4. Close the test.
Choose File > Close.
5. Close the Flight Reservation application.
Choose File > Exit

Result :

Thus, we checked verification and validation of Airline Reservation System using

Winrunner software testing tool successfully.