Skip to content
Snippets Groups Projects
Commit 7a5cce8f authored by jda1g15's avatar jda1g15
Browse files

Merge branch 'final_report' into 'master' 

Final report

See merge request !1
parents 03189d47 62d7bcab
No related branches found
No related tags found
1 merge request!1Final report
Show whitespace changes
Inline Side-by-side
Showing
with 5873 additions and 48 deletions
report/6_Chapter6.tex deleted 100644 → 0
+ 0
− 4
View file @ 03189d47
%% ----------------------------------------------------------------
%% Chapter6.tex
%% ----------------------------------------------------------------
\chapter{Results and Analysis} \label{Chapter:six}
\ No newline at end of file
report/6_TestingAndSoftwareValidation.tex 0 → 100644
+ 77
− 0
View file @ 7a5cce8f
%% ----------------------------------------------------------------
%% 6_TestingAndSoftwareValidation.tex
%% ----------------------------------------------------------------
\chapter{TESTING AND SOFTWARE VALIDATION}
Verification and validation are essential parts of any software project. Consequently, multiple different methods for testing the application have been employed to confirm that the application is fully functional and robust, from manual and automated to user and requirements testing.
\section{Verification}
Verification tests have been carried to make sure that all functionality has been implemented in the project to meet the requirements of the target users.
\subsection{Requirements testing}
\begin{table}[H]
\centering
\begin{tabular}{|c|c|c|c|}
\hline
Requirement & Expectation & Outcome & Result\\
\hline
\hline
\makecell{Register} & \makecell{Use email address to\\create an account} & \makecell{Users are able to use their\\email address to create a\\persistent account} & \cellcolor{green}\checkmark\\
\hline
\makecell{Sign in} & \makecell{Use email address and\\password created at sign\\up to sign in} & \makecell{Users are able to login} & \cellcolor{green}\checkmark\\
\hline
\makecell{Sign out} & \makecell{Sign out of account\\so that account is\\no longer accessible\\without signing back in} & \makecell{On clicking the sign out\\button the user is no\\longer able to access\\their account without\\logging back in} & \cellcolor{green}\checkmark\\
\hline
\makecell{Create Form} & \makecell{Create a custom\\compliance form which is\\stored in association\\with the user's account} & \makecell{Ability to create a compliance\\form which is stored and\\associated with the user's\\account} & \cellcolor{green}\checkmark\\
\hline
\makecell{View Form} & \makecell{View created forms} & \makecell{Users can view their own\\forms and those of other\\users that have been shared\\with them.} & \cellcolor{green}\checkmark\\
\hline
\makecell{Share Form} & \makecell{Share a form created\\by the user with\\another user} & \makecell{Sharing a form with\\another user allows that\\ user to view, fill out and\\return a form submission} & \cellcolor{green}\checkmark\\
\hline
\makecell{Edit Form} & \makecell{Edit the questions and\\responses of created forms.} & \makecell{Requirement dropped due\\to time constraints as it\\was not a part of the MVP.} & \cellcolor{red}\texttimes\\
\hline
\makecell{Delete Form} & \makecell{Delete a form created\\by the user} & \makecell{Deleting a form that\\was originally created by\\that user. Unable to\\delete forms created\\by other users} & \cellcolor{green}\checkmark\\
\hline
\makecell{Form Submission} & \makecell{To return a user's responses\\to a form to its author} & \makecell{Users can select responses\\for each form's questions\\and submit their responses\\to the form's author} & \cellcolor{green}\checkmark\\
\hline
\makecell{Add Partner} & \makecell{To search and add another\\user as a partner} & \makecell{Requirement dropped due\\to time constraints as it\\was not a part of the MVP.} & \cellcolor{red}\texttimes\\
\hline
\end{tabular}
\caption{Requirements testing}
\end{table}
\section{Validation}
To ensure that CompForge met the functional requirements specified in chapter 2, and to establish the absence of bugs, the application was evaluated using an automated test suite.
\subsection{Manual Testing}
The most straightforward way to test the application was to simply use it. Listed below are the steps taken to manually test CompForge.
\begin{itemize}
\item Accounts 1, 2 \& 3 created.
\item Account 1 creates and shares Forms 1 \& 2 with the other accounts.
\item Account 1 \& 2 view Form 1.
\item Account 1 deletes Form 1.
\item Accounts 1 \& 2 verify Form 1 is no longer visible.
\item Account 2 creates a submission for Form 2.
\item Account 1 views the submission from Account 2 for Form 2.
\item Account 3 verifies that it can view Form 2, but not the submission for Form 2, and that it does not have the ability to delete Form 2.
\item Account 3 creates a submission for Form 2.
\item Account 1 verifies that there are 2 separate, viewable submissions of Form 2, for Accounts 2 \& 3.
\end{itemize}
\subsection{Robot Framework}
The testing and validation of the application was done using Robot Framework. Robot Framework is a generic, open source, automation framework for acceptance testing \cite{Robot}, developed with Python. The framework has many libraries that extend its functionality, and one such library is Selenium, which was used extensively to automatically drive the application's user interface.
\subsubsection{Integration}
TODO:
How robot was integrated into the project
\subsubsection{Testing Writing}
TODO:
The process of planning and implementing tests
Test cases etc
\subsubsection{Results}
TODO:
Insert the beautiful HTML results page (and discuss?)
\ No newline at end of file
report/7_Chapter7.tex deleted 100644 → 0
+ 0
− 4
View file @ 03189d47
%% ----------------------------------------------------------------
%% Chapter7.tex
%% ----------------------------------------------------------------
\chapter{Evaluation} \label{Chapter:seven}
\ No newline at end of file
report/7_Evaluation.tex 0 → 100644
+ 129
− 0
View file @ 7a5cce8f
%% ----------------------------------------------------------------
%% 7_Evaluation.tex
%% ----------------------------------------------------------------
\chapter{EVALUATION}
This chapter will evaluate the project by critical evaluation and will discuss the results of the requirements testing, taking into consideration issues that were faced during implementation.
\section{Critical Evaluation}
While React was a good choice from a development and maintenance point of view, it would probably have been more prudent to use a language/library/framework with which I was already more familiar. Whilst a great deal was learned from the implementation of this project, it was significantly delayed - in part due to the time required to learn how to properly use the React library, including React Router and Redux/Thunk.
With regard to the outcome of the project versus the initial functional requirements, the project is functional because all of the components identified as the MVP have been implemented, however with the obvious downfall that some features, namely adding partners and editing forms, were not implemented which was disappointing, albeit unavoidable, given the delays.
\section{Project Management}
Some of the first parts of the project actually progressed ahead of schedule, such as the creation of the initial Gantt chart. Until the deadline for the progress report in December, the project was progressing on schedule. Understandably, the implementation, testing and final report write up were severely impacted by the university closure from the 23rd March onwards, due to the spread of COVID-19. This, coupled with delays during the implementation caused by an underestimation of the learning curve of the technologies that were used, resulted in much of the remainder of the project being completed behind schedule.
\subsection{Gantt Chart}
The initial Gantt chart is represented by the cells in blue, with the aforementioned delays to the project represented in orange. Major components are represented in a darker shade of each colour, with each subcomponent represented by respective lighter shades. For readability, it has been split over two pages.
\begin{sidewaystable}[h]
\centering
\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
\hline
Component & Subcomponent & October & November & December & January & February & March & April & May\\
\hline
\hline
Project Brief & & \cellcolor{RoyalBlue} & & & & & & & \\
\hline
& Background Research & \cellcolor{Cyan} & & & & & & & \\
\hline
& Write up & \cellcolor{Cyan} & & & & & & & \\
\hline
\hline
\makecell{Time Management\\Planning} & & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & & & & & \\
\hline
& Gantt Chart & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Cyan} & & & & & \\
\hline
\hline
Research & & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & & & & & \\
\hline
& \makecell{Further\\background research} & \cellcolor{Cyan} & \cellcolor{Cyan} & & & & & & \\
\hline
& Literature review & & \cellcolor{Cyan} & \cellcolor{Cyan} & & & & & \\
\hline
\hline
Design & & & \cellcolor{RoyalBlue} & & & & & & \\
\hline
& Planning diagrams & & \cellcolor{Cyan} & & & & & & \\
\hline
\hline
Progress Report & & & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & & & & & \\
\hline
& Write up & & \cellcolor{Cyan} & \cellcolor{Cyan} & & & & & \\
\hline
\hline
Implementation & & & & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{BurntOrange} & & \\
\hline
& Sign up & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & & & \\
\hline
& Sign in & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & & & \\
\hline
& Sign out & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & & & \\
\hline
& Create form & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & & \\
\hline
& Delete form & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & & \\
\hline
& View form & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & & \\
\hline
& Share form & & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & \\
\hline
& Submit form & & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & \\
\hline
& View submissions & & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & & \\
\hline
\end{tabular}
\caption{Gantt Chart}
\end{sidewaystable}
\pagebreak
\begin{sidewaystable}[h]
\centering
\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
\hline
Component & Subcomponent & October & November & December & January & February & March & April & May\\
\hline
\hline
\makecell{Testing and\\Validation} & & & & & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{BurntOrange} & \cellcolor{BurntOrange} & \\
\hline
& Robot Framework setup & & & & \cellcolor{Cyan} & \cellcolor{Apricot} & \cellcolor{Apricot} & \cellcolor{Apricot} & \\
\hline
& Test Implementation & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot} & \cellcolor{Apricot} & \\
\hline
Final Report & & & & & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{RoyalBlue} & \cellcolor{BurntOrange}\\
\hline
& Introduction & & & \cellcolor{Cyan} & & & & & \\
\hline
& \makecell{Background and\\Literature Review} & & & \cellcolor{Cyan} & & & & & \\
\hline
& Designs & & & \cellcolor{Cyan} & & & & & \\
\hline
& Implementation & & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot} & \\
\hline
& Testing and software validation & & & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot} \\
\hline
& Results and Analysis & & & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot} \\
\hline
& Evaluation & & & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot}\\
\hline
& Project management & & & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot}\\
\hline
& Conclusions & & & & & & \cellcolor{Cyan} & \cellcolor{Cyan} & \cellcolor{Apricot}\\
\hline
& Future work & & & & & & & \cellcolor{Cyan} & \cellcolor{Apricot}\\
\hline
& Bibliography & & & & & & & \cellcolor{Cyan} & \cellcolor{Apricot}\\
\hline
& Appendices & & & & & & & \cellcolor{Cyan} & \cellcolor{Apricot}\\
\hline
\hline
\makecell{\st{Project Viva}\\(cancelled)} & - & - & - & - & - & - & - & \cellcolor{RoyalBlue} - & - \\
\hline
- & \st{Viva} & - & - & - & - & - & - & \cellcolor{Cyan} - & - \\
\hline
\end{tabular}
\caption{Gantt Chart cont.}
\end{sidewaystable}
\ No newline at end of file
report/8_Chapter8.tex deleted 100644 → 0
+ 0
− 6
View file @ 03189d47
%% ----------------------------------------------------------------
%% Chapter8.tex
%% ----------------------------------------------------------------
\chapter{Project Management} \label{Chapter:eight}
It works.
report/8_Conclusions.tex 0 → 100644
+ 27
− 0
View file @ 7a5cce8f
%% ----------------------------------------------------------------
%% 9_Conclusions.tex
%% ----------------------------------------------------------------
\chapter{CONCLUSION} \label{Chapter: Conclusions}
This project aimed to enable SMEs to create and customise their own compliance forms in order to stay up to date with the latest cyber security standards, as well as ensure that their partner organisations and other organisations in their supply chain are keeping to those same standards. CompForge has lowered the time and cost required to perform these tasks, with a user-friendly UI and real time updates from the application's Firestore database.
\section{Improvements}
After evaluating the application and comparing it to competitors, a number of improvements that could be made have come to mind.
The ability to edit forms that have already been created, would be a useful tool in case a mistake is found, or an update is required. This is to be expected in the continuously growing field of cyber security, as doubtless many of the standards that are active today will change with time as technology continues to move forward along with the threats.
On the same vein, it would be useful to add the ability to share a form with new partners after it has been created. Organisations change and grow, and it could be necessary to share a form with additional organisations.
To save time, another useful feature would be the ability to add partners in a similar way to adding a friend on a social media platform. There would be no need to look up email addresses every time you needed to share a new form with an existing partner.
Finally, the number of forms you can create and share is technically infinite, so a search bar and sorting filter would both be useful additions to the application.
\section{Future Work}
Further to the above improvements, there are some more major improvements that could be made with future work.
Specifically, a feature that allows a user to export form templates and specific submissions from partners to a particular format. Users may wish to print another user's submission to their form or share a form template with another user.
Conversely, the ability to import existing form templates would allow users to share popular standards such as; ISO/IEC 27001, Cloud Controls Matrix, the Cyber Essentials Scheme, or its progeny, IASME.
Finally, the use of email notifications to notify users when a form has been shared with them, or when a partner has made a submission would be convenient, as it is unlikely a user will have the application open at all times.
\ No newline at end of file
report/12_Appendices.tex → report/99_Appendix.tex
+ 1
− 1
View file @ 7a5cce8f
%% ---------------------------------------------------------------- %% ----------------------------------------------------------------
%% Appendices.tex %% Appendix.tex
%% ---------------------------------------------------------------- %% ----------------------------------------------------------------
\chapter{Appendix A: Photos} \label{appendix1} \chapter{Appendix A: Photos} \label{appendix1}
This is an appendix This is an appendix
......
report/9_Conclusions.tex deleted 100644 → 0
+ 0
− 5
View file @ 03189d47
%% ----------------------------------------------------------------
%% Conclusions.tex
%% ----------------------------------------------------------------
\chapter{Conclusions} \label{Chapter: Conclusions}
It works.
report/master.bbl 0 → 100644
+ 121
− 0
View file @ 7a5cce8f
% Generated by IEEEtran.bst, version: 1.12 (2007/01/11)
\begin{thebibliography}{10}
\providecommand{\url}[1]{#1}
\csname url@samestyle\endcsname
\providecommand{\newblock}{\relax}
\providecommand{\bibinfo}[2]{#2}
\providecommand{\BIBentrySTDinterwordspacing}{\spaceskip=0pt\relax}
\providecommand{\BIBentryALTinterwordstretchfactor}{4}
\providecommand{\BIBentryALTinterwordspacing}{\spaceskip=\fontdimen2\font plus
\BIBentryALTinterwordstretchfactor\fontdimen3\font minus
\fontdimen4\font\relax}
\providecommand{\BIBforeignlanguage}[2]{{%
\expandafter\ifx\csname l@#1\endcsname\relax
\typeout{** WARNING: IEEEtran.bst: No hyphenation pattern has been}%
\typeout{** loaded for the language `#1'. Using the pattern for}%
\typeout{** the default language instead.}%
\else
\language=\csname l@#1\endcsname
\fi
#2}}
\providecommand{\BIBdecl}{\relax}
\BIBdecl
\bibitem{CSCRM}
\BIBentryALTinterwordspacing
S.~Boyson, ``Cyber supply chain risk management: Revolutionizing the strategic
control of critical it systems.'' [Online]. Available:
\url{https://www.sciencedirect.com/science/article/pii/S0166497214000194}
\BIBentrySTDinterwordspacing
\bibitem{CyberEssentials}
\BIBentryALTinterwordspacing
GOV.UK, ``Cyber essentials scheme: Overview,'' 2014. [Online]. Available:
\url{https://www.gov.uk/government/publications/cyber-essentials-scheme-overview}
\BIBentrySTDinterwordspacing
\bibitem{GDPR}
\BIBentryALTinterwordspacing
J.~Zerlang, ``Gdpr: a milestone in convergence for cyber-security and
compliance,'' 2017. [Online]. Available:
\url{https://www.sciencedirect.com/science/article/pii/S1353485817300600}
\BIBentrySTDinterwordspacing
\bibitem{CombattingCyberRisks}
\BIBentryALTinterwordspacing
D.~Shackleford, 2015. [Online]. Available:
\url{https://www.raytheon.com/sites/default/files/capabilities/rtnwcm/groups/cyber/documents/content/rtn_273005.pdf}
\BIBentrySTDinterwordspacing
\bibitem{ComplianceGovernance}
\BIBentryALTinterwordspacing
S.~et~al., ``Aiding compliance governance in service-based business
processes,'' in \emph{Handbook of Research on Service-Oriented Systems and
Non-Functional Properties: Future Directions}, 2012, pp. 524--548. [Online].
Available:
\url{https://www.igi-global.com/chapter/handbook-research-service-oriented-systems/60900}
\BIBentrySTDinterwordspacing
\bibitem{StanfordConsortium}
\BIBentryALTinterwordspacing
e.~a. Elliott, ``Consrotium for research on information security and policy,''
1998-2001. [Online]. Available:
\url{https://fsi.stanford.edu/research/consortium_for_research_on_information_security_and_policy}
\BIBentrySTDinterwordspacing
\bibitem{CyberCrime}
\BIBentryALTinterwordspacing
N.~C. Agency, ``Cyber crime.'' [Online]. Available:
\url{https://www.nationalcrimeagency.gov.uk/what-we-do/crime-threats/cyber-crime}
\BIBentrySTDinterwordspacing
\bibitem{ITGovernance}
\BIBentryALTinterwordspacing
I.~Governance, ``Customers lose confidence - data breaches aren't just about
fines,'' 2018. [Online]. Available:
\url{https://www.itgovernance.co.uk/blog/customers-lose-confidence-data-breaches-arent-just-about-fines}
\BIBentrySTDinterwordspacing
\bibitem{BusinessInfo}
\BIBentryALTinterwordspacing
p.~b. I. N.~I. nibusinessinfo.co.uk, ``Cyber security for business.'' [Online].
Available:
\url{https://www.nibusinessinfo.co.uk/content/impact-cyber-attack-your-business}
\BIBentrySTDinterwordspacing
\bibitem{z6mag}
\BIBentryALTinterwordspacing
z6mag, ``Two cashback sites leaked data of 3.5 million users.'' [Online].
Available:
\url{https://z6mag.com/2019/10/16/two-cashback-sites-leaked-data-of-3-5-million-users/}
\BIBentrySTDinterwordspacing
\bibitem{Formstack}
\BIBentryALTinterwordspacing
Formstack. [Online]. Available: \url{https://formstack.com/}
\BIBentrySTDinterwordspacing
\bibitem{DeviceMagic}
\BIBentryALTinterwordspacing
D.~Magic. [Online]. Available: \url{https://devicemagic.com/}
\BIBentrySTDinterwordspacing
\bibitem{Personas}
Usability.gov.
\bibitem{React}
\BIBentryALTinterwordspacing
Facebook. [Online]. Available: \url{https://reactjs.org/}
\BIBentrySTDinterwordspacing
\bibitem{Firebase}
\BIBentryALTinterwordspacing
Google. [Online]. Available: \url{https://firebase.google.com/}
\BIBentrySTDinterwordspacing
\bibitem{Robot}
\BIBentryALTinterwordspacing
R.~F. Foundation. [Online]. Available: \url{https://www.robotframework.org/}
\BIBentrySTDinterwordspacing
\end{thebibliography}
report/master.bib
+ 98
− 0
View file @ 7a5cce8f
...@@ -6,3 +6,101 @@ ...@@ -6,3 +6,101 @@
title = {PDFLaTeX Instructions}, title = {PDFLaTeX Instructions},
url = {http://www.ecs.soton.ac.uk/~srg/softwaretools/document/} url = {http://www.ecs.soton.ac.uk/~srg/softwaretools/document/}
} }
@article{CSCRM,
author = {Boyson, Sandor},
title = {Cyber supply chain risk management: Revolutionizing the strategic control of critical IT systems},
url = {https://www.sciencedirect.com/science/article/pii/S0166497214000194}
}
@incollection{ComplianceGovernance,
author = {Silveira et al.},
title = {Aiding Compliance Governance in Service-Based Business Processes},
year = {2012},
pages = {524-548},
booktitle = {Handbook of Research on Service-Oriented Systems and Non-Functional Properties: Future Directions},
url = {https://www.igi-global.com/chapter/handbook-research-service-oriented-systems/60900}
}
@document{CombattingCyberRisks,
author = {Shackleford, Dave},
publisher = {SANS Whitepaper},
year = {2015},
url = {https://www.raytheon.com/sites/default/files/capabilities/rtnwcm/groups/cyber/documents/content/rtn_273005.pdf}
}
@misc{CyberCrime,
author = {National Crime Agency},
title = {Cyber Crime},
url = {https://www.nationalcrimeagency.gov.uk/what-we-do/crime-threats/cyber-crime}
}
@misc{CyberEssentials,
author = {GOV.UK},
title = {Cyber Essentials Scheme: Overview},
year = {2014},
url = {https://www.gov.uk/government/publications/cyber-essentials-scheme-overview}
}
@misc{StanfordConsortium,
author = {Elliott, et al.},
title = {Consrotium for Research on Information Security and Policy},
year = {1998-2001},
url = {https://fsi.stanford.edu/research/consortium_for_research_on_information_security_and_policy}
}
@article{GDPR,
author = {Zerlang, Jesper},
title = {GDPR: a milestone in convergence for cyber-security and compliance},
issue = {6},
year = {2017},
url = {https://www.sciencedirect.com/science/article/pii/S1353485817300600}
}
@misc{ITGovernance,
author = {IT Governance},
title = {Customers lose confidence - data breaches aren't just about fines},
year = {2018},
url = {https://www.itgovernance.co.uk/blog/customers-lose-confidence-data-breaches-arent-just-about-fines}
}
@misc{BusinessInfo,
author = {nibusinessinfo.co.uk, provided by Invest Northern Ireland},
title = {Cyber security for business},
url = {https://www.nibusinessinfo.co.uk/content/impact-cyber-attack-your-business}
}
@misc{Robot,
author = {Robot Framework Foundation},
url = {https://www.robotframework.org/}
}
@misc{z6mag,
author = {z6mag},
title = {Two cashback sites leaked data of 3.5 million users},
url = {https://z6mag.com/2019/10/16/two-cashback-sites-leaked-data-of-3-5-million-users/}
}
@misc{React,
author = {Facebook},
url = {https://reactjs.org/}
}
@misc{Firebase,
author = {Google},
url = {https://firebase.google.com/}
}
@misc{Formstack,
author = {Formstack},
url = {https://formstack.com/}
}
@misc{DeviceMagic,
author = {Device Magic},
url = {https://devicemagic.com/}
}
@misc{Personas,
author = {Usability.gov},
url = {https://usability.gov/how-to-and-tools/methods/personas.html}
\ No newline at end of file
report/master.dvi
+ 0
− 0
View file @ 7a5cce8f
No preview for this file type
report/master.pdf
+ 0
− 0
View file @ 7a5cce8f
No preview for this file type
report/master.tex
+ 19
− 25
View file @ 7a5cce8f
...@@ -8,33 +8,31 @@ ...@@ -8,33 +8,31 @@
%% ---------------------------------------------------------------- %% ----------------------------------------------------------------
\begin{document} \begin{document}
\frontmatter \frontmatter
\title {Electronics and Computer Science\\Faculty of Engineering and Physical Sciences\\University of Southampton} \title {Automatically Generated Cyber Security Compliance Engine}
\authors { \authors {
{James D'Alton} {James D'Alton}
} }
\addresses {\groupname\\\deptname\\\univname} \addresses {\groupname\\\deptname\\\univname}
\date {October 21st, 2019} \date {19 May 2020}
\subject {Automatically Generated Cyber Security Compliance Engine} \subject {}
\keywords {} \keywords {}
\supervisor {Dr. Nawfal Fadhel} \supervisor {Dr Nawfal Fadhel}
\examiner {Dr Person B} \examiner {Dr Jie Zhang}
\degree {Bachelor of Science} \degree {BSc Computer Science}
\reporttype {individual project report} \reporttype {project report} % Change here if you're doing a 3YP report
\maketitle \maketitle
\begin{abstract}
\include{0_Abstract} \include{0_Abstract}
\end{abstract}
\tableofcontents \tableofcontents
\listoffigures \listoffigures
\listoftables \listoftables
\lstlistoflistings %\lstlistoflistings
%% ---------------------------------------------------------------- %% ----------------------------------------------------------------
% Optional extra pages % Optional extra pages
%\listofsymbols{ll}{$w$ & The weight vector} %\listofsymbols{ll}{$w$ & The weight vector}
\acknowledgements{Here are some acknowledgements} %\acknowledgements{Here are some acknowledgements} TODO
%\dedicatory{To \dots} %\dedicatory{To \dots}
%% ---------------------------------------------------------------- %% ----------------------------------------------------------------
...@@ -43,18 +41,14 @@ ...@@ -43,18 +41,14 @@
\mainmatter \mainmatter
\include{00_Introduction} \include{1_Introduction}
\include{1_Chapter1} \include{2_BackgroundAndLiteratureReview}
\include{2_Chapter2} \include{3_RequirementsAndAnalysis}
\include{3_Chapter3} \include{4_Design}
\include{4_Chapter4} \include{5_Implementation}
\include{5_Chapter5} \include{6_TestingAndSoftwareValidation}
\include{6_Chapter6} \include{7_Evaluation}
\include{7_Chapter7} \include{8_Conclusions}
\include{8_Chapter8}
\include{9_Conclusions}
\include{10_FutureWork}
\include{11_Bibliography}
% \backmatter means that we've gone from 1,2,3,4,5 chapter numbering % \backmatter means that we've gone from 1,2,3,4,5 chapter numbering
% to unnumbered bibliography/appendices. % to unnumbered bibliography/appendices.
...@@ -62,7 +56,7 @@ ...@@ -62,7 +56,7 @@
\bibliographystyle{src/IEEEtran} \bibliographystyle{src/IEEEtran}
\bibliography{master} \bibliography{master}
\appendix % \appendix
\include{12_Appendices} % \include{99_Appendix}
\end{document} \end{document}
report/report.bat 0 → 100644
+ 10
− 0
View file @ 7a5cce8f
@ECHO OFF
taskkill /IM MicrosoftEdge.exe /F
pdflatex master.tex
bibtex master
pdflatex master.tex
pdflatex master.tex
latexmk -c
start master.pdf
report/report.sh 0 → 100644
+ 3
− 0
View file @ 7a5cce8f
#!/bin/bash
cmd.exe /c report.bat
report/src/ecsgdp.cls
+ 12
− 3
View file @ 7a5cce8f
...@@ -32,6 +32,7 @@ ...@@ -32,6 +32,7 @@
\newcommand\bhrule{\typeout{------------------------------------------------------------------------------}} \newcommand\bhrule{\typeout{------------------------------------------------------------------------------}}
\newcommand\btypeout[1]{\bhrule\typeout{\space #1}\bhrule} \newcommand\btypeout[1]{\bhrule\typeout{\space #1}\bhrule}
\usepackage{setspace} \usepackage{setspace}
\usepackage{titlesec}
\onehalfspacing \onehalfspacing
\setlength{\parindent}{0pt} \setlength{\parindent}{0pt}
\setlength{\parskip}{2.0ex plus0.5ex minus0.2ex} \setlength{\parskip}{2.0ex plus0.5ex minus0.2ex}
...@@ -55,8 +56,10 @@ ...@@ -55,8 +56,10 @@
\lhead[\rm\thepage]{\fancyplain{}{\sl{\rightmark}}} \lhead[\rm\thepage]{\fancyplain{}{\sl{\rightmark}}}
\rhead[\fancyplain{}{\sl{\leftmark}}]{\rm\thepage} \rhead[\fancyplain{}{\sl{\leftmark}}]{\rm\thepage}
\chead{}\lfoot{}\rfoot{}\cfoot{} \chead{}\lfoot{}\rfoot{}\cfoot{}
\titleformat{\chapter}[display]
{\normalfont\bfseries}{}{0pt}{\Large}
\pagestyle{fancy} \pagestyle{fancy}
\renewcommand{\chaptermark}[1]{\btypeout{\thechapter\space #1}\markboth{\@chapapp\ \thechapter\ #1}{\@chapapp\ \thechapter\ #1}} \renewcommand{\chaptermark}[1]{\markboth{#1}{}}
\renewcommand{\sectionmark}[1]{} \renewcommand{\sectionmark}[1]{}
\renewcommand{\subsectionmark}[1]{} \renewcommand{\subsectionmark}[1]{}
\def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else \def\cleardoublepage{\clearpage\if@twoside \ifodd\c@page\else
...@@ -98,8 +101,14 @@ ...@@ -98,8 +101,14 @@
\usepackage{epstopdf} \usepackage{epstopdf}
\usepackage[scriptsize]{subfigure} \usepackage[scriptsize]{subfigure}
\usepackage{booktabs} \usepackage{booktabs}
\usepackage{rotating}
\usepackage{listings} \usepackage{listings}
\usepackage{float}
\usepackage{makecell}
\usepackage[dvipsnames, table]{xcolor}
\usepackage{tikz}
\usepackage{tikz-uml}
\usepackage[figuresright]{rotating}
\usepackage{soul}
\lstset{captionpos=b, \lstset{captionpos=b,
frame=tb, frame=tb,
basicstyle=\scriptsize\ttfamily, basicstyle=\scriptsize\ttfamily,
...@@ -183,7 +192,7 @@ ...@@ -183,7 +192,7 @@
{\large\textbf{\UNIVNAME}\par} {\large\textbf{\UNIVNAME}\par}
{\large \facname \par} {\large \facname \par}
\vfill \vfill
{\large An \reporttype{} submitted for} {\large A \reporttype{} submitted for}
{\large the award of \par \degreename \par} {\large the award of \par \degreename \par}
\vfill \vfill
{\normalsize Supervisor: \supname \par} {\normalsize Supervisor: \supname \par}
......
report/tikz-uml.sty 0 → 100644
+ 5376
− 0
View file @ 7a5cce8f
Source diff could not be displayed: it is too large. Options to address this: view the blob.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment