7.4 in Appendix B. The output of the review should be a report
identifying:
??? What still needs to be done to improve baselines and tests
??? The degree of coverage expected to be achieved
??? The weaknesses so far discovered
??? The risks remaining
6.7 System-Testing Phase
System testing is the moment when the project??™s success or failure becomes evident. It is the first time
that the system is being used in anything like the way and the environment it was intended for, and is
often the moment at which the customer can observe the system in action.
During this phase the system is tested against its requirements. Since some parts of the system may
be expensive to test or the contract requires you to invite customer representatives to observe them, dryrun
the system tests beforehand. System tests tend to be long, drawn-out affairs for the following reasons:
??? Many features aren??™t ready.
??? Those features which
are
built have so many bugs in them that they can only be partly used.
??? Fixing the bugs exposes more bugs.
??? Many tests aren??™t ready.
??? The process of fixing bugs induces more of them.
??? The testers discover new ways of testing features not evident from the specifications.
??? Subtle and unwanted feature-feature interactions occur.
During this phase:
??? Execute the full system tests. If they derive from business process models, then at some point
execute them in the context defined by those process models.
Pages:
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243