summaryrefslogtreecommitdiff
path: root/content/design.tex
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-07-15 15:56:09 +0200
committermjkwiatkowski <mati.rewa@gmail.com>2026-07-15 15:56:09 +0200
commitd4c3a916398e4eee9c1eaaa840968d4b19f40c91 (patch)
treedc5e43afc055545b5bf687ff90576e9356e91168 /content/design.tex
parent0018fdbff007f689e9cd7d877d72db4fd308b65f (diff)
feat: finished section 2.4.3
Diffstat (limited to 'content/design.tex')
-rw-r--r--content/design.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/design.tex b/content/design.tex
index 2eb195d..4fbb1b4 100644
--- a/content/design.tex
+++ b/content/design.tex
@@ -12,7 +12,7 @@
\end{mynote}
\section{Requirements Analysis}\label{ss:requirements_analysis}
In this section we determine the requirements that should be fulfilled by \mysystem.
-We present here the stakeholders identified by our literature survey (see \Cref{sss:digital_twins_for_datacenters}) and the relevant use-cases.
+We present here the stakeholders identified by our literature survey (see \Cref{ss:digital_twins_for_datacenters}) and the relevant use-cases.
Afterwards, we list the functional and non-functional requirements for \mysystem.
\subsection{Stakeholders}\label{sss:stakeholders}