Professional Documents
Culture Documents
Transaction
Usage
Implementation
Perspective
TRANSACTION
P1 P2 P3 P4
RE-ORDER
ACCEPT
USER D1 REQUEST ORDER PROCESS
A WAIT ORDER FROM B
START TYPE 1 FROM THE CPU FORM
THE CPU
D2 YES
P5 P6 P7 P8
TRANSMIT NO
B PAGE TO C ACCEPT FIELD ANY MORE
WAIT TRANSMIT
TERMINAL INPUT FIELDS D
ANSWERS TO CPU
P9 P10 D3
P12
NO TRANSMIT
DIAGNOSTIC EXIT
TO TERMINAL YES SET UP REVIEW
ANALYSIS: Online Information Retrieval System
INPUT S A S B S C S S
TRANSACTION FLOW E
A B C D E
PROCESS QUEUES
PROCESSOR PROCESSOR PROCESSOR PROCESSOR PROCESSOR
DISPATCHER QUEUES
Application Processes
Births
Mergers
BIRTHS
Parent
Parent
DAUGHTER
DAUGHTER
ALTERNATE 2
MITOSIS
DECISION BIOSIS
Assumptions
Assume that the transaction flow model is imperfect but that the
correct model is untried. As with all models, we ignore the
complications that can invalidate the model and use what we
can apply with ease. After all, models for testing are intended to
give us insights into effective test case design- so it doesn’t
matter that they are imperfect as long as the testing results are
good.
COMPLICATED CASES
Biosis: Follow the parent flow from beginning to end. Treat each
daughter as a new flow, either to the end or to the point where
the daughter is absorbed.
Mitosis : This situation involves three or more transaction flows:
from the beginning of the parent’s flow to the mitosis point and
one additional flow for each daughter, from the mitosis point to
respective end.
Absorption : Follow the predator as the primary flow. The prey is
modeled from its beginning to the point at which it’s eaten.
Conjugation : Three or more separate flows- the opposite of
mitosis. From the birth of each parent, proceed to the
conjugation point and follow the resulting daughter from the
conjugation point to her end.
TRANSACTION FLOWS- ILL STRUCTURES
Use Patches- Put a patch into our system or a patch into the
system of external interface. In either case, someone has to put
an unrealistic patch.
Mistune - Test a system sized with grossly inadequate
resources(5% to 10%). This helps t o force most of the resource
related exception conditions.
Break the Rules - Transactions always require correctly
specified data structures to support them. Often a system
database generator is used to create such objects and to assure
that all required objects have been correctly specified. Bypass
the database generator and use patches to break all rules that
are required to go down the desired path.
Use Breakpoints - put breakpoints at the branch points where
hard-to-sensitize path segment begins and then patch the
sensitization control block to force that path.
INSTRUMENTATION