Equally
developers need to be disturbed as little as possible. The criteria for seeking such help is:
??? The feature is under-specified with respect to the delivered system
??? The feature is specified in the business or functional requirements
??? The feature is included in the release
??? The feature can be demonstrated by the developer
??? A problem with the feature can be demonstrated by the tester
Test Documents
135
8.5.4 Interfaces with Other Systems
Identify all other systems with which this system must coexist or share data, and where the specifications
of the interfaces and data can be found. Show the order (if any) in which this integration should occur.
Identify backup facilities to be used in the event of failure of this integration.
8.5.5 Business Processes Supported
Identify the major business processes, their criticality, and where they are defined. Relate (or refer to a
document relating) each major business objective to the flows involved and the system feature to be
used. Identify all flows which will originate or end in other, coexisting systems. Identify how the
changeover between the current and the future system will be handled.
8.5.6 Features to Be Tested
Identify the software features and combinations of software features to be tested and the corresponding
test design specifications.
8.5.7 Features Not to Be Tested
Identify any features and major combinations of features which will not be tested and the reasons, if this
is not self-evident from the previous section.
Pages:
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314