Software Requirement Specification for Flight Reservation

Page 1

Software Requirements
Specification

Dani Vainstein

Page 1

Software Requirement Specification for Flight Reservation

Page 2

Table of Conten
Table of Contents..................................................................II
Table of Figures...................................................................III
Revision Log........................................................................ IV
1.
Introduction...............................................................1
1.1
Purpose..................................................................................1
1.2
Document Conventions.........................................................1
1.2.1 Abbreviations......................................................................1
1.2.2 Symbols...............................................................................2
1.3
Intended Audience.................................................................2
1.4
Project Scope.........................................................................3
1.5
References.............................................................................3
2.
Overall Description.....................................................4
2.1
Product Features....................................................................4
2.1.1 Secured Login......................................................................4
2.1.2 Inserting new reservations..................................................4
2.1.3 Confirmations......................................................................4
2.1.4 Updating existing reservations............................................4
2.1.5 Removing existing reservations..........................................4
2.1.6 Search capabilities..............................................................5
2.1.7 Reporting.............................................................................5
2.1.8 Database.............................................................................5
2.2
Known Bugs...........................................................................5
2.3
Operating Environment..........................................................5
2.4
User Documentation..............................................................6
2.5
Assumptions and Dependencies............................................6
3.
Requirements.............................................................6
3.1
Login......................................................................................6
3.1.1 Description..........................................................................6
3.1.2 Functional Requirements.....................................................7
3.1.3 Login Graphical User Interface..........................................8
3.2
Flight Reservation..................................................................9
3.2.1 Description..........................................................................9
3.2.2 Flight Reservation Graphical User Interface...................11
3.2.3 Functional Requirements...................................................19
3.3
New Order Process...............................................................20
3.3.1 Description........................................................................20
3.3.2 Functional Requirements...................................................20
3.3.3 Error Messages..................................................................24
4.
User Challenge..........................................................25
4.1
Fax Preview..........................................................................25
4.1.1 Gui Defaults.......................................................................26
4.2
Menu....................................................................................27
4.2.1 Functionality......................................................................27
Dani Vainstein

Page 2

Software Requirement Specification for Flight Reservation

4.3
4.3.1
4.4
4.4.1
4.5
4.5.1
4.5.2
4.5.3
4.6
4.7
4.7.1
4.7.2

Page 3

Fax Order No. <n>...............................................................29

Functionality......................................................................29
About Flight Reservations System.......................................29
Gui Defaults.......................................................................29
Open Order Process.............................................................30
Description........................................................................30
Functional Requirements...................................................31
Functional Requirements...................................................32
Deleting an Order Process...................................................33
Reporting.............................................................................33
Description........................................................................33
Graphical User Interface Defaults.....................................34

Table of FiguresY
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

1 - Login Dialog............................................................................6
2 - Login Image............................................................................8
3 - Flights Table............................................................................8
4 - Flights Reservation Window....................................................9
5 Fax Order No. <n>...............................................................10
6 Flight Reservation Toolbar....................................................10
7 Flight Schedule Frame..........................................................10
8 Order Information Frame......................................................11
9 Summary Frame...................................................................15
10 Window Image...................................................................15
11 Order Information Frame....................................................15
12 Flights Table Image............................................................16
13 Fax Order No. <n> Dialog..................................................17
14 Fax Preview Dialog.............................................................25
15 Fax Preview Image.............................................................26
16 About Image.......................................................................29
17 Open Order Dialog.............................................................29
18 Search Results Dialog........................................................30
18 Graphical Report................................................................33

Dani Vainstein

Page 3

Software Requirement Specification for Flight Reservation

Page 4

Revision Log
Name
Dani Vainstein

Date
18 Dec 2007

Revision Description
Draft

Version
1.0

Dani Vainstein

31 Jan 2008

Req0013 removed
duplication (T Roopesh )

1.1

Dani Vainstein

Page 4

Software Requirement Specification for Flight Reservation

Page 1

1. Introduction
A Product requirements document is used in product marketing to
plan and execute new products.
A Software Requirements Specification is a complete description of
the behavior of the system to be developed. It includes a set of use
cases that describe all of the interactions that users will have with the
software.
Use Cases are also known as Functional Requirements. In addition to
use cases, the SRS also contains nonfunctional requirements.
The software requirements document is a written statement of what
the software will do.
What the software does is directly perceived by its users. When the
user performs some action, the software responds in a particular way.
Therefore you must agree on actions the users can perform and
response they should expect. This common understanding is
captured in the requirements document.

