Company Name: Mikasa Sukasa

Slogan: Your Home is our Business

Project Name: Mikasa Sukasa

Non-Functional Requirements Document

Version 1.0
16th March 2021
Document Number:
Contract Number:

Non-Functional Requirements Document 16th March 2021<Pub Date>16th March 2021

Slogan: Your Home is our Business

Non-Functional Requirement Document Sign-off

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

Non-Functional Requirements Document Version 1.0 iii Project Name: Mikasa Sukasa
Record of Changes

Here are the details of the development and distribution of the Non-Functional Requirements
Document. It contains the author of the document, and a comment of why a revised version of
the document was created through the course of the project.

Table 2: Record of Changes

Version
Date Author/Owner Description of Change
Number
Draft 16/04/202 Draft version with available details
1
0.1 16/04/202 Added Business NFR details
1
0.2 16/04/202 Added Quantified NFR details
1

Non-Functional Requirements Document Version 1.0 iv Project Name: Mikasa Sukasa

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 Requirements Document Version 1.0 v Project Name: Mikasa Sukasa

1. Executive Summary

Nonfunctional requirements of a system refer to all important aspects of the system that are
not functional. They indicate how a system performs and not what the system does
(Functional). This document outlines the expected performance of the system against certain
user loads. We also measure the system’s scalability and availability when maximum load is
exceeded. Server-side performance is also documented.

Non-Functional Requirements Document Version 1.0 vi Project Name: Mikasa Sukasa

2. Application Architecture

Overview: System Architecture

The system is an e-commerce platform that allows users to buy any items online. The items are
then delivered to the user’s location.

Architecture Diagram

Non-Functional Requirements Document Version 1.0 vii Project Name: Mikasa Sukasa
3. Performance Test Requirements

Requirements

The system’s performance test will ensure that there are no delays in any functionality of the
system. This will be done by measuring the number of users using the system at a given time.
We will also increase the number of users gradually and measure the system’s performance
upon load increase. We will also note down the CPU performance and performance of the
system when the load spikes.

3.1.1 Business NFR

This section will contain all the non-functional requirements which come from project manager.

Table 3: Business NFR

Business Transactions User Load 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

Non-Functional Requirements

This table contains the quantitative conversion of the Non-Functional Requirements

Table 3: Non-Functional Requirements Detail

Business NFR Type /

NFR # NFR Description
Transactions Category

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

NFR02 Business Performance - The system response time on peak load for user
Process 1 Responsiveness requests, shall be less than 5 seconds for any
individual request

Non-Functional Requirements Document Version 1.0 viii Project Name: Mikasa Sukasa
 Business NFR Type /
NFR # NFR Description
Transactions Category

NFR03 Business Performance – The average count of transactions received by

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

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

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

NFR05 Business Performance – The acceptable limit of the failed transaction

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

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

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

NFR08 Business Scalability – The average count of transactions received by

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

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

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

NFR10 Business Scalability – The acceptable limit of the failed transaction

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

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

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

NFR12 Business Availability – The system response time on average load for
Process 1 Responsiveness user requests, shall be less than 3 seconds for
any individual request

Non-Functional Requirements Document Version 1.0 ix Project Name: Mikasa Sukasa

 Business NFR Type /
NFR # NFR Description
Transactions Category

NFR13 Business Availability – The average count of transactions received by

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

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

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

NFR15 Business Availability – The acceptable limit of the failed transaction

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

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

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

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

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

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

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

Non-Functional Requirements Document Version 1.0 x Project Name: Mikasa Sukasa

 Business NFR Type /
NFR # NFR Description
Transactions Category

NFR21 Business Robustness – A sudden load (spike) of 200% of peak user load
Process 1 User Load must be handled by the system. The duration of
the spike will be 2 minutes after every 15
minutes.

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

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

Process 1 Transaction spike.
Rate

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

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

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

Non-Functional Requirements Document Version 1.0 xi Project Name: Mikasa Sukasa

4. Assumptions, Constraints, Risks and Dependencies

4.1.1 Assumptions

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.1.2 Constraints
Below are the constraints on the NFR associated with the performance tests.

Table 16: Constraints

No. Constraint Impact

1 The Performance Test environment has The scaling factor of the Performance Test
50% of the servers that Production has. to 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
100% Load Test in the Test environment.

4.1.3 Risks
Below are the risks on the available ono-functional requirements associated with the
performance test.

Table 17: Risks

No. Risk Impact Action/Mitigation Assigned To

Non-Functional Requirements Document Version 1.0 xii Project Name: Mikasa Sukasa
4.1.4 Dependencies
Below are the dependencies on the available non-functional requirements associated with the
performance test.

Table 18: Risks

No. Dependencies Impact Action/Mitigation Assigned To

1 Any further details HIGH Unavailability of Project Business
required in business information may add Team
NFR should be provided some delay in the
by the project team timeline

Non-Functional Requirements Document Version 1.0 xiii Project Name: Mikasa Sukasa
Appendix A: Acronyms

Table 21: Acronyms

Acronym Literal Translation

NFR Non-functional Requirement
PT Performance Testing

Non-Functional Requirements Document Version 1.0 xiv Project Name: Mikasa Sukasa
Appendix B: Glossary

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 Requirements Document Version 1.0 xv Project Name: Mikasa Sukasa

Appendix C: Referenced Documents

Table 2: Referenced Documents

Document Name Document Location and/or URL Issuance Date

AO (Architecture https://xxxxxx.xxxxx.com/project_doc 4/16/2021
Overview) ument/architecture/ao.doc
Version: 1.2
Business NFR Document https://xxxxxx.xxxxx.com/project_doc 4/16/2021
Version 0.6 ument/requirement/businessNFR.xls

Non-Functional Requirements Document Version 1.0 xvi Project Name: Mikasa Sukasa