<Company Logo>

<Company Name>
<Company slogan>

<Project Name>
Non-Functional Requirement Template
Version X.X
MM/DD/YYYY

Document Number: <document’s configuration item control number>

Contract Number: <current contract number of company maintaining document>
Non-Functional Requirement Document Sign-off
<List out the name of import stakeholders responsible to sign-off the document>

Table 1: Sign-off Table

Name Role / Designation Signoff Date Signature
Name Project Manager
Name Business Analyst
Name Application Architect
Name Lead Developer
Name Performance Test
Manager
Name xxxxxx
Name xxxxxx

Non-Functional Requirement Template Version X.X ii <Project Name>

Record of Changes
< Provide information on how the development and distribution of the non-functional
requirement document were carried out and tracked with dates. Use the table below to
provide the version number, the date of the version, the author/owner of the version,
and a brief description of the reason for creating the revised version.>

Table 2: Record of Changes

Version
Date Author/Owner Description of Change
Number
Draft 01/11/2018 PerfMatrix Draft version with available details
0.1 15/11/2018 PerfMatrix Added Business NFR details
0.2 30/11/2018 PerfMatrix Added Quantified NFR details
xx xx/xx/xxxx xxxxxx xxxx xxxx xxxx xxx

Non-Functional Requirement Template Version X.X iii <Project Name>

Table of Contents
Non-Functional Requirement Document Sign-off.......................................................ii
Record of Changes....................................................................................................... iii
Table of Contents..........................................................................................................iv
1. Executive Summary..................................................................................................1
1.1 Overview: Project Background and Scope.......................................................1
2. Application Architecture..........................................................................................2
2.1 Overview: System Architecture........................................................................2
2.2 Architecture Diagram....................................................................................... 2
3. Performance Test Requirements.............................................................................3
3.1 Requirements...................................................................................................3
3.1.1 Business NFR.....................................................................................3
3.2 Non-Functional Requirements.........................................................................3
3.3 Other Non-Functional Requirements................................................................6
4. Assumptions, Constraints, Risks and Dependencies...........................................7
4.1.1 Assumptions.......................................................................................7
4.1.2 Constraints..........................................................................................7
4.1.3 Risks...................................................................................................7
4.1.4 Dependencies.....................................................................................8
Appendix A: Acronyms..........................................................................................9
Appendix B: Glossary.......................................................................................... 10
Appendix C: Referenced Documents..................................................................11

Non-Functional Requirement Template Version X.X iv <Project Name>

1. Executive Summary
<Please write here, a summary and the purpose of non-functional requirement
document>

1.1 Overview: Project Background and Scope

<Please write here about the project, application, the purpose of the application,
impacted users, benefits etc.>

Non-Functional Requirement Template Version X.X 5 <Project Name>

2. Application Architecture
<Please write here the summary of the architecture, technology used, impacted
components etc.>

2.1 Overview: System Architecture

<Please write here the detailed description of the application/system>

2.2 Architecture Diagram

<Add architectural diagram of the application in this section>

Non-Functional Requirement Template Version X.X 6 <Project Name>

3. Performance Test Requirements

3.1 Requirements
<Please write here the justification to include the performance testing for this project.
Attach the Performance Score Metrics sheet or MOM in which Performance Testing of
specific or all the components was agreed.>

3.1.1 Business NFR

<This section will contain all the non-functional requirements which come from the
project team. These requirements could be in the layman term or very high level. A
typical example is given in the table>:

<In some cases raw NFRs or High-Level NFRs or Business NFRs are not available, so
delete this section>

Table 3: Business NFR

Business Transactions User Load SLA/response times Transactions per hour

Business Process 1 100 5 seconds 1452

Business Process 2 150 2 seconds 1700

Business Process 3 75 4 second 900

Business Process 4 50 3 seconds 750

Business Process 5 200 3 seconds 1980

3.2 Non-Functional Requirements

<After analyzing the business NFR, refine them and convert into quantitative NFR which should
be written down in the below table>