1.1 Purpose
This document contains the tests requirements for the Automation FR
Project.
These software requirements were established by Dani Vainstein.
This Software requirements document was done using our
imagination and our understanding on the Mercury "Flight
Reservation" application, and also to demonstrate and
simulate a real QA automation project.
This SRS specifies to Mercury Flight Application Version 4a.

1.2 Document Conventions

1.2.1Abbreviations
AUT
GUI
UI
LIB
MTM
QFL
VBS
N/A

Dani Vainstein

Application Under Test

Graphical User Interface
User Interface
Library folder contains QTP library functions
Multi Test Manager Tool.
File Extension (QTP File Library )
File Extension ( VBScript )
Not Available

Page 1

Software Requirement Specification for Flight Reservation

DP
OR
SOR
OO
OOP
OOT
STD
PK
FK

Page 2

Descriptive Programming
Object Repository
Shared Object Repository
Object Oriented
Object Oriented Programming
Object Oriented Testing
Software Test Documentation
Primary Key ( Database relationships )
Foreign key ( Database relationships )

1.2.2Symbols
Exclamation
Question
Information
Critical

1.3 Intended Audience

This project is for "First Steps" members that want to learn how to
practically learn how to use QTP as well as intermediate and expert
users that want to review different methodology methods, code tricks
and implementations.
Project Team :

Project Manager
Senior Manager
Advisors
Dani Vainstein

Natwarlal Asawa from India, Hyderabad

Bharathi Babu from India, Pune
Dinkar Singh from India, Delhi
Ayyappa Koppolu from India, Pune
Paul Grossman from USA, Chicago
Sumit Singhal from India, Bangalore
Sanjeev Mathur from India, Noida
Manasa VN from India, Bangalore
Prakash Kumar from India, Pune
Richi Sharma from USA, New Jersey
Suresh K from India, Bangalore
Janardhan Kalvakuntla from USA, New England
Joydeep Das from India, Hyderabad
Indlamudi Rajesh from India, Mumbai.
Monika Arora Gautam from USA, Austin
Dani Vainstein from Israel, Petah Tikva
Yaron Assa from Israel, Ramat Gan
Page 2

Software Requirement Specification for Flight Reservation

Page 3

Meir Bar-Tal from Israel, Beer Sheva

1.4 Project Scope

This document defines at a functional level the business activities
that are encompassed by the system and the rules that apply to
them. It also encompasses some of the key high and low level
technical requirements of the system.
It draws heavily on both proposed Framework and Business Rules and
the Technical Architecture documents. The scope of the detailed
analysis project phase specifies that this document will include.

Classification of requirements according to their functional

areas.
A description of each process in the system, including their
inputs, outputs, and data transformation rules.

1.5 References

VBScript Tutorial
http://www.advancedqtp.com/knowladge-base/firststeps/vbscript-tutorial/

VBScript Basics
http://www.advancedqtp.com/knowladge-base/scriptingquicktest-professional/vbscript-basics/

VBScript Advanced
http://www.advancedqtp.com/knowladge-base/scriptingquicktest-professional/advanced-vbscript/

Databases
http://www.advancedqtp.com/knowladge-base/scriptingquicktest-professional/adodb/

Dictionary
http://www.advancedqtp.com/knowladge-base/codetechniques/code-design-101/object-dictionaries-for-genericfunctions/

Regular Expressions
http://www.advancedqtp.com/knowladge-base/scriptingquicktest-professional/regular-expressions/

CheckPoints
http://www.advancedqtp.com/knowladge-base/codetechniques/custom-checkpoints/

Dani Vainstein

Page 3

Software Requirement Specification for Flight Reservation

Negative Testing
http://www.advancedqtp.com/knowladge-base/codetechniques/code-design-101/negative-tests/

DP
http://www.advancedqtp.com/knowladge-base/codetechniques/dp-101/

Page 4

2. Overall Description
2.1 Product Features
2.1.1Secured Login
The system supports a secured login user/password.
Insert a new flight reservation.

2.1.2Inserting new reservations

The application is able to insert new flight reservations according
a future date requested, destinations and flight selections.

2.1.3Confirmations
The application is send fax confirmations to clients, about new,
updates and cancelled flights.

2.1.4Updating existing reservations.

The application is able to update any data from an existing
reservation.

2.1.5Removing existing reservations.

The application is able to cancel any existing reservation.

2.1.6Search capabilities.
The application supports a searching mechanism by order
number customer name and/or date of flight

2.1.7Reporting
The application supports graphical and text reports of
reservations.

2.1.8Database

The Flight Reservation database is a MS-Access file ( .mdb ).

