<aside> 💡 This is the template for software engineering teams to define their Non-Functional Requirements. If you are looking for the inspiration about how to introduce NFRs to your work, check this article: https://www.practicalengineering.management/p/non-functional-requirements

</aside>

🗓️ Document Change Log

📄 Document Overview

🎯 Purpose

This document outlines the non-functional requirements crucial for our technology stack's long-standing success. These requirements ensure that the system's performance, usability, security, and other quality attributes meet the stakeholders' expectations and the end users' needs.

🔍 Scope

The document covers non-functional requirements for the backend, frontend, and mobile components.

🛠️ NFRs

⚙️ Backend NFRs

Performance

• Requirement: Response time for APIs should not exceed 2 seconds under normal load conditions.
• Measurement: Use Grafana dashboards to monitor response times.
• Target: 95% of requests within 2 seconds.

Scalability

• Requirement: The system should automatically scale to handle a 10x increase in user traffic.
• Measurement: Simulate increased loads using Gatling testing.
• Target: Automatic scaling without human intervention.