Table 3: Non-Functional Requirements Detail

Business NFR Type /
NFR # NFR Description
Transactions Category

NFR0 Business Performance – Peak Load: The system must be able to support
1 Process 1 User Load 100 active users.

Non-Functional Requirement Template Version X.X 7 <Project Name>

 Business NFR Type /
NFR # NFR Description
Transactions Category

NFR0 Business Performance - The system response time on peak load for user
2 Process 1 Responsiveness requests, as identified in the figure, shall be less
than 5 seconds for any individual request

NFR0 Business Performance – The average count of transactions received by

3 Process 1 Transaction the system by must be equal to or more than
Rate 1452 transactions per hours.

NFR0 Business Performance – CPU utilization must be less than 60%.

4 Process 1 Server Side
Memory Utilization must not exceed more than
NFR
10%.

NFR0 Business Performance – The acceptable limit of the failed transaction

5 Process 1 Generic count is less than 3% of total transactions
during the test.

NFR0 Business Scalability – Stress (future) Load: The system must be able
6 Process 1 User Load to support 150% of peak time active user load
(=150).

NFR0 Business Scalability – The system response time on future load for
7 Process 1 Responsiveness user requests, as identified in the figure, shall
be less than 5 seconds for any individual
request

NFR0 Business Scalability – The average count of transactions received by

8 Process 1 Transaction the system by must be equal to or more than
Rate 150% of peak time transaction rate (=2178
transactions per hours.)

NFR0 Business Scalability – CPU utilization must be less than 70%.

9 Process 1 Server Side
Memory Utilization must not exceed more than
NFR
14%.

NFR1 Business Scalability – The acceptable limit of the failed transaction

0 Process 1 Generic count is less than 5% of total transactions
during the test.

NFR1 Business Availability – Average Load: The system must be able to

1 Process 1 User Load support 75% of peak time active user load
(=75).

NFR1 Business Availability – The system response time on average load for
2 Process 1 Responsiveness user requests, as identified in the figure, shall
be less than 3 seconds for any individual
request

Non-Functional Requirement Template Version X.X 8 <Project Name>

 Business NFR Type /
NFR # NFR Description
Transactions Category

NFR1 Business Availability – The average count of transactions received by

3 Process 1 Transaction the system by must be equal to or more than
Rate 75% of peak time transaction rate (=1089
transactions per hours.)

NFR1 Business Availability – CPU utilization must be less than 60%.

4 Process 1 Server Side
Memory Utilization must not exceed more than
NFR
10%.
Memory leakage must not occur.

NFR1 Business Availability – The acceptable limit of the failed transaction

5 Process 1 Generic count is less than 5% of total transactions
during the test.

NFR1 Business Capacity The user load must be increased gradually until
6 Process 1 (Break-Point) – the system break-point reached
User Load

NFR1 Business Capacity – Response time must be noted at different user

7 Process 1 Responsiveness load level like:
1. 50 User Load
2. 100 User Load
3. 150 User Load
4. 200 User Load
5. 250 User Load
6. ….. so on

NFR1 Business Capacity – Note down the transaction rate at different user
8 Process 1 Transaction load.
Rate

NFR1 Business Capacity – Note down the CPU utilization at different user
9 Process 1 Server Side load. Check at what point it reaches to 100%.
NFR
Note down the memory utilization at different
user load.

NFR2 Business Capacity – Note down the error count at different user load.
0 Process 1 Generic

NFR2 Business Robustness – A sudden load (spike) of 200% of peak user

1 Process 1 User Load load must be handled by the system. The
duration of the spike will be 2 minutes after
every 15 minutes.

Non-Functional Requirement Template Version X.X 9 <Project Name>

 Business NFR Type /
NFR # NFR Description
Transactions Category

NFR2 Business Robustness – The response time must be noted at every spike
2 Process 1 Responsiveness and that must be less than 6 seconds.

NFR2 Business Robustness – The transaction rate must be noted at every

3 Process 1 Transaction spike.
Rate