The database has 2 tables
Flights table
o [PK] Flight_Number Integer

Dani Vainstein

Page 4

Software Requirement Specification for Flight Reservation

Page 5

o Departure_Initials String( size = 3 )

o Departure String( size = 30 )
o Day_Of_Week String( size = 9 )
o Arrival_Initials String( size = 3 )
o Arrival String( size = 30 )
o Departure_Time String( size = 8 )
o Arrival_Time String( size = 8 )
o Airlines String( size = 5 )
o Seats_Available Integer
o Ticket_Price - Currency
Orders table
o [PK] Order_Number Long Integer
o Customer_Name String( size = 20 )
o Departure_Date Date
o [FK] Flight_Number Integer
o Tickets_Ordered Byte
o Class String ( size = 1 )
o Agents_Name - String ( size = 10 )
o Send_Signature_With_Order String ( size = 1 Y/N )

2.2 Known Bugs

1.

In the application database, table Flights, there is a

field name Seats_Available. Usually the value is set to 250. I
was trying to test if the reservations are limited and
calculated. I ordered 400 tickets ( 40 iterations 10 tickets periteration ) and not get any error message.

2.3 Operating Environment

The Project is implemented on QTP version 9.2

2.4 User Documentation

It is recommended to use the QTP help. Every presentation has a
"Before You Start" slide where all the topics that will be used in
the current presentation.

2.5 Assumptions and Dependencies

The project was originally designed, tested and reviewed for QTP
version 9.2. If you use a different version of QTP, some
screenshots might see different from yours. Be aware that some
functionality may not work in earlier versions of QTP.
I will need MS-Excel installed on your computer, to create and
modify datasheets files.
You might need MS-Access to modify and view the flight
application database. However you can use "Snapshot Viewer for

Dani Vainstein

Page 5

Software Requirement Specification for Flight Reservation

Page 6

MS-Access" from Microsoft at www/microsoft.com/downloads site.

This software is free.
From presentation one you will need the "Multi Test Manager"
provided by HP/Mercury. We will provide a download link fro this
tool.
We are assuming that you dont have Quality-Center; this
project was designed with no interaction to Quality Center.
We are also assuming that you dont have a network drive. So,
always save your work.

3. Requirements
This part of the requirements document serves to present the
"big picture" of the application. Here you lay out the objectives of
the application.

3.1 Login
3.1.1Description
The Login dialog, logs to the Flight Reservation application. A
shortcut to the application demo can be found in
Start Sample Applications Flight.
The user must provide an Agent Name that must be at least 4
characters long and the Password is always "Mercury". Clicking
the OK button will access the application if requested information
is correct.

Figure 1 - Login Dialog

3.1.2Functional Requirements
3.1.2.1

Req0001

Req0001a - User activates the Flight Application executable file

from installation directory plus "\samples\flight\app\flightxx.exe"
Req0001b - immediately afterwards the Dialog "Login" should be
displayed.

Dani Vainstein

Page 6

Software Requirement Specification for Flight Reservation

3.1.2.2

Page 7

Req0003

User press OK without entering any information.

Req0003a Popup dialog is displayed.
Req0003b Popup title "Flight Reservations"
Req0003c message type: Exclamation
Req0003d message text "please enter agent name"

3.1.2.3

Req0004

The agent name must be at least 4 characters long.

Req0004a - Popup dialog displayed: True.
Req0004b Popup title: "Flight Reservations"
Req0004c message type: Exclamation
Req0004d message text "Agent name must be at least 4
characters long."

3.1.2.4

Req0005

The password must be at least 4 characters long.

Req0005a - Popup dialog is displayed.
Req0005b Popup title "Flight Reservations"
Req0005c message type: Exclamation.
Req0005d message text: "Password must be at least 4
characters long"

3.1.2.5

Req0006

The field Password should not be empty.

Req0006a - Popup dialog is displayed.
Req0006b Popup title "Flight Reservations"
Req0006c message type: Critical
Req0006d message text "Please enter password"

3.1.2.6

Req0007

Wrong Password field will trigger a critical popup message

Req0006a Popup dialog is displayed.
Req0006b Popup title "Flight Reservations"
Req0006c message type: Critical
Req0006d message text: "Incorrect password. Please try again"

Dani Vainstein

Page 7

Software Requirement Specification for Flight Reservation

3.1.2.7

Page 8

Req0008

Pressing "Cancel" at any time should close immediately the "Login"

dialog

3.1.2.8

Req0009

After 4 bad attempts to login (bad password) the application will

