From 364eb475b98b88cbca6ace69b9701128a7841530 Mon Sep 17 00:00:00 2001 From: narawat Date: Fri, 22 May 2026 06:01:02 +0700 Subject: [PATCH] update --- ASG_Framework.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ASG_Framework.md b/ASG_Framework.md index aadf779..a5fcdcf 100644 --- a/ASG_Framework.md +++ b/ASG_Framework.md @@ -50,10 +50,10 @@ This document defines the documentation framework for a software project. It est - Maintain backward compatibility with existing requirements - Review and update requirements as business context changes -**NFR 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") -- **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") -- NFRs tell you **what to build**; KPIs tell you **how well you built it** +**Requirement vs KPI Clarification**: +- **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 requirement was met (e.g., "Peak traffic was 8.5K TPS", "MTTR was 8 minutes", "100% of connections use TLS 1.3") +- Requirements tell you **what to build**; KPIs tell you **how well you built it** ---