From 5dceec9b414a100e5a84f2e07f80ac2eabfba6ad Mon Sep 17 00:00:00 2001 From: "Robin P. Clark" Date: Tue, 31 Jul 2012 09:12:59 +0100 Subject: [PATCH] better into to abstract --- papers/fmea_software_hardware/software_fmea.tex | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/papers/fmea_software_hardware/software_fmea.tex b/papers/fmea_software_hardware/software_fmea.tex index 17b1084..477e656 100644 --- a/papers/fmea_software_hardware/software_fmea.tex +++ b/papers/fmea_software_hardware/software_fmea.tex @@ -140,9 +140,14 @@ failure mode of the component or sub-system}}} %up through the electronics and then through the controlling software. % %Presently Failure Mode Effects Analysis (FMEA), stops at the glass ceiling of the computer program. -% +This paper takes, from the literature, new and emerging methodologies +for software FMEA, applies them to a simple example system, and then +reaches conclusions about the effectiveness and failure mode +coverage of the combined FMEA techniques. + This paper presents a worked example of FMEA applied to an -integrated electronics/software system. +integrated electronics/software system, the industry standard +{\ft} signalling loop. % %FMEA methodologies trace from the 1940's and were designed to %model simple electro-mechanical systems.