The Eatwell Guide is a recommendation given by Public Health England on having a balanced diet. Following and maintaining a diet may be difficult for people, and logging can help them keep track of their plan. However, the task of logging itself can also require a lot of commitment which can cause people inconvenience and make them give it up.
This project aims to develop an application that solves these problems of maintaining a diet plan; this was achieved through months of research and development into users, food and logging, in order to create a fully-integrated and convenient system that does not add a burden onto users, but rather motivates them to adhere to their plan. Considering the time-frame, this project also leaves development open-ended with scope for future work that can be passed over to or taken over by developers who can make use of the open-source side projects created and best practices followed by the system without great difficulty.
To confirm the usability of the application, evaluation was carried out through a survey where participants could share their thoughts with the help of System Usability Scale that also in-turn helps in analysing the results to a score that deemed the system as acceptable.
This document follows the provided template (/dissertation @ 89738d2) that can be found on Overleaf and GitHub. It provides a class module file l4proj.cls with attribution to the authors and modifiers.
\ProvidesClass{l4proj}[%
2009/01/09 Colin Perkins <[email protected]>.%
2009/09/16 Modified by Tim Storer <[email protected]> to support non pdf modes.%
2011/02/15 Modified by Gregg Hamilton <[email protected]> for use in final year projects.%
2012/10/18 Modified by Patrick Prosser, use geometry to control margins, simplified.%
2018/09/14 Modified by John Williamson, improve typographic appearance%
]However, this class has been extended with features such as supporting syntax highlighting for JavaScript, TypeScript, YAML, and TOML using listings (not minted), and autogenerating labels for headings and figures.
Majority of writing and working with LaTeX was with Overleaf, and required a separate repository since branching and symlinks are not supported as of yet (changes are still synchronised here). The chapters have been divided into separate files (using subfiles) in chapters/, and compilation is through pdflatex that requires --shell-escape and inkscape enabled for svg support. Referencing was managed using Zotero and their API, split into separate files. These are added using biblatex with the default numeric style.
%=============================================================================
% CHAPTER NAME
% description about chapter
% ## Guidance
% - Some guidance about the chapter if provided or necessary.
% - This would help in writing and fill criterias.
%=============================================================================
\documentclass[../main.tex]{subfiles}
% \graphicspath{{\subfix{../images/}}}
\begin{document}
% contents ..
\end{document}