.

.gitignore

@@ -12,6 +12,8 @@
 *.lot
 *.toc
 *.*~
+*.bbl
+*.blg
 
 *paper.tex
 *.txt

introduction/introduction.tex

@@ -370,9 +370,9 @@ This introduces a level of self checking into the system.
 Admittedly this is the simplest failure mode scenario (that the 
 sensor is not wired correcly or has become disconnected).
 %
-This safety resisitor has a side effect, it also checks for some internal errorsi
+This safety resisitor has a side effect, it also checks for internal errors
 that could occur in this circuit.
-Should the input resistor $R22$ go OPEN this will be detected.
+Should the input resistor $R22$ go OPEN this would be detected.
 Should the gain resistors $R30$ or $R26$ go OPEN or SHORT a fault condition will be detected.
 %
 \paragraph{Not rigorous, but tested by time}
@@ -505,7 +505,7 @@ obvious faults, such as tautologies and contradictions, but also
 intermediate results can be extracted and these checked.
 
 Mathematical modeling of systems is not new, the Z language
-has been used to model systems\cite{ince}. However this is not widely
+has been used to model physical and software systems\cite{ince}. However this is not widely
 understood or studied even in engineering and scientific circles.
 Graphical techniques for representing the mathematics for
 specifying systems, developed at Brighton and Kent university

logic_diagram/logic_diagram.tex

@@ -653,7 +653,7 @@ the low temperature failure~mode $C$ can only occur if $A$ is true.
 The `O' ring could fail in a different way independent of the critical temperature and this is 
 represented, for the sake of this example, by contour $D$.
 
-In terms of propositional logic, the inhibit gate of FTAi\cite{nasafta}[pp 41-42], and the contour enclosure
+In terms of propositional logic, the inhibit gate of FTA\cite{nasafta}[pp 41-42], and the contour enclosure
 of PLD represent {\em implication}.
 \\
 % \tiny

sw_as_plds/sw_as_plds.tex

@@ -4,29 +4,6 @@
 %
 %
 %%\documentclass{entcs} \usepackage{formatmacro}  \usepackage{epsfig} \usepackage{pspicture} \usepackage{pstricks} \usepackage{subfigure} \usepackage{tikz}
-%\documentclass{entcs} \usepackage{formatmacro}  \usepackage{epsfig} \usepackage{pstricks} \usepackage{subfigure} \usepackage{tikz}
-%
-%\newcommand{\Fam}{{\mathbb F}}
-%\newcommand{\Pow}{{\mathbb P}}
-%\newcommand{\Dis}{{\vee}}
-%\newcommand{\Con}{{\wedge}}
-%\newcommand{\FMEA}{{\bowtie}}
-%
-%\newcommand{\Nat}{{\mathbb N}}
-%\newcommand{\Real}{{\mathbb R}}
-%\newcommand{\Complex} {{\mathbb C}}
-%\newcommand{\Rational} {{\mathbb Q}}
-%
-%%\bibliographystyle{unsrt}
-%%\newtheorem{theorem}{Thoeorem}
-%
-%\def\lastname{Clark}
-%\begin{document}
-%\begin{frontmatter}
-%  \title{ Software Component Failure Analysis } \author{Robin Clark\thanksref{ALL}\thanksref{r.clark@energytechnologycontrol.com}}
-%  \address{ Energy Technology Control\\
-%    25 North Street, Lewes, BN7 2PE, Great Britain} 
-%
 
 \ifthenelse {\boolean{paper}}
 {
@@ -93,6 +70,20 @@ Also that it has a self test IR LED, and a mechanical shutter
 to prove the detector can determine dark IR conditions.
 
 
+\section{Theoretical Example: Youdon to PLD}
+
+discuss hardware or software transform of data types. Same process as far as data flow is concerned.
+The two visual formats complement each other.
+
+\begin{itemize}
+\item Context diagram
+\item Transform bubbles
+\item software structure
+\item Software structure mapped to PLD with $\mu$P failure modes
+\end{itemize}
+
+
+
 \clearpage
 \begin{verbatim}
   // example C code
@@ -143,24 +134,24 @@ to prove the detector can determine dark IR conditions.
 % \caption{}
 % \label{fig:ir_det_pld}
 % \end{figure} % OR
-
+%
-\begin{figure}[h]
+%\begin{figure}[h]
- \centering
+% \centering
- \includegraphics[width=400pt,bb=0 0 675 1023,keepaspectratio=true]{sw_as_plds/ir_det_pld.png}
+% \includegraphics[width=400pt,bb=0 0 675 1023,keepaspectratio=true]{sw_as_plds/ir_det_pld.png}
- % ir_det_pld.png: 675x1023 pixel, 72dpi, 23.81x36.09 cm, bb=0 0 675 1023
+% % ir_det_pld.png: 675x1023 pixel, 72dpi, 23.81x36.09 cm, bb=0 0 675 1023
- \caption{IR Detector C code as PLD}
+% \caption{IR Detector C code as PLD}
- \label{fig:ir_det_pld}
+% \label{fig:ir_det_pld}
-\end{figure}
+%\end{figure}
-
+%
-
+%
-Note that the function calls in the example code, will
+%Note that the function calls in the example code, will
-each create their own PLD diagram, which can be considered as being nested in
+%each create their own PLD diagram, which can be considered as being nested in
-the main diagram.
+%the main diagram.
-
+%
-{\huge DIAGRAM REQUIRED OF NESTED DIAGRAMS FOR FUNCTION CALLS}
+%{\huge DIAGRAM REQUIRED OF NESTED DIAGRAMS FOR FUNCTION CALLS}
-Note it should be possible to automatically  generate
+%Note it should be possible to automatically  generate
-diagrams from code.
+%diagrams from code.
-Analyse C code for instance and make these types of diagrams.
+%Analyse C code for instance and make these types of diagrams.
 %
 %\subsection{Afferent, processing and Efferent flow}
 %