inputs to software expanded on
This commit is contained in:
parent
086361edff
commit
be416e8827
@ -106,11 +106,11 @@ In this analogy the connections are the code, and the functions and variables ar
|
|||||||
If we consider the
|
If we consider the
|
||||||
calls and variables/inputs to be components of a function,
|
calls and variables/inputs to be components of a function,
|
||||||
%
|
%
|
||||||
any erroneous behaviour from them has the same effect as component failure mode
|
any erroneous behaviour from them has the same effect as component failure modes
|
||||||
on an electronic {\fg}. %HHmmm HHHHMMMM XXXXXX gora den har nar dets finns into nagon some harker hela tiden
|
on an electronic {\fg}. %HHmmm HHHHMMMM XXXXXX gora den har nar dets finns into nagon some harker hela tiden
|
||||||
%
|
%
|
||||||
For a software function, a violation of a pre-condition is
|
For a software function, we consider a violation of a pre-condition to be
|
||||||
in effect a failure mode of `one of its components'.
|
equivalent to failure mode of `one of its components'.
|
||||||
|
|
||||||
|
|
||||||
\paragraph{Mapping contract `post-condition' violations to symptoms.}
|
\paragraph{Mapping contract `post-condition' violations to symptoms.}
|
||||||
|
Loading…
Reference in New Issue
Block a user