trigger an information message and closed.
Req0009a Popup dialog is displayed.
Req0009b Popup title "Flight Reservations"
Req0009c message type: Exclamation
Req0009d message text: "Login unsuccessful. Please try again
later."
Req0009e Application is closed.

3.1.3Login Graphical User Interface

3.1.3.1

Req0002

User activates the application the first time.

Req0002a - Label "Agent Name" visible: True.
Req0002b - Textbox "Agent Name" text: "", enabled: True, focused
: True.
Req0002c - Label "Password" visible: True.
Req0002d - Textbox "Password" enabled: True, text: "".
Req0002e - Button "OK" enabled: True.
Req0002f - Button "Cancel" enabled: True.
Req0002g - Button '"Help" enabled: True.
Req0002h Image Logo:

Figure 2 - Login Image

3.2 Flight Reservation

3.2.1Description
By inserting a valid and future date, and selecting a base and
destination city, the user can choose a flight; order 1 to 10

Dani Vainstein

Page 8

Software Requirement Specification for Flight Reservation

Page 9

tickets on 3 different classes. A client can receive a fax

confirmation.
The user must provide a future valid Flight Date and must select
a Fly From city and a Fly To city.

Figure 3 - Flights Table

The system will monitor from this point the price-per-ticket and
the total amount to pay.
In addition the user can select 1 to 10 tickets and a flight class.
The information is inserted to a database, and a successful or
failure message should be displayed in the transaction progress
bar.

Dani Vainstein

Page 9

Software Requirement Specification for Flight Reservation

Page 10

Figure 4 - Flights Reservation Window

In addition the user can get fax confirmation with an optional

agent signature.

Figure 5 Fax Order No. <n>

Dani Vainstein

Page 10

Software Requirement Specification for Flight Reservation

Page 11

3.2.2Flight Reservation Graphical User Interface

3.2.2.1

The Toolbar

Figure 6 Flight Reservation Toolbar

3.2.2.1.1 Req0010
Req0010a Button "New Order"

enabled: True

icon:

Req0010b Button "Open Order"

enabled: True

icon is:

Req0010c Button "Delete Order"

enabled: False

icon is:

Req0010d Button "Graphs"

enabled: True,

con is:

Req0010e Button "Reports"

enabled: True

icon is:

Req0010f Button "Help"

enabled: True

icon is:

3.2.2.2

Dani Vainstein

Flight Schedule Frame

Page 11

Software Requirement Specification for Flight Reservation

Page 12

Figure 7 Flight Schedule Frame

3.2.2.2.1 Req0011
Req0011a "Date of Flight"

enabled: True

text: ""

formattedText: "__/__/__"

mask: "99/99/99"

focused: True

Req0011b "Flight From"

enabled: True

selection: ""

Req0011c "Flight To"

enabled: True

selection: ""

Req0011d "Flights"

enabled: False

3.2.2.3

Order Information Frame

Figure 8 Order Information Frame

3.2.2.3.1 Req0012
Dani Vainstein

Page 12

Software Requirement Specification for Flight Reservation

Page 13

Req0012a "Flight No." text: ""

Req0012b "Departure Time" text: ""
Req0012c "Arrival Time" text: ""
Req0012d "Airline" text: ""
Req0012e "Name", text: ""
Req0012f "Tickets" text: ""
Req0012g "Price", text: ""
Req0012h "Total" text: ""
Req0012i "Insert Order"

Enabled: False

Req0012j "Delete Order"

Enabled: False

Req0012k "Update Order"

Enabled: False

Req0012l "Business"

enabled: False

Req0012m "Economy"

enabled: False

Req0012n "First"

enabled: False

3.2.2.4

Menu Defaults

3.2.2.4.1 Req0013
Req0013a "File"

Exists: True

Enabled: True

Index: 1

Label: "File"

SubMenuCount: 4

Req0013b "Edit"

Dani Vainstein

Exists: True,

Enabled: True

Index: 2

Page 13

Software Requirement Specification for Flight Reservation

Label: "Edit"

SubMenuCount: 3

Page 14

Req0013c "Analysis"

Exists: True

Enabled: True

Index: 3

Label: "Analysis"

SubMenuCount: 2

Req0013d "Help"

Exists: True

Enabled: True

Index: 4

Label: "Help"

SubMenuCount: 2

Req0013e "New Order"

Exists: True

Enabled: True

Label: "New Order"

HasSubMenu: False

Req0013f "Open Order"

Exists: True

Enabled: True

Label: "Open Order..."

HasSubMenu: False

Req0013g "Fax Order"

Exists: True

Enabled: False

