From 771f6bee4a8488256450e1c1c6a4f9bc8117e577 Mon Sep 17 00:00:00 2001 From: Robin Clark Date: Wed, 25 Sep 2013 19:35:13 +0100 Subject: [PATCH] more polishing --- submission_thesis/CH3_FMEA_criticism/copy.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/submission_thesis/CH3_FMEA_criticism/copy.tex b/submission_thesis/CH3_FMEA_criticism/copy.tex index da672dd..4cc8e83 100644 --- a/submission_thesis/CH3_FMEA_criticism/copy.tex +++ b/submission_thesis/CH3_FMEA_criticism/copy.tex @@ -354,7 +354,7 @@ Traditional FMEA does not cater for the software hardware interface and using a distributed system means the signal path will cross several hardware/software interfaces\footnote{The complications of introducing a communications protocol and the failure mode characteristics of the communications -physical~layer must also be considered in a distributed system.}. +physical~layer must also be considered for a distributed system.}. %of the communications physical layer.. % %, and this leads on to the additional complications @@ -371,7 +371,7 @@ with its multiple passes of the hardware/software interface, mean traditional FMEA, for these systems, is impossible to perform. % -The base component failure mode to system failure paradigm is +The base component failure mode to system failure paradigm is thus utterly anachronistic in the distributed real time system environment.