ton/ASG_Framework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
narawat
2026-05-22 06:01:02 +07:00
parent ece7272502
commit 364eb475b9
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ASG_Framework.md
View File

@@ -50,10 +50,10 @@ This document defines the documentation framework for a software project. It est
- Maintain backward compatibility with existing requirements - Maintain backward compatibility with existing requirements
- Review and update requirements as business context changes - Review and update requirements as business context changes
**NFR vs KPI Clarification**: **Requirement vs KPI Clarification**:
- **NFR** is a *requirement* — it defines what quality or constraint the system must have (e.g., "System shall support 10K TPS", "99.9% monthly uptime", "TLS 1.3+ encryption") - **FR and NFR** is a *requirement* — it defines what quality or constraint the system must have (e.g., "System shall support 10K TPS", "99.9% monthly uptime", "TLS 1.3+ encryption")
- **KPI** is a *measurement* — it's the actual data collected to verify if the NFR was met (e.g., "Peak traffic was 8.5K TPS", "MTTR was 8 minutes", "100% of connections use TLS 1.3") - **KPI** is a *measurement* — it's the actual data collected to verify if the requirement was met (e.g., "Peak traffic was 8.5K TPS", "MTTR was 8 minutes", "100% of connections use TLS 1.3")
- NFRs tell you **what to build**; KPIs tell you **how well you built it** - Requirements tell you **what to build**; KPIs tell you **how well you built it**
--- ---