From 8c485650adef53ab53416ffa2ad82a3de236ba02 Mon Sep 17 00:00:00 2001
From: Robin Clark <r.clark@energytechnologycontrol.com>
Date: Wed, 8 Dec 2010 16:52:15 +0000
Subject: [PATCH] morning edit

---
 .../component_failure_modes_definition.tex       |  2 +-
 fmmd_concept/fmmd_concept.tex                    | 16 ++++++++++------
 2 files changed, 11 insertions(+), 7 deletions(-)

diff --git a/component_failure_modes_definition/component_failure_modes_definition.tex b/component_failure_modes_definition/component_failure_modes_definition.tex
index e4433b8..0aed33b 100644
--- a/component_failure_modes_definition/component_failure_modes_definition.tex
+++ b/component_failure_modes_definition/component_failure_modes_definition.tex
@@ -54,7 +54,7 @@ build hierarchical bottom-up models of failure mode behaviour.
 %for a given type of part can be obtained from standard literature~\cite{mil1991}
 %\cite{mech}. %The failure modes for a given component $K$ form a set $F$.
 
-
+\label{defs}
 %%
 %% Paragraph component and its relationship to its failure modes
 %%
diff --git a/fmmd_concept/fmmd_concept.tex b/fmmd_concept/fmmd_concept.tex
index 840ccd8..09c7048 100644
--- a/fmmd_concept/fmmd_concept.tex
+++ b/fmmd_concept/fmmd_concept.tex
@@ -1190,16 +1190,14 @@ chosing {\fg}s and working bottom-up this hierarchical trait will occur as a nat
 The UML models thus far in this 
 \ifthenelse {\boolean{paper}}
 {
-paper
-}
-{
-chapter
-}
+%paper
 have been used to develop the data relationships required to perform FMMD analysis.
 This section re-organises and rationalises the UML model.
+We want to be able to use {\dcs} in functional groups.
+It therefore makes sense for {\dc} to inherit {\em component}.
 
+The re-factored UML diagram is shown in figure \ref{fig:refactored_uml}.
 
-GO THROUGH INHERITANCE RELATIONSHIPS ETC
 
 \begin{figure}[h]
  \centering
@@ -1209,6 +1207,12 @@ GO THROUGH INHERITANCE RELATIONSHIPS ETC
  \label{fig:refactored_uml}
 \end{figure}
 
+}
+{
+% chapter
+The terms used in FMMD and the UML data model are refined in the 
+chapter \ref{defs}.
+}
 
 \section{Conclusion}