Acti

vity
Net
work
for
Syst
em
Testi
ng
Click
to edit
text styles
Prepare
the Master
test plan

Second level

Specify
Third level conditions for user acceptance testing.
Fourth level
Fifth
level
Prepare
test data for program testing.
Prepare test data for transaction path testing.
Plan user training.
Compile/assemble programs.
Prepare job performance aids.
Prepare operational documents.

 Prepare test plan

Outputs expected from the system
Criteria for evaluating outputs
A volume of test data
Click to edit Master text styles
Procedure
for using test data
Second
level
level
Third
Personnel and training requirements
Fourth level
Fifth level

Specify conditions for user acceptance testing

involves analyst and the user to agree on the conditions
for test
conditions may be derived from the test plan
agreement on test schedule, test duration and the
people designated for the test
start and the termination date should also be specified.

 Prepare Test Data for Program Testing

prepared
and documented
Click
to edit Master
text stylesto ensure that all aspects of
the
program are properly tested.
Second
level
Third
level

data is filed for future reference.

Fourth level
Fifth level

prepare test data for transaction path testing

data required for testing every condition and
transactions to be introduced in the system.
path from origin to destination is tested for reliable
results
virtually comparable with the live data.

 Click
to edit
Master text styles
Plan user
testing
Second
level

to
Third level prepare the user for testing and converting the
Fourth level
system
Fifth level

The system group has time available to spend on training

while the programs are being written.
Initiating a user-training program gives the system group a
clearer image of the user's interest in the new system.
A trained user participates more effectively in system
testing.

having a checklist is useful

usual method, train the supervisor or the head and they
will train their team/staff.

 Click
to edit
textprograms
styles
compile
andMaster
assemble
Second
level

before
starting this, complete program description
Third level
Fourth level
should be available.
Fifth level

should include the purpose of the program, its use, the

programmers, time taken to run the program.

run order schedule and test schemes are finalized.

specifies the transactions to test and the order in which

they should be tested.
test scheme specifies how program software should be
debugged.

 Click
to edit
text styles
Prepare
Job Master
Performance
Aids
Second
level

materials
used should be specified and scheduled.
Third level
level
Fourth
Prepare
Operational Documents
Fifth level

all operational documents are finalized, including

copies of the operational formats required by the
candidate system.

Typ
es
of
syst
em
test
Click
systemtotesting
edit Master
begins by
text
testing
styles
program modules separately,
Second
followedlevel
by testing "bundled" modules as a unit.
Third level
Fourth
level testing
program
Fifth level
string testing
system testing
system documentation
user acceptance training

qual
ity
ass
ura
nce
Click to edit Master text styles
Second level

quality assurance defines the objectives of the

Fourth level
and reviews the overall activities so that
Fifthproject
level
errors are corrected early in the development
process.
Third level

 quality factor specification

correctness

Click reliability
to edit Master text styles
efficiency
Second
level
Third
level

usability
Fourth level
Fifthlevel
maintainability
testability
portability
accuracy
error tolerance
expandability
access control and audit
communicativeness

 Click
Master
text styles
Levelstoofedit
quality
assurance
Second
level

testing
Third level
Fourth level
Fifth level

to eliminate errors
fail test cycle

validation

checks the quality in simulated and live environment

alpha testing
beta testing

certification

certifies that the package is correct and conforms to

standard

Doc
um
ent
atio
n
Click
to edit
Master text styles
program
documentation
Second
level

describes
the inputs, outputs, and processing logic for
Third level
Fourth level
all program modules
Fifth level
starts in the systems analysis phase and continues
during systems implementation

System Documentation
System documentation describes the systems functions
and how they are implemented.
necessary reference material for the programmers and
analysts who must support and maintain the system.

 Click
to editDocumentation
Master text styles
Operations
Second
level

contains
all the information needed for processing and
Third level
Fourth level
distributing online and printed output.
Fifth level

User Documentation
consists of instructions and information to users who
will interact with the system and includes user
manuals, Help screens, and tutorials.