Added some refs for quality and diagnostics

mybib.bib

@@ -149,6 +149,35 @@ Database
 	keywords = "fault-tolerance"
 }
 
+@article{iso9001,
+	title = "ISO 9001 Quality",
+	journal = "British Standards Institute",
+	volume = " ",
+	number = "",
+	pages = " ",
+	year = "2012",
+	note = "Proceedings of the First International Workshop on Euler Diagrams (Euler 2004)",
+	issn = "1571-0661",
+	doi = "DOI: 10.1016/j.entcs.2005.02.018",
+	url = "http://www.bsigroup.com/en/assessment-and-certification-services/management-systems/standards-and-schemes/iso-9001/",
+	author = "BSI",
+	keywords = "quality",
+	keywords = "ISO9001"
+}
+
+@article{dbamafta,
+	title = "Diagnosis by Algebraic Modelling and Fault Tree Induction",
+	journal = "Sixth International Workshop on principles of diagnosis",
+	volume = " ",
+	number = "",
+	pages = " ",
+	year = "1995",
+	note = "Working papers of DX-95: Sixth International Workshop on principles of diagnosis",
+	author = "Maus, Jakob and Neumann, Bernd",
+	keywords = "FTA",
+	keywords = "DIAGNOSTICS"
+}
+
 @article{syssafe2011,
 	title = "Developing a rigorous bottom-up modular static failure modelling methodology",
 	journal = "6th IET International Conference on System Safety, 2011",

submission_thesis/CH4_FMMD/copy.tex

@@ -1006,14 +1006,7 @@ from which we can trace top level failure modes to the base component failure mo
 that can cause them.
 That is, we can trace failure mode effects 
 from base component level to the top and vice versa.
-%
+
-Having a  failure mode graph/model where base component failure modes are traceable to top event events,
-provides  a forward search  failure mode model.
-%
-We can use this model to derive information
-to assist in creating related models such as FTA~\cite{nucfta,nasafta},
-traditional FMEA, FMECA~\cite{safeware}[p.344], FMEDA~\cite{scsh}
-and other failure mode analysis methodologies.
 
 
 
@@ -1496,31 +1489,41 @@ with the op-amp.
 This {\fg} is now analysed and a {\dc} created to 
 represent the failure mode behaviour of the {\em INVAMP}.
 %
-An analysis report is generated as part of the  {\fg} to {\dc}
+%
+We may now use the  {\em INVAMP} {\dc} in even higher level {\fgs}.
+%
+An analysis report is generated for each stage in the FMMD  % {\fg} to {\dc}
 process. %\footnote
-By having an analysis report report for each analysis stage, 
+%
-%i.e. {\fg} to {\dc},
+%
+\paragraph{Traceability and quality of FMMD analysis.}
+By having an analysis report report for each analysis stage, %i.e. {\fg} to {\dc},
 we add traceability to the reasoning applied to the FMEA process.
 %
 Consider that traditional FMEA has one large reasoning stage, that of component failure mode
-directly to system level failure. The reasoning given is typically one line
+directly to system level failure. The reasoning given is typically a one line comment
 on a spreadsheet entry~\cite{sccs}[p.38]. % (if we are lucky!).
 %
-FMMD typically has several reasoning stages from {\dc} {\fms} to system level failure modes.
+FMMD typically has several reasoning stages (i.e. from each {\dc} to {\fms}) up to to 
+final system level failure modes.
 %
-Thus, each possible cause for a system {\fm} will have a collection of analysis reports associated with it.
+Thus, each possible cause for a system {\fm} will have a collection of FMMD analysis reports associated with it.
 %
 These collections of analysis reports will provide a cause and effect
 story for each possible scenario that could cause the system level failure.
 %
-This increases the traceability---or documented paper trail---for the understanding the
+Traceability of design processes are considered necessary for
-failure event causes and potentially for use in diagnostics.
+safety critical product~\cite{en61508} and is an important concept 
+in quality systems~\cite{iso9001}.
 %
-We may now use the  {\em INVAMP} {\dc} in even higher level {\fgs}.
+Having analysis reports increases the traceability---or documented paper trail---aiding understanding 
+and maintainability for failure mode models.
+%
+Also a  detailed cause and effect model is useful creating diagnostic schemas~\cite{dbamafta}.
 
 
 
-\subsection{Keeping track of the derived components position in the hierarchy}
+\paragraph{Keeping track of the derived components position in the hierarchy}
 \label{sec:alpha}
 The UML meta model in figure \ref{fig:cfg}, shows the relationships
 between the entities used in FMMD.
@@ -2142,4 +2145,21 @@ The abstraction level concept is formally defined in section~\ref{sec:abstractio
 
 \section{Conclusion}
 
-Tie into wish list at end of chapter 3.
+Tie into wish list at end of chapter 3. Solves state explosion, completeness, traceability, models for related such as FMECA
+
+
+\paragraph{State explosion problem of FMEA solved by FMMD}.
+
+\paragraph{Uses of the FMMD failure mode model.}
+%
+Having a  failure mode graph/model where base component failure modes are traceable to top event events,
+provides  a forward search derived failure mode model. 
+%
+A forward search means that we can ensure that
+all known component failure
+modes have been considered in the analysis.
+%
+We can use this model to derive information
+to assist in creating related models such as FTA~\cite{nucfta,nasafta},
+traditional FMEA, FMECA~\cite{safeware}[p.344], FMEDA~\cite{scsh}, diagnostics schemas~\cite{dbamafta}
+and other failure mode analysis methodologies.