From dc9bc0881d9ce10f1f7dba2a0c10503aec516f93 Mon Sep 17 00:00:00 2001 From: Robin Clark Date: Wed, 25 Sep 2013 19:53:38 +0100 Subject: [PATCH] polish polish --- 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 4cc8e83..49ced0b 100644 --- a/submission_thesis/CH3_FMEA_criticism/copy.tex +++ b/submission_thesis/CH3_FMEA_criticism/copy.tex @@ -22,7 +22,7 @@ and look for ways in which it could be performed better and more efficiently. A major problem is with the scope of examination---i.e. which/how~many components should be checked against a particular failure mode---to -apply for FMEA analysis. +apply FMEA analysis. % \fmmdglossSTATEEX Checking all possible combinations of {\fms} against all components quickly leads to a state explosion problem. %: @@ -118,7 +118,7 @@ typically sensors and actuators connected to an industrially hardened computer b With traditional FMEA it is difficult to deal with a `plug~and~play' paradigm. % -The design philosophy of FMEA is to trace {\bc} failure through to system failures. +The design philosophy of FMEA is to trace {\bc} failures through to system failures. This is incompatible with a modular approach where the architecture of a system may be different for implementation sites. %