Label: "Fax Order"

HasSubMenu: False

Req0013h "Exit"

Dani Vainstein

Exists: True

Enabled: True

Page 14

Software Requirement Specification for Flight Reservation

Label: "Exit"

HasSubMenu: False

Page 15

Req0013i "Copy" Exists: True

Req0013j "Cut" Exists: True
Req0013k "Paste" Exists: True
Req0013l "Reports"

Exists: True

Enabled: True

Label: "Reports"

HasSubMenu: False

Req0013m "Graphs"

Exists: True

Enabled: True

Label: "Graphs"

HasSubMenu: False

Req0013n "Contents"

Exists: True

Enabled: True

Label: "Contents"

HasSubMenu: False
Req0013o "About"

Exists: True

Enabled: True

Label: "About"

HasSubMenu: False

3.2.2.5

Summary Defaults

Figure 9 Summary Frame

3.2.2.5.1 Req0014
Req0014a "Order No." text: ""
Req0014b Progress bar text: ""

Dani Vainstein

Page 15

Software Requirement Specification for Flight Reservation

3.2.2.6

Page 16

Window Image

3.2.2.6.1 Req0015

Figure 10 Window Image

3.2.2.7

Flights Table Dialog

Figure 11 Order Information Frame

3.2.2.7.1 Req0016
Req0016a List

enabled: True

columns count: 7

Req0016b Columns

Dani Vainstein

"Flight"

"From"

Page 16

Software Requirement Specification for Flight Reservation

"To"

"Departure"

"Arrival"

"Airline"

Page 17

"Price"
Req0016c Button "OK"

enabled: True

Req0016d Button "Cancel

enabled: True

Req0016e Image :

Figure 12 Flights Table Image

3.2.2.8

Send Fax - Defaults

Figure 13 Fax Order No. <n> Dialog

Dani Vainstein

Page 17

Software Requirement Specification for Flight Reservation

Page 18

3.2.2.8.1 Req0018
Information match:
Req0018a Dialog

text: "Fax Order No. <num>"

Ispopupwindow: True

Req0018b Name

text: <Name>

Order: text: <Order>

Flight: text: <Flight>

Date: text: <Date>,

From: text: <Fly From>

Departure text: <Departure Time>

To: text: <Flight To>

Arrival: text: <Arrival Time>,

Class: text: <Class>

# Tickets text: <Tickets>,

Ticket Price: <Price>

Total text: <Total>

Req0018c Fax Number;

enabled: True

format: "(###)###-####"

FormattedText: "(___)___-____"

mask: (999)999-9999; text: ""

focused: True

Req0018c Send Signature with order; enabled: True, checked:

OFF
Req0018d Agent Signature bitmap:

Req0018e Preview Fax button

Dani Vainstein

enabled: True

Page 18

Software Requirement Specification for Flight Reservation

Page 19

Req0018f Send button

enabled: True

Req0018g Cancel button

enabled: True

Req0018h Clear Signature button

enabled: True

3.2.3Functional Requirements
3.2.3.1

Toolbar Functionality

3.2.3.1.1 Req0020
If Data displayed, selecting "New" button, should clear the
form. However if information updated without saving
changes:
Req0020a Popup dialog is displayed.
Req0020b Popup title "Flight Reservations"
Req0020c message type: Question.
Req0020d message text: "The information has changed. Save
changes?"

3.2.3.1.2 Req0021
Toolbar "Open Order" will display the Dialog "Open Order".
Req0021 - Open Order dialog exist: True

3.2.3.1.3 Req0022
Toolbar "Delete" will be enabled only after open an order.
Req0022 open an order "Delete" enabled: True

3.2.3.1.4 Req0023
Toolbar "Graphs" will open the dialog "Graph"
Req0023 Graph dialog

exist: True

3.2.3.1.5 Req0024
Toolbar "Reports" will open "report.txt" notepad file.
Req0024 Reports text file

Dani Vainstein

exist: True

Page 19

Software Requirement Specification for Flight Reservation

Page 20

3.2.3.1.6 Req0025
Toolbar "Help" will open the window "Flight Reservation
Help Version.*"
Req0025 Flight Reservation Help Version .*

exist: True

3.3 New Order Process

3.3.1Description
See Description

3.3.2Functional Requirements
3.3.2.1

Req0035

Only valid departures cities must be in list "Fly Form" and "Fly
To"
Req0035a Fly From

all items: < all items >

Req0035b Fly To

all items: < all items >

3.3.2.2

Req0036

After selecting "Fly From" The "Fly To" field

Req0035a Fly To

