morning edit
This commit is contained in:
parent
5be73d9303
commit
4da27903f4
@ -190,7 +190,7 @@ with its own set of failure modes.
|
|||||||
|
|
||||||
|
|
||||||
\subsection{From functional group to newly derived component}
|
\subsection{From functional group to newly derived component}
|
||||||
|
\label{fg}
|
||||||
The process for taking a {\fg}, considering
|
The process for taking a {\fg}, considering
|
||||||
all the failure modes of all the components in the group,
|
all the failure modes of all the components in the group,
|
||||||
and analysing it is called `symptom abstraction'.
|
and analysing it is called `symptom abstraction'.
|
||||||
|
@ -60,11 +60,11 @@ if they have multiple causes.
|
|||||||
}
|
}
|
||||||
|
|
||||||
%{ \huge This might become a chapter in its own right after fmmdset }
|
%{ \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}
|
\section{From UML Model to Object Model}
|
||||||
|
|
||||||
@ -73,6 +73,8 @@ consider that all base~components have %only
|
|||||||
two failure modes that
|
two failure modes that
|
||||||
we will label $a$ and $b$.
|
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 \}$.
|
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}
|
\input{./shortfm}
|
||||||
|
|
||||||
|
|
||||||
|
36
shortfg.tex
Normal file
36
shortfg.tex
Normal file
@ -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}.
|
||||||
|
}
|
Loading…
Reference in New Issue
Block a user