See section 15.2 for an example.
???
Interfaces with other systems:
Identify all other systems with which this system must coexist or
share data, and the specifications.
???
Business processes supported:
Identify the major business processes, their criticality, and where
they are defined.
???
Approach:
For each major group of features, specify the overall approach to testing.
??? Test suspension/resumption criteria: list which tests should be repeated.
???
Test deliverables:
Reference the documents in the test document set, test input/output data, and
test tools.
???
Environmental needs:
List the hardware, software, supplies, test tools.
???
Responsibilities
for managing, designing, preparing, executing, witnessing, checking, and
resolving.
??? Staffing and training needs.
???
Schedule
with any additional tasks/milestones not defined in the project plan, their dates, and
resources.
??? Risks and contingencies.
134
Manage Software Testing
8.5.1 Test Plan Header
A test plan should have a header containing the following fields:
??? Project name and identifying number
??? Plan date
??? Plan manager??™s name and signature
??? Any other signatures required for approval
??? Table of contents
??? Release number
Summarize the software items and software features to be tested. The need for each item and history may
be included. In multi-level test plans, each lower-level plan should reference the next higher-level plan.
Pages:
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312