items count : < FlyFrom >.count - 1

Req0035b Fly To;

< FlyFrom > value is not in the "all items"

3.3.2.3

Req0037

Only after selecting "Fly From" the access to Flights Table

will be available.
Req0037a Button "Flights"

enabled: True.

Req0037b icon

Dani Vainstein

Page 20

Software Requirement Specification for Flight Reservation

3.3.2.4

Page 21

Req0038

All items are ordered by Flight.

Req0038a List

items count: <items count>

all items: <all items>

selected: <item 0>

3.3.2.5

Req0039

After selecting a flight from "Flights Table"

Req0039a "Name"

focused: True

Req0039b "Tickets"

enabled: True

Text: "1"

Req0039c "Economy"

enabled: True

checked: "ON"

Req0039d "Flight No."

text: <FlightNo>

Req0039e "Departure Time"

text: <DepartureTime>

Req0039f "Arrival Time"

text: <ArrivalTime>

Req0039g "Airline"

text: <Airline>

Req0039h "Price"

text: <Price>

Req0039i "Total"

text: <Price> * <Tickets>

3.3.2.6

Req0040

After typing a name, tickets or selecting a class

Req0040a "Insert Order"

Dani Vainstein

enabled: True

Page 21

Software Requirement Specification for Flight Reservation

Page 22

Req0040b "Total"

text: <Price> * <Tickets>

3.3.2.7

Req0041

After pressing "Insert Order"

Req0041a Application temporally disabled "Flight Reservation

enabled: False

Req0041b "Insert Order"

enabled: True

Req0040c "Update Order"

enabled: False

Req0041d "Delete Order"

enabled: False

Req0041e "Order No."

text: <last order no> + 1

Req0041f "Send Fax" menu item

enabled: True

Req0041g toolbar "Delete"

enabled: True

Req0041h toolbar button "Delete"

image:

Req0041i progress bar message

text: "Insert Done"

Req0041j new record was added to Orders table in database.

Fields values must be consists.

"Order_Number",

"Customer_Name",

"Departue_Date",

"Flight_Number"

"Tickets_Ordered", "Class"

"Agents_Name"

3.3.2.8

Req0042

After pressing "Send"

Req0042a Message "Dialing..."

Dani Vainstein

Page 22

Software Requirement Specification for Flight Reservation

Page 23

Req0042b Message "Connecting..."

Req0042c Message "Sending Fax..."
Req0042d dialog "Fax Order No. <x>

Exists: False

Req0042e progress bar message

text: "Fax Sent Successfully"

Req0042f record <n> Field "Send Signature" must be consists.

3.3.2.9

Req0043

After pressing "Send"

Req0043a dialog "Fax Preview

Exists: False

Req0043b Message "Dialing..."

Req0043c Message "Connecting..."
Req0043d Message "Sending Fax..."
Req0043e progress bar message

text: "Fax Sent Successfully"

Req0043f record <n> Field "Send Signature" must be consists.

3.3.3Error Messages
3.3.3.1

Req0044

User types an invalid month.

Req0044a Popup dialog is displayed.
Req0044b Popup title: "Flight Reservations"
Req0044c message type: Exclamation
Req0044d message text: "Invalid month Entered.The month
must be greater than 01 and less than 12."

3.3.3.2

Req0045

User types an invalid day

Req0045a Popup dialog is displayed.
Req0045b Popup title: "Flight Reservations"
Req0045c message type: Exclamation
Req0045d message text: "Invalid day Entered. The date should
be valid for the given month."

Dani Vainstein

Page 23

Software Requirement Specification for Flight Reservation

3.3.3.3

Page 24

Req0046

User type an invalid year (valid 2007-2038).

Req0046a Popup dialog is displayed.
Req0046b Popup title: "Flight Reservations"
Req0046c message type: Exclamation
Req0046d message text: "Invalid year Entered.
The year must be greater than 2007 and less than 2038.

3.3.3.4

Req0047

Valid dates are Today()+1, User type an old acceptable date.

Req0047a Popup dialog is displayed.
Req0047b Popup title: "Flight Reservations"
Req0047c message type: Information
Req0047d message text: "Valid flight dates are after <Today>"

3.3.3.5

Req0048

User select "Fly From" without "Date of Flight"

Req0048a Popup dialog is displayed.
Req0048b Popup title: "Flight Reservations"
Req0048c message type: Information
Req0048d message text: "Please enter a flight date"

3.3.3.6

Req0049

User select "Fly To" without "Fly From"

