...
This commit is contained in:
parent
a55aa9698d
commit
423b2894bb
@ -1222,8 +1222,7 @@ of its component's failure modes.
|
||||
We can thus create a new component derived from analysing the {\fg} where
|
||||
%
|
||||
the symptoms of failure of the {\fg} are the failure modes of this new `{\dc}'.
|
||||
|
||||
|
||||
%
|
||||
An outline of the FMMD process is itemised below:
|
||||
\begin{itemize}
|
||||
\item Collect components to form a {\fg},
|
||||
@ -1233,7 +1232,8 @@ An outline of the FMMD process is itemised below:
|
||||
\item Create and name a derived component for the {\fg},
|
||||
\item Assign the common failure modes from the {\fg} as the failure modes of the {\dc}.
|
||||
\end{itemize}
|
||||
|
||||
%
|
||||
The FMMD process is described in more detail in section~\ref{sec:symptomabs}.
|
||||
|
||||
%We can now call our functional~group a sub-system or a derived~component.
|
||||
%The goal here is to know how it will behave under fault conditions !
|
||||
|
@ -626,7 +626,7 @@ The next section describes the details of the symptom extraction process.
|
||||
|
||||
%\section{A Formal Algorithmic Description of `Symptom Abstraction'}
|
||||
\section{Algorithmic Description}
|
||||
|
||||
\label{sec:symptomabs}
|
||||
The algorithm for {\em symptom extraction} is described in
|
||||
this section
|
||||
%describes the symptom abstraction process
|
||||
|
Loading…
Reference in New Issue
Block a user