Dekker1/dekker-phd-thesis
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Some notes on structure for the conclusion

Browse Source
This commit is contained in:
Jip J. Dekker 2021-06-21 16:53:29 +10:00
parent 232cac1a81
commit ac7d64292a
No known key found for this signature in database
GPG Key ID: 517DF4A00618C9C3
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
chapters/6_conclusions.tex
View File

@ -2,6 +2,16 @@
\chapter{Conclusions}\label{ch:conclusions} \chapter{Conclusions}\label{ch:conclusions}
%************************************************ %************************************************
This section should probably have the following components:
\begin{itemize}
\item Quick restatement of problem/importance/motivation
\item Contributions, preferrably discussed per section. Relate them back to the research objectives.
\item Limitation and Future work. This can also focus on what my work makes possible, not just what to explore next.
\item Concluding remarks. Maybe a summary of the findings.
\end{itemize}
\par\noindent\rule{\textwidth}{0.4pt}
The work conducted during my candidature presents significant improvements in the infrastructure surrounding the use of high-level constraint modelling languages. The work conducted during my candidature presents significant improvements in the infrastructure surrounding the use of high-level constraint modelling languages.
The implementation of my work can significantly reduce the overhead of the use of these languages. The implementation of my work can significantly reduce the overhead of the use of these languages.