Req0049a Popup dialog is displayed.
Req0049b Popup title: "Flight Reservations"
Req0049c message type: Information
Req0049d message text: "Please enter a fly 'from' city."

3.3.3.7

Req0050

Valid number of tickets between 1 and 10, The user types an

amount greater than 10.
Req0050a Popup dialog is displayed.
Req0050b Popup title: "Flight Reservations"
Req0050c message type: Critical

Dani Vainstein

Page 24

Software Requirement Specification for Flight Reservation

Page 25

Req0050d message text: "Only ten tickets may be ordered at one

time"

4. User Challenge
This part of the requirements document is for students that want to go
forward and complete the whole project.
AdvancedQTP staff will help you, on the "Student Challenge" part.
Use the FR Project Forum to ask question, report errors in the
presentations, and any other issue regarding the FR Project.
In addition, you want to add more ( we know there are more )
requirements to this document, write me to [email protected]

4.1 Fax Preview

4.1.1Gui Defaults

Figure 14 Fax Preview Dialog

4.1.1.1

Req0019

Information match:
Req0019a Dialog; Ispopupwindow: True
Req0019b Fax # = < faxNo >
Req0019c Customer = < customer >
Req0019d Flight Date = < flightDate>
Req0019e Flight No. = < flightNo >
Req0019f From = < flyFrom >
Req0019g To = < flyTo >

Dani Vainstein

Page 25

Software Requirement Specification for Flight Reservation

Page 26

Req0019h Departure = < departure >

Req0019i Arrival = < arrival >
Req0019j Airline = < airline >
Req0019k Class = < class >
Req0019l # Tickets = < tickets >
Req0019m Agent = < agent >
Req0019n Price = < price >
Req0019o Total = < total >
Req0019p Order No. = < orderNo >
Req0019q Button "send"

enabled" True

Req0019r Button "Cancel"

enabled: True

Req0019s image :

Figure 15 Fax Preview Image

4.2 Menu
4.2.1Functionality
4.2.1.1

Req0026

If Data displayed, selecting "File; New" menu item, should

clear the form. However if information updated without saving
changes:
Req0026a Popup dialog is displayed.
Req0026b Popup title "Flight Reservations"
Req0026c message type: Question.
Req0026d message text: "The information has changed. Save
changes?"

Dani Vainstein

Page 26

Software Requirement Specification for Flight Reservation

4.2.1.2

Page 27

Req0027

If Data displayed, selecting "File; New" menu item, should

clear the form. However if information updated without saving
changes:
Req0026a Popup dialog is displayed.
Req0026b Popup title "Flight Reservations"
Req0026c message type: Question.
Req0026d message text: "The information has changed. Save
changes?"

4.2.1.3

Req0028

Toolbar "Open Order" will display the Dialog "Open Order".

However if information updated without saving changes:
Req0026a Open Order dialog exist:
Req0026b Popup dialog is displayed.
Req0026c Popup title "Flight Reservations"
Req0026d message type: Question.
Req0026e message text: "The information has changed. Save
changes?"

4.2.1.4

Req0029

If "File; Fax Order" is enabled it should open the "Fax Order

No. x" Dialog, where "x" is the currently opened reservation.
Req0029a "Fax Order No. x"

exist: True

Req0029b "x"; currently opened reservation. < orderNo >

4.2.1.5

Req0030

Menu item "File; Exit" should close application

4.2.1.6

Req0031

Menu item "Analysis; Graphs" will open the dialog "Graph"

Graph dialog exist: True

4.2.1.7

Req0032

Menu item "Analysis; Reports" will open "report.txt" notepad

file.

Dani Vainstein

Page 27

Software Requirement Specification for Flight Reservation

Page 28

Reports text file exist: True

4.2.1.8

Req0033

Menu item "Help; Contents" will open the window "Flight

Reservation Help Version.*"
Flight Reservation Help Version .*

exist: True

4.2.1.9

Req0034

Menu item "Help; About" will open the dialog "About Flight
Reservation System"
About Flight Reservation System

exist: True

4.3 Fax Order No. <n>

4.3.1Functionality
4.3.1.1

Req0051

Click on "Cancel" button will close dialog.

Req0041 "Fax Order No. <x>"; Exists: False

4.3.1.2

Req0052

Clear Signature Button will erase the signature.

Req0042 Agent Signature; bitmap:

4.3.1.3

Req0053

User Clicks Send or Preview Fax with empty fax number or

less than 10 digits.
Req0043a Popup dialog is displayed.
Req0043b Popup title "Flight Reservations"
Req0043c message type: Critical
Req0043d message text "Please complete the fax number."

