Merge branch 'master' of 192.168.0.3:/home/robin/git/thesis

This commit is contained in:
Robin Clark 2012-04-05 16:24:42 +01:00
commit ca35436eb7
2 changed files with 10 additions and 3 deletions

View File

@ -131,6 +131,13 @@ methodology",
YEAR = "2002" YEAR = "2002"
} }
@BOOK{misra,
AUTHOR = "Gavin McCall",
TITLE = "MISRA:C:2004 Guidelines for the use of the C language in critical systems ISBN 978-0-9524156-4-0 ",
PUBLISHER = "Hobbs",
YEAR = "2004"
}
@BOOK{alggraph, @BOOK{alggraph,
AUTHOR = "Alan Gibbons", AUTHOR = "Alan Gibbons",
TITLE = "Algorithmic Graph Theory ISBN:978-0521288811 ", TITLE = "Algorithmic Graph Theory ISBN:978-0521288811 ",
@ -271,7 +278,7 @@ methodology",
@BOOK{kandr, @BOOK{kandr,
AUTHOR = "Kernighan,Ritchie", AUTHOR = "Kernighan,Ritchie",
TITLE = "The C programming Language 2nd edition", TITLE = "The C programming Language 2nd edition ISBN 0-13-110362-8",
PUBLISHER = "Prentise Hall", PUBLISHER = "Prentise Hall",
YEAR = "1988" YEAR = "1988"
} }

View File

@ -171,7 +171,7 @@ and then definitions from contract programming are used
to define failure modes and failure symptoms in to define failure modes and failure symptoms in
software functions. software functions.
With these definitions we can apply FMEA With these definitions we can apply FMEA
to existing software\footnote{Existing software excluding recursive code, and unstructured non-functional languages}. to existing software\footnote{Existing software excluding recursive~\cite{misra}[16.2] code, and unstructured non-functional languages}.
} }
\section{FMEA Background} \section{FMEA Background}
@ -323,7 +323,7 @@ to software functions.
\subsection{Software, a natural hierarchy} \subsection{Software, a natural hierarchy}
Software written for safety critical systems is usually constrained to Software written for safety critical systems is usually constrained to
be modular~\cite{en61508}[3]~\cite{misra}[cc] and non recursive~\cite{misra}[aa]~\cite{iec61511}. be modular~\cite{en61508}[3]~\cite{misra}[cc] and non recursive~\cite{misra}[15.2]{iec61511}.
Because of this we can assume a direct call tree. Functions call functions Because of this we can assume a direct call tree. Functions call functions
from the top down and eventually call the lowest level library or IO from the top down and eventually call the lowest level library or IO
functions that interact with hardware/electronics. functions that interact with hardware/electronics.