robin/Robin_PHD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

saw a couple of typos

Browse Source
This commit is contained in:
Robin Clark 2010-10-26 18:12:01 +01:00
parent 27f11dc4f4
commit dd07b8b174
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
fmmd_concept/fmmd_concept.tex
View File

@ -342,7 +342,7 @@ to smaller and smaller functional modules \cite{maikowski}.
\end{itemize}
\section{}
\section{Design of a new static failure mode based methodology}
\paragraph{New methodology Must be bottom-up}
In order to ensure that all component failure modes have been covered
@ -363,7 +363,7 @@ in \cite{maikowski}. This top down technique de-composes by functionality.
Simpler and simpler functional blocks are discovered as we delve
further into the way the system works and is built.
\paragraph{Design Decision: Methodology Mus be Bottom-up}
\paragraph{Design Decision: Methodology must be bottom-up.}
In oder to ensure that all component failure modes are handled,
this methodology must statrt at the bottom, with base component failure modes.
In this way automated checking can be applied to all component failure modes
@ -390,13 +390,13 @@ This means that we have to tie base component failure modes
to SYSTEM level errors. This is the `possibility to miss failure mode effects
at SYSTEM level' critism of the FTA, FMEDA and FMECA methodologies.
\paragraph{Design Decision: Methodolgy must reduce and collate errors at each functional group stage}
\paragraph{Design Decision: Methodolgy must reduce and collate errors at each functional group stage.}
SYSTEMS typically have far fewer failure modes then the sum of its comonent failure modes.
Many SYSTEM level errors may be caused by a variety of component level errors.
At each fucntional group collection, there must be a process to collect
common symptoms and reduce the number of failure modes to handle.
\paragraph{How to build a SYSTEM failure behaviour model}
\paragraph{How to build a meaningful SYSTEM failure behaviour model.}
The next problem is how to we build a failure mode model
that converges to a finite set of SYSTEM level failure modes.
%
@ -410,7 +410,7 @@ component failure mode, become the target for reducing the number
of failure modes to handle as we traverse up the hierarchy.
\paragraph{Component failures and {\fg} failure symptoms}
\paragraph{Component failures and {\fg} failure symptoms.}
In other words we want to find out what the symptoms of the failures in the {\fg}s
are.
The number of symptoms of failure should be equal to or