4.3.1.4

Dani Vainstein

Req0054

Page 28

Software Requirement Specification for Flight Reservation

Page 29

User Clicks Send or Preview Fax with checked field "Send

Signature with order" and without signature.
Req0043a Popup dialog is displayed.
Req0043b Popup title "Flight Reservations"
Req0043c message type: Critical
Req0043d message text "Please sign the fax."

4.4 About Flight Reservations System

4.4.1Gui Defaults
4.4.1.1

Req0055

Req0055a Button "OK"

enabled: True
Req0055b Static "Version" text: "Version 4.0"
Req0055a Icon:
Req0055a image

Figure 16 About Image

4.5 Open Order Process

4.5.1Description
When the Flight Reservation Main window is displayed, the agent is
able to open an existing order for review, update or delete an existing
order.

Dani Vainstein

Page 29

Software Requirement Specification for Flight Reservation

Page 30

Figure 17 Open Order Dialog

By entering an Order No Or a Customer Name Or a Flight Date Or a

combination of Customer Name and Flight Date, the relevant order will
open.
Opening an order by Order No. will open the order directly if it exists.
Opening an order by Customer Name and/Or Flight Date will open a
dialog "Search Results" if more than one matches the description.

Figure 18 Search Results Dialog

4.5.2Functional Requirements
4.5.2.1

Req0056

Req0056a - Check only "Customer Name" option.

"Customer Name" field

Dani Vainstein

enabled: True
focused: True

Page 30

Software Requirement Specification for Flight Reservation

Page 31

"Flight Date" field

enabled: True

"Order No" option

enabled: False

"Order No" field

enabled: False

Req0056b - Check "Order No" option

"Order No" field

enabled: True
focused: True

"Flight Date" field

enabled: False

"Flight Date" option

enabled: False

"Customer Name" option

enabled: False

"Customer Name" field

enabled: False

Req0056c - Check only "Flight Date" option

"Flight Date" field

enabled: True
focused: True

"Customer Name" field

enabled: False

"Customer Name" option

enabled: True

"Order No" option

enabled: False

"Order No" field

enabled: False

Req0056d - Check "Customer Name" and then "Flight Date"

options
"Flight Date" field

Dani Vainstein

Page 31

Software Requirement Specification for Flight Reservation

Page 32

enabled: True
focused: True

"Customer Name" field

enabled: True

"Order No" option

enabled: False

"Order No" field

enabled: False

4.5.2.2

Req0057

Pressing "Cancel" close the dialog

4.5.3Functional Requirements
4.5.3.1

Req0058

Trying to open a non-existing order No. will display a critical

message
Req0058a Popup dialog is displayed.
Req0058b Popup title "Flight Reservations"
Req0058c message type: Critical
Req0058d message text "Order Number < OrderNo > does not
exist"

4.5.3.2

Req0059

Trying to open a non-existing Customer Name will display a

critical message
Req0059a Popup dialog is displayed.
Req0059b Popup title "Flight Reservations"
Req0059c message type: Critical
Req0059d message text "No order found. Please try again "

4.5.3.3

Req0060

Trying to open a non-existing "Flight Date" will display a

critical message
Req0060a Popup dialog is displayed.
Req0060b Popup title "Flight Reservations"
Req0060c message type: Critical

Dani Vainstein

Page 32

Software Requirement Specification for Flight Reservation

Page 33

Req0060d message text "No order found. Please try again "

4.6 Deleting an Order Process

Make your own requirements for this process

4.7 Reporting
4.7.1Description
The flight application supports two report mechanism
1.

Textual Report

2.

Graphical Report

Both are available from the menu and toolbar.

Figure 19 Graphical Report Dialog

4.7.2Graphical User Interface Defaults

4.7.2.1

Req0061

Req0061a Dialog

ispopupwindow: True

Req0061b "Style"

Exists: True

Enabled: True

Index: 1

Label: "File"

SubMenuCount: 4

Req0061c "Style; 2D Bar"

Dani Vainstein

Exists: True

Page 33

Software Requirement Specification for Flight Reservation

Enabled: True

Label: "2D Bar Graph"

HasSubMenu: False

Page 34

Req0061d "Style; 3D Bar"

Exists: True

Enabled: True

Label: "3D Bar Graph"

HasSubMenu: False

Req0061e "Style; 3D Bar"

Exists: True

Enabled: True

Label: "3D Pie Graph"

HasSubMenu: False

Req0061f "Agent Name: <AgentName>

Req0061g "Total Tickets Sold: <TotalTickets>

Dani Vainstein

Page 34