From 54cfe711dc73b86c4cb4a396e95951a4ef18e0fe Mon Sep 17 00:00:00 2001 From: Robin Clark Date: Mon, 21 Jun 2010 12:34:42 +0100 Subject: [PATCH] . --- symptom_ex_process/symptom_ex_process.tex | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/symptom_ex_process/symptom_ex_process.tex b/symptom_ex_process/symptom_ex_process.tex index 61341b0..500c824 100644 --- a/symptom_ex_process/symptom_ex_process.tex +++ b/symptom_ex_process/symptom_ex_process.tex @@ -11,13 +11,12 @@ its components. This chapter describes a process for taking a functional group of components, applying FMEA analysis and then determining how that functional group can fail. With this information, we can treat the functional group as a component in its own right. - This new component is a derived component. For a top down technique this would correspond to a low~level sub-system. %The technique uses a graphical notation, based on Euler\cite{eulerviz} and Constraint diagrams\cite{constraint} to model failure modes and failure mode common symptom collection. The technique is designed for making building blocks for a hierarchical fault model. Once the failure modes have been determined for a sub-system/derived~component, -This derived component can be combined with others to form functional groups +this derived component can be combined with others to form functional groups to model higher level sub-systems/derived~components. In this way a hierarchy to represent the fault behaviour