From e00977c9f6b8546acd6c93579dd2b673aa8ef015 Mon Sep 17 00:00:00 2001
From: mjkwiatkowski <mati.rewa@gmail.com>
Date: Wed, 8 Jul 2026 19:29:11 +0200
Subject: feat: added non-functional requirements

---
 content/design.tex | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)

(limited to 'content/design.tex')

diff --git a/content/design.tex b/content/design.tex
index a207089..b14dfec 100644
--- a/content/design.tex
+++ b/content/design.tex
@@ -78,7 +78,7 @@ Based on a subset of the above use-cases, we formulate the functional and non-fu
 	      A system cannot be considered a \gls{dt} without insights stemming from accurate data analytics~\cite{DBLP:usdoe/report/AP26894}.
 	      \gls{nasem} digital twin definition requires both real-time insights, and guidance based on historical-patterns.
 	      Therefore, it is imperative to ensure \textbf{FR3}.
-	\item \textbf{The system should support real-time descriptive data analytics.}\\
+	\item \textbf{The system should support descriptive data analytics.}\\
 	      There are many types of data analytics present is existing deployments~\cite{DBLP:conf/wosp/SumanCNTMI24}.
 	      In order to scope down the project, we only select several use-cases for \gls{my_system}.
 	      Out of the 4 prime analytics type, we find in the literature survey the predictive analytics to be the most urgently needed, and descriptive analytics to be the most prevailing type of data processing.
@@ -100,7 +100,20 @@ Based on a subset of the above use-cases, we formulate the functional and non-fu
 \subsection{Non-functional Requirements}\label{sss:non_functional_requirements}
 In addition to the functional requirements, we also present non-functional requirements for \mysystem:
 \begin{enumerate}[label=\textbf{NFR\arabic* --},align=left]
-	\item \textbf{Datacenter} \\
+	\item \textbf{The system should enable real-time insights and visualizations.} \\
+	      The system must work in real-time, without significant delay.
+	      The system must support datacenter operators with insights at fine-grained granularity, so that insights derived from data analysis remain accurate upon reception by datacenter operators.
+	      Without \textbf{NFR1}, \mysystem's insights will not be timely, and will be useless to datacenter operators.
+	\item \textbf{The system should log the ingestion and processing of metrics.} \\
+	      The system should provide a log of the current network traffic to and from the digital twin.
+
+	\item \textbf{The system should adhere to modern software development standards.} \\
+	      The system should follow modern coding principles and guidelines to ensure reproducibility and usefulness for future work.
+	      Without \textbf{NFR3}, it will be difficult for current and  future digital twin developers to include predictive analytics using \mysystem in their deployments.
+
+	\item \textbf{The system should provide insights at varying levels of confidence.} \\
+	      With the huge amount of telemetry data incoming from the physical twin, the digital counterpart must be able to filter and pre-process the telemetry.
+	      Without \textbf{NFR4}, the system will present overwhelming amount of information to its users, rendering it unusable.
 \end{enumerate}
 
 \section{Design of \emph{Sunfish}}\label{ss:design_of_mysystem}
-- 
cgit v1.2.3

