Performance Testing NFR Questionnaire v01

General Initiative Information Description of Information Needed
Initiative name
Please provide a description of the initiative scope,

objectives, and background. This description should
focus on a summary of the functional and technical
changes introduced in the initiative that require
Overview of Initiative performance testing.
High Impact? (yes/no) Complexity of the Initiative
Plan View Project#
Change Record #
Production Target Date
Proposed Testing Schedule
TDM Technical Delivery Manager
TDL Technical Delivery Lead
Technical Architect Technical Architect for the Project
Capacity
WAS Team Support
Environment Support
SystemTesting Start Date
Link to Project Folder(s) Path for accessing the project specific documents
Path for accessing the business requirement
Link to BRD document
Path for accessing the high level or technical design
Link to HLD document
Link to LLD
Link to Production Diagrams
Link to Environment Diagrams/
Architecural Diagram
Impacted Applications
System Flow Diagram
URL for Test Environment
Test Environment Hardware Scale
Test Environment location
For example: Is this performance testing, proof of

concept, improve phase tesing, etc…List what is
Objective of Tech Testing expected of tech test by doing this test, for example,
API performance meets SLA’s, determine impact on
processing capacity if Webshpere components, etc.
Please provide a quick overview on what you would
like to have accomplished by completing the
Performance Testing phase.
For example: The introduction of a new
architecture/component for which scalability has not
Overview of potential performance impact been previously demonstrated in the Prod
environment;
New usage patterns which represent large magnitude
increases over previous usage patterns; New page
component that could potentially increase page load
time
Project Response
Informational Request
Project Background Information
Known Issues
Are new tables being introduced
Logistics and other related testing information

Description of information needed
Please provide detailed background information about

this initiative
Please list out any known issues that is related to this

initiative
If yes, Volume of data to be pre-populated
Does the project need data that are required to be in

sync? If so, this may not be performed by Performance
Testing Team but will require additional coordination
between support, development and data processing
teams if any.
Do you anticipate needing data mining to satisfy test

conditions for performance testing?
What types of data conditions do you need? Please be as
specific as you can.
How many of each condition do you need?
What data fields do you need?
Ø Account number?
Ø ZIP Code?
Ø Phone numbers?
Ø Expiration number? etc…….
What type of volumes of data do you anticipate?
When will you do shakeout? Do you just need samples of

data for that (volume to be provided later)?
Are there conditions that you need not listed in the

examples?
Ø Provide Test Script Name: e.g., SRS Business, etc…

data condition? e.g., "Claims number must have 0
promos".
Ø Provide data condition: e.g., "Claims number must

have 0 promos".
Ø Provide Data needed as input to Script: e.g.,
"Policy number".
Project Manager
Development Lead
Functional Testing Lead
Project Response
Required Deliverables
Key Questions
Test Data Mine / Sync Notes:
Infrastructure / Architectural Changes Notes:
TESTLAB Managed Environments Notes:
Use Case
Usecase: <Insert Name of Script>
Step Description Target Response Time
Average Daily Volume

Peak Daily Volume
Service/API Inbound or Outbound?
Data Mining / Use Cases / API Mapping
Test Users Details

Storage Server Name Database Reference
Test Data Details

Storage Server Name Database Reference
XML’s for new services/calls being introduced:

Data Conditioning
If data is needing conditioning by PT Team to accommodate testing this initiative, please note below.
First give API that conditioning is needed for:

API / Usecase Name Process
Requested Test Name
Environment Server Names

Throughput (TPH/TPM/TPS) Description Duration:
Transact Type Expected Response Time Protocol
Short Description Dependancies Affected Use Case
Short Description Dependancies Affected Use Case

e below.
Type Purpose
Component Is this component meeting

expectations?
Is this component reasonably
well optimized?
Is the observed performance
issue caused by this
component?
Capacity Is system capacity meeting

business volume under 25%
peak load conditions?
Stress What happens if the

production load exceeds the
anticipated load?
What kinds of failures should
we plan for?
What indicators should we look
for in order to intervene prior
to failure?
Endurance Will performance be consistent

over time?
Are there slowly growing
problems that have not yet
been detected?
Is there external interference
that was not accounted for?
Number Purpose Shared Yes/No?

How many users typically access the system?
< 50 - Update in NFR
50 – 1000 - Update in NFR, > 1000 - Update in NFR
End point url for SOAP request New or Modified?
SQL Statement(s) SME
SQL Statement(s) SME

CPU Type Number of CPU's
Operating System and Version Server Model Notes

Performance Testing NFR Questionnaire v01

Uploaded by

Copyright:

Available Formats

Performance Testing NFR Questionnaire v01

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Performance Testing NFR Questionnaire v01

Uploaded by

Copyright:

Available Formats

General Initiative Information Description of Information Needed

Please provide a description of the initiative scope,

For example: Is this performance testing, proof of

Project Background Information

Are new tables being introduced

Logistics and other related testing information

Please provide detailed background information about

Please list out any known issues that is related to this

If yes, Volume of data to be pre-populated

Does the project need data that are required to be in

Do you anticipate needing data mining to satisfy test

What type of volumes of data do you anticipate?

When will you do shakeout? Do you just need samples of

Are there conditions that you need not listed in the

Ø Provide Test Script Name: e.g., SRS Business, etc…

Ø Provide data condition: e.g., "Claims number must

Average Daily Volume

Service/API Inbound or Outbound?

Data Mining / Use Cases / API Mapping

Test Users Details

Test Data Details

XML’s for new services/calls being introduced:

First give API that conditioning is needed for:

Requested Test Name

Environment Server Names

Transact Type Expected Response Time Protocol

Short Description Dependancies Affected Use Case

Short Description Dependancies Affected Use Case

Component Is this component meeting

Capacity Is system capacity meeting

Stress What happens if the

Endurance Will performance be consistent

Number Purpose Shared Yes/No?

End point url for SOAP request New or Modified?

SQL Statement(s) SME

SQL Statement(s) SME

You might also like