NFR2 Business Robustness – CPU utilization must not be more than 80%
4 Process 1 Server Side during spike period.
NFR
Note down the memory utilization at different
user load.

NFR2 Business Robustness – Note down the error count during the spike
5 Process 1 Generic period.

xxxx xxx xxxx xxxxx

<Similarly analyze and write down the NFR for

each business case. NFR must be clear,
quantitative and understandable>

3.3 Other Non-Functional Requirements

<This section contains the other non-functional requirements which are provided by project
team like:
1. Security Testing Requirement
2. Accessibility Testing Requirement
3. Usability Testing Requirement
4. Compatibility Testing Requirement
Ideally, some specific teams are assigned to conduct the respective NFR analysis. The outcome
of the analysis may be written in this section.>

Non-Functional Requirement Template Version X.X 10 <Project Name>

4. Assumptions, Constraints, Risks and Dependencies
4.1.1 Assumptions
<Assumptions should be documented concerning the available non-functional requirement
associated with the performance test. Examples are shown below.>

Table 15: Assumptions

No. Assumption
1 The business NFRs are verified by client, BA, Architecture and Project Manager.
2 The Final NFRs are extracted from business NFRs
3 The Final NFRs are the quantitative NFRs and approved by all the stakeholders.
4 xxxxxxxxxxxxxx

4.1.2 Constraints
<Constraints should be documented concerning the available non-functional requirement
associated with the performance test. Examples are shown below.>

Table 16: Constraints

No. Constraint Impact
1 The Performance Test environment has The scaling factor of the Performance Test to
50% of the servers that Production has. Production is 50%. The user load and
transaction rate NFR are executed in the
Performance Test should be run at 50% of the
full Production load Model to represent a 100%
Load Test in the Test environment.
2 xxxx xxxx

4.1.3 Risks
<Risks should be documented concerning the available non-functional requirement associated
with the performance test. Examples are shown below.>

Table 17: Risks

No. Risk Impact Action/Mitigation Assigned To
1 If there is any change in HIGH Re-design the Project Manager
the NFR during the performance test
performance test cycle scenario
then it may add some
delay in the timelines Delay in performance
testing cycle completion
2 xxxx xxxx xxxx xxxx

Non-Functional Requirement Template Version X.X 11 <Project Name>

4.1.4 Dependencies
<Dependencies should be documented concerning the available non-functional requirement
associated with the performance test. Examples are shown below>

Table 18: Risks

No. Dependencies Impact Action/Mitigation Assigned To
1 Any further details HIGH Unavailability of Project Business
required in business NFR information may add Team
should be provided by the some delay in the
project team timeline
2 xxxx xxxx xxxx xxxx

Non-Functional Requirement Template Version X.X 12 <Project Name>

Appendix A: Acronyms
<List out all the acronyms and associated literal translations used within the document.
List the acronyms in alphabetical order using a tabular format as depicted below.

Table 21: Acronyms

Acronym Literal Translation
NFR Non-functional Requirement
PT Performance Testing

Non-Functional Requirement Template Version X.X 13 <Project Name>

Appendix B: Glossary
<Write down the clear and concise definitions for terms used in this document that may
be unfamiliar to readers of the document. Terms are to be listed in alphabetical order.>

Table 1: Glossary
Term Definition
Transaction Rate The rate at which transaction will be triggered from client to server.
Transaction The bunch of requests associated with a page

Non-Functional Requirement Template Version X.X 14 <Project Name>

Appendix C: Referenced Documents
<List out the documents which were referred during the preparation of Performance
Test plan. Also, provide who and when the reference document was prepared along
with version>

Table 2: Referenced Documents

Document Name Document Location and/or URL Issuance Date
AO (Architecture Overview) https://xxxxxx.xxxxx.com/ 30/10/2018
Version: 1.2 project_document/architecture/ao.doc

Business NFR Document https://xxxxxx.xxxxx.com/ 11/11/2018

Version 0.6 project_document/requirement/
businessNFR.xls

Non-Functional Requirement Template Version X.X 15 <Project Name>