Download CAUSE-EFFECT GRAPHING USER GUIDE

BenderRBT Cause-Effect Graphing Users Guide
T02—<Untestable> Due to non-OBServable effect(s) or
unable to sensitize
The state(s) of one or more cause nodes within the variation are
not observable, therefore the state of the effect node cannot be
validated (i.e., if there is a flaw in the logic associated with the
non-observable cause state(s), then the true/false state
represented by the faulty node cannot be relied upon).
Any intermediate effect nodes (synonymously referred to as
cause nodes for the current functional variation) whose
true/false state are verifiable during any test case scenario by
virtue of their observability, should be annotated with the OBS
designation in their node definition statements. Examples of
observable nodes are: a field displayed on a terminal, a record
data field whose contents can be printed or viewed after a test
has been run; in short, any processing event that can be
observed to have occurred, or conversely, to not have occurred.
Any node which is not actually observable, but which you
would like to force its observability to create a test case that
includes this variation, should be defined using its node
definition statement using the FOBS (forced) annotation.
T03—<Untestable> Need to create EXPLICIT/OBServable
intermediate node
A non-observable, BenderRBT-generated intermediate node
(i.e., the node name appears in the format **INT-xx*) has been
created due to a compound Relations statement (i.e., one
having two or more different relational operators, that has
necessitated the need for enclosing two or more cause nodes in
parentheses). Since the intermediate node is implied to exist, it
is implicitly non-observable. If it is necessary to ensure that
this functional variation is included in the test cases, then it is
necessary to explicitly create an observable intermediate node
and break the original compound relationship into two or
more simpler relations statements.
T04—<Untestable> Due to non-OBServable effect(s) or
unable to sensitize
BenderRBT was able to extrapolate the effect state of the
functional variation but was unable to fully sensitize a path
containing this variation in any of the test cases. This condition
will either occur due to observability issues or a combination of
node states being sensitized that does not match any of the
functional variations defined. Examine the test cases generated.
If it is necessary to ensure that this functional variation is
100