summaryrefslogtreecommitdiff
path: root/content/implementation.tex
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-07-02 21:59:44 +0200
committermjkwiatkowski <mati.rewa@gmail.com>2026-07-02 21:59:44 +0200
commitf0268138b5b29c5c3c098fb74aa92f5e21074213 (patch)
treee7b295cf60b9584a3bf9e28e7f6c77b749a5bfe2 /content/implementation.tex
parentf628c0c3a1ab7ec6f38338c7bc6e1498fe5f1dfa (diff)
feat: added the reference fraud declaration
Diffstat (limited to 'content/implementation.tex')
-rw-r--r--content/implementation.tex12
1 files changed, 10 insertions, 2 deletions
diff --git a/content/implementation.tex b/content/implementation.tex
index 3c2e45a..f55aef1 100644
--- a/content/implementation.tex
+++ b/content/implementation.tex
@@ -5,6 +5,14 @@ After reading one should understand the technical decisions, choice of tools and
Any complex system is more than the sum of its parts~\cite{Wikipedia:article/Systems_Thinking}.
To understand why \gls{my_system} it is crucial to provide a holistic view on the prototype.
-Therefore, the rest of the chapter is structured as follows:
+Therefore, the rest of the chapter is structured in a top-down approach: \Cref{ss:implementation_overview}
+presents the rationale for using the specific software packages, \Cref{ss:data_flow} shows the flow of data within the system, and \Cref{ss:programming} details the different modifications and new software extensions.
-\section{}
+\section{Overview}\label{ss:implementation_overview}
+
+At the onset of the project, we decided \gls{my_system} will use only state-of-the-art software, deployed in the industry or evaluated in peer-reviewed scientific publications.
+In order to facilitate visualizations and interactive dashboards, we decided to use \texttt{Grafana}~\cite{Wikipedia:article/Grafana}.
+
+\section{Data Flow}\label{ss:data_flow}
+
+\section{Code Writing}\label{ss:programming}