From 01b2dd7c869ae1dcd8a7382be4fc5077e2725101 Mon Sep 17 00:00:00 2001 From: "Robin P. Clark" Date: Mon, 25 Jun 2012 09:55:44 +0100 Subject: [PATCH] Sending this one to supervisors now. --- papers/fmmd_software_hardware/software_fmmd.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/papers/fmmd_software_hardware/software_fmmd.tex b/papers/fmmd_software_hardware/software_fmmd.tex index 3aa5a92..722765c 100644 --- a/papers/fmmd_software_hardware/software_fmmd.tex +++ b/papers/fmmd_software_hardware/software_fmmd.tex @@ -230,7 +230,7 @@ and determining what system level failure modes could be caused. FMEA dates from the 1940s where simple electro-mechanical systems were the norm. Modern control systems nearly always have a significant software/firmware element, and not being able to model software with current FMEA methodologies -is a cause for criticism~\cite{safeware}. +is a cause for criticism~\cite{safeware}[Ch.12]. %Several variants of FMEA exist, % traditional FMEA being associated with the manufacturing industry, with the aims of prioritising @@ -270,7 +270,7 @@ software hardware/interface~\cite{embedsfmea}. Although this would give a better picture of the failure mode behaviour, it is by no means a rigorous approach to tracing errors that may occur in hardware -through the top (and therefore ultimately controlling) layer of software. +through to the top (and therefore ultimately controlling) layer of software. \subsection{Current FMEA techniques are not suitable for software}