Session By:

Valluru
Sreenivasulu
Non-Functional Naidu

Requirements Date:
23-07-2024
Gathering Process Email:
vennelacnu@gm
ail.com
Agenda

Introduction
Critical Requrements
General Requirements
Business Specific Requirements
Environment Requirements (Test & UAT/ Prod)
Workload Model Requirements
Project Specific Contacts Requrirements
Key NFR’s
Pay Attention
 In systems engineering and requirements engineering,
a non-functional requirement is a requirement that
specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors.

Functional requirements define what a software

product must do: its features and functions. An
example of a functional requirement for a messenger
will be something like, “A user must be able to edit
Introduction messages after they are sent.” (Meta, the system must
provide this functionality. Just so you know.)

Nonfunctional requirements specify how the system

must perform. Continuing our messaging platform
example, a nonfunctional requirement can be the
speed with which a system must perform editing to
satisfy user expectations, e.g., “The message must be
updated for all users in a chat within 0.1 seconds,
given that all users are online and have LTE connection
or better.”
 Critical Requirements/Dependency

DEDICATED ENV
SHOULD BE PROVIDED
THERE SHOULD NOT
FOR PT EXECUTION.
BE ANY CHANGE IN
(IN CASES OF A
THE SOURCE CODE TEST BED CREATION
SHARED ENV, THE
AFTER THE HAS TO BE DONE BY
OTHER INSTANCES
ST / SIT SIGN OFF IS SCRIPTING IS THE PROJECT TEAM
SHOULD BE BROUGHT
ENTRY CRITERIA FOR STARTED, AND THE (EG., USERID
DOWN AND THE
PT SCRIPTING SAME SOURCE CODE CREATION, ACCOUNT
APPLICATION
HAS TO BE DEPLOYED NUMBERS ETC.,)
ACCESSES FROM
IN THE TEST
OTHER TEAM HAS TO
EXECUTION
BE SUSPENDED
ENVIRONMENT TOO
DURING PT
EXECUTION)
General Requirements

• Application Name
• Application Short Name
• Project (New/Existing)
• Project ID
• SOW
• SRS/BRS Versions
Business Specific Requirements

Please provide a brief Do you have any specific What are the specific
What performance goals do performance requirements
description of the business areas of performance
you hope to achieve with this for the application? Please
purpose of the application to concerns for this application?
testing? (eg., User load and list the requirements and
be tested? If yes, what are they?
type of tests) indicate if there are any
contractual commitments

Does the load have to be

simulated from different History of PT
Please provide the ST/SIT
geographical location? If so, Tech details(Application
date of Completion
please provide us the location Technologies)
names. (e.g., Chennai or HK)
Environment Requirements
 Business Functions

User Split-up

Pacing time

Workload Think Times

Model
Requriements
Targeted Number of Transactions

Response time SLA’s

Resource Utilization Threshold

Batch Jobs Processing

Project Contact’s Requirements

Primary
Secondary
Escalation

Project Sponser/ Engagement Team

Dev/Application Walk Though/Support Team
Infra/Test Environment Support Team
Other team if any
Performance Testing Team
Key NFR’s

Who are the users of this application (Eg. bank, customers)

Users Geographical distribution of users
Distribution of users across various channels (IVR, ATM, internet, etc)
How are the users connected to the application (WAN, LAN, VPN)
No of Active Users (Current volume) - Avg & Peak
Nof of Simultaneous users (Current volume) - Avg & Peak
Expected no. of active users - Avg & Peak
Expected no. of simultaneous users - Avg & Peak
 Data Volume
• Current Monthly Volume of data - Avg & Peak
• Anticipated Monthly Volume growth - Avg & Peak
• Volume seen in the last 6 months - Avg & Peak
• Database Growth Pattern over 12 months - Avg & Peak
Inter Dependency
• Would the online and batch jobs coexist. Please explain in detail.
• Would any special / ad-hoc reports / queries run which would impact
the online performance of the system.

Response Times

NFR’s • Expected average response time - Please categorize depending on type

of transaction - e.g. enquiries / reporting / data entry etc
• Maximum tolerable response time - lease categorize depending on type
of transaction - e.g. enquiries / reporting / data entry etc
• Is variation in response time accepted for low bandwidth access -
e.g. through dial-up . If so what is the threshold ?

Historical Data:
• If the system is replacing an existing one or current benchmarks for
performance available?
 Scalability Requirements:
• Number of countries to be added over the next/couple of years
• Number of branches to be added over the next few months/years
• Additional functionality to be added over the next/couple of years
• Expected % increase in load per year
• Expected % increase in number of users per year
• Expected % increase in data volume per year

NFR’s Availability Requirements:

• Is the application expected to be available 24 x 7 ?
• Business processes supported by the application ?
• What are the operational hours for the application ?
• What is the acceptable downtime for the application ?
• What is the Business impact in the event of service disruption?
• "Any variation in expected availability component wise ( e.g.
reporting )"
• Is offline access a requirement ? Please elaborate on which aspects
need to have this capability?
 Usability Requirements:
• Categorize different user groups and their profiles
• Are there any special GUI needs for these user groups?
• Can a combination of UI mechanisms - keyboard / mouse etc be
used?
• Does the user prefer long data entry screens or a set of smaller
screens
• What is level of application knowledge required by different

NFR’s groups of users?

• How is the usability of the current application perceived? Are
there any deficiencies or issues that should be addressed?
• What is the user productivity realized by using the current
application?
• If there is a change in GUI, will user re-training impose significant
costs on the organization?
• Are there any priorities with respect to various functions . E.g.
teller / ATM might be having higher priority with respect to back-
office ?
• What is the acceptable session timeout for users ?
 Maintainability Requirements:
• What parts of the current application would see frequent maintenance
activity in terms of functional enhancements, etc?
• Any requirements for parametrization at any level (e.g. screen
definition)
• Is there a requirement to turn ON / OFF certain modules / parameters ?
• Should there be an ability to turn on / off the log files for debugging ?
• Any requirement for rules management / workflow management by
business users

NFR’s Environment Constraints:

• Are there any specific needs the application should use or cater to in
terms of operating systems, hardware, programming languages,
development tools and third-party software in order to protect the
investments made on them?
• Are there any specific network protocols or network software to be
used? Are there any limitations in the network infrastructure that might
have a bearing on the application?
• Is your deployment environment hardware dedicated to this application
in question or is it shared by different applications? If so what and how
many other applications are running on that hardware?
• Is the security infrastructure is shared with other applications? Is there a
need to reuse the existing security infrastructure?
 Monitoring Requirements:
• What is the extent of monitoring required?
(Network, Hardware such as App server, web
server and database server)
• Are there any preferred tools for monitoring?
• Do we require filtering the alerts, notification
messages? What are the ways in which the alerts
NFR’s and notifications take place? (On Screen, Pager
etc)
• What is the extent of monitoring required for the
custom coded software components and adapters?
• What actions would need to be taken when an
exceptional condition is detected by the
monitoring system besides notification?
• Is there an escalation procedure for notification?
Any Questions?