4 in Chapter
18, and the
Resilience Checklist
(section B.14.4) in Appendix B. Ensure that every transaction
type has been run. Simulate clock changes for new year, leap year, etc.
d. Identify whether it is necessary and cost-effective to have some way of capturing all transactions
made on the new system such that they can be applied to the old one.
e. Write a procedure to roll back to the old system and perform it.
f. Test if the old system can handle an update of all the transactions previously made on the new
system before roll-back.
5.
Will any systems coexisting on our company network affect or be affected by this release?
a. Identify a means of providing syntactically-correct but semantically irrelevant and harmless
outputs to any dependent systems.
b. Create a version of the system to use the harmless outputs to operational systems and run it.
c. Monitor all related systems.
6.
Do the Support staff have sufficient knowledge of the system to handhold users through their installation?
a. Identify all the new or changed features of the system.
b. Check the Support staff ??™s training program.
c. If necessary rotate all members of the Support staff through the installation testing and general
system testing, working as part of the test team.
d. Prepare a list of the most-often-occurring bugs from the buggiest features and make it available
to Support staff.
7.
Are we going to be overwhelmed with bugs?
This could happen if:
a.
Pages:
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247