diff options
| author | mjkwiatkowski <mati.rewa@gmail.com> | 2026-07-08 13:58:32 +0200 |
|---|---|---|
| committer | mjkwiatkowski <mati.rewa@gmail.com> | 2026-07-08 13:58:32 +0200 |
| commit | 071356f9c510dc83f23984558855f7efe8e6fdd9 (patch) | |
| tree | 91341bbf1816b2e2c1c689ee0e5809efb133126a | |
| parent | 3a81b76d1b22c0109b6f3d81c83af91378fb8800 (diff) | |
feat: added the structure to chapter 3
| -rw-r--r-- | content/design.tex | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/content/design.tex b/content/design.tex index a6fd23f..d4473b0 100644 --- a/content/design.tex +++ b/content/design.tex @@ -9,6 +9,37 @@ \end{enumerate} \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. +Afterwards, we list the functional and non-functional requirements for \mysystem. + +\subsection{Stakeholders}\label{sss:stakeholders} +\begin{enumerate}[label=\textbf{S\arabic*:},align=left] + \item \textbf{Datacenter} \\ +\end{enumerate} + +\subsection{Use-cases}\label{sss:use_cases} +\begin{enumerate}[label=\textbf{UC\arabic*:},align=left] + \item \textbf{Datacenter} \\ +\end{enumerate} + +\subsection{Functional Requirements}\label{sss:functional_requirements} +\begin{enumerate}[label=\textbf{FR\arabic*:},align=left] + \item \textbf{Datacenter} \\ +\end{enumerate} + +\subsection{Non-functional Requirements}\label{sss:non_functional_requirements} +\begin{enumerate}[label=\textbf{NFR\arabic*:},align=left] + \item \textbf{Datacenter} \\ +\end{enumerate} + \section{Design of \emph{Sunfish}}\label{ss:design_of_mysystem} + +\subsection{Digital Thread} + +\subsection{Data Storage} + +\subsection{Predictive Analytics Module} + \section{Discussion}\label{ss:design_discussion} |
