robin/Robin_PHD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added citations to support spider

Browse Source 
diagrams as logic and theorem proving tools
This commit is contained in:
Robin P. Clark 2013-08-12 14:48:13 +01:00
parent ed1aacb71a
commit 7281c3ba4c
3 changed files with 1486 additions and 1450 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2919
mybib.bib
View File

File diff suppressed because it is too large Load Diff

14
submission_thesis/CH1_introduction/copy.tex
View File

@ -101,10 +101,15 @@ I had recently completed an
MSc and my project was to create an Euler/Spider~Diagram~\cite{howse:spider} editor in Java. MSc and my project was to create an Euler/Spider~Diagram~\cite{howse:spider} editor in Java.
This editor allowed the user to draw Euler/Spider diagrams, and could then This editor allowed the user to draw Euler/Spider diagrams, and could then
represent these as abstract---i.e. mathematical---definitions. represent these as abstract---i.e. mathematical---definitions.
%
The primary motive for writing the Spider diagram editor was to provide an alternative The primary motive for writing the Spider diagram editor was to provide an alternative
to formal languages for software specification. to formal languages for software specification.
% %
Because of my daily work exposure to FMEA, I started thinking of ways to apply formal languages and spider diagrams to An added attraction for using spider diagrams was that they could be used in
proving logic~\cite{stapleton:atpieds} and theorems~\cite{theoremflower,Fish200553} in an intuitive way.
%
Because of my daily work exposure to FMEA,
I started thinking of ways to apply formal languages and spider diagrams to
failure mode analysis. failure mode analysis.
% %
% %
@ -127,9 +132,10 @@ Any of the components that could, in failing, create a dangerous state were alre
documented and approved using failure mode effects analysis (FMEA). documented and approved using failure mode effects analysis (FMEA).
% %
This new requirement This new requirement
effectively meant that all single and double component failures effectively meant that all single and double component failures were
%double combinations of component failures were now required to be analysed.
now required to be analysed. This, from a state explosion problem alone, %
This, from a state explosion problem alone,
meant that it was going to be virtually impossible to perform. meant that it was going to be virtually impossible to perform.
% %
To compound the problem, %state explosion problem To compound the problem, %state explosion problem

3
vmgbibliography.bib
View File

@ -44,8 +44,7 @@
%%%%%%%%%%%%%%%%%%%%%%% WEB SITES ONLY %%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%% WEB SITES ONLY %%%%%%%%%%%%%%%%%%%%
%site,
@MISC{dau:website,
author = {{F.~Dau}}, author = {{F.~Dau}},
howpublished = "{http://www.dr-dau.net/eg\_readings.shtml}", howpublished = "{http://www.dr-dau.net/eg\_readings.shtml}",
year = "2006" year = "2006"