Any change may thus become most expensive. See also [Kelly 2].
Certification testing will include but not be limited to performance testing. See Chapter 16
for more
details.
Microsoft (and other companies) has Gold certification schemes against which your software can be
assessed.
6.10 Documentation, Help, and Training Phase
During this phase the documentation and training materials are prepared and reviewed. Test staff are
invaluable as course guinea-pigs and document reviewers. The business process models can be tested
before cutover. See section 15.10.7 in Chapter 15 for more details.
6.11 Install, Coexist, Cutover, Support, and Evolution Phase
During this phase the software is installed and a series of tests are run to answer the big questions of
this phase:
1.
Does the software install properly? Does it interfere with anything else? How will we know if it doesn??™t?
2.
Does it coexist with the other systems? How will we know if it doesn??™t?
3.
How would we know that cutover has failed?
4.
Having cutover, if anything goes seriously wrong, can we revert to a previous state with minimal cost?
a. Identify the cost of a system failure.
b. Test the cutover, see if any part of the old database and any network-coexisting system is
affected.
c. Run the new system simulating loads at critical performance periods for a period indicating
a sufficient reliability. See section 16.8 in Chapter 16, the discussion in section 18.
Pages:
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246