From 4da27903f445205ed251e796564bebe7d77f39f8 Mon Sep 17 00:00:00 2001
From: Robin Clark <r.clark@energytechnologycontrol.com>
Date: Mon, 6 Dec 2010 09:03:21 +0000
Subject: [PATCH] morning edit

---
 .../component_failure_modes_definition.tex    |  2 +-
 fmmd_data_model/fmmd_data_model.tex           |  8 +++--
 shortfg.tex                                   | 36 +++++++++++++++++++
 3 files changed, 42 insertions(+), 4 deletions(-)
 create mode 100644 shortfg.tex

diff --git a/component_failure_modes_definition/component_failure_modes_definition.tex b/component_failure_modes_definition/component_failure_modes_definition.tex
index 7a4f250..58022dd 100644
--- a/component_failure_modes_definition/component_failure_modes_definition.tex
+++ b/component_failure_modes_definition/component_failure_modes_definition.tex
@@ -190,7 +190,7 @@ with its own set of failure modes.
 
 
 \subsection{From functional group to newly derived component}
-
+\label{fg}
 The process for taking a {\fg}, considering
 all the failure modes of all the components in the group,
 and analysing it is called `symptom abstraction'.
diff --git a/fmmd_data_model/fmmd_data_model.tex b/fmmd_data_model/fmmd_data_model.tex
index 66e0ebc..07509c0 100644
--- a/fmmd_data_model/fmmd_data_model.tex
+++ b/fmmd_data_model/fmmd_data_model.tex
@@ -60,11 +60,11 @@ if they have multiple causes.
 }
 
 %{ \huge This might become a chapter in its own right after fmmdset }
-\[ \xrightarrow{\hspace*{3cm}} \]
+%\[ \xrightarrow{\hspace*{3cm}} \]
 
-\[ \xrightarrow{\hspace*{8cm}} \]
+%\[ \xrightarrow{\hspace*{8cm}} \]
 
-\[ \xrightarrow{\hspace*{10cm}} \]
+%\[ \xrightarrow{\hspace*{10cm}} \]
 
 \section{From UML Model to Object Model}
 
@@ -73,6 +73,8 @@ consider that all base~components have %only
 two failure modes that
 we will label $a$ and $b$.
 We can start with some base components, of types C and K  say, $\{ C_1, C_2, C_3, K_4, C_5, C_6, K_7 \}$.
+
+\input{./shortfg}
 \input{./shortfm}
 
 
diff --git a/shortfg.tex b/shortfg.tex
new file mode 100644
index 0000000..906af52
--- /dev/null
+++ b/shortfg.tex
@@ -0,0 +1,36 @@
+\ifthenelse {\boolean{paper}}
+{
+\paragraph{Functional Groups.}
+At low levels of design, components
+are brought together to interact and perform
+given functions. We can call these collections
+of components `functional groups'.
+%
+For instance we may have a handful of components
+brought together to perform a simple function
+like amplifying a signal or a power supply.
+%
+The components in a {\fg} can be considered
+to be `functionally~adjacent' to each other, in that
+they interact with each other to perform
+as a higher level component.
+}
+{
+\paragraph{Functional Groups.}
+At low levels of design, components
+are brought together to interact and perform
+given functions. We can call these collections
+of components `functional groups'.
+%
+For instance we may have a handful of components
+brought together to perform a simple function
+like amplifying a signal or a power supply.
+%
+The components in a {\fg} can be considered
+to be `functionally~adjacent' to each other, in that
+they interact with each other to perform
+as a higher level component.
+%
+Functional groups and their relationship to
+other FMMD datatypes are described in Section \ref{fg}.
+}