3.3 Other system interfaces
6.4 Software packages
6.5 Communications interfaces
6.6 Database
6.7 Operating system
7 Data
7.1 Overview of system data
7.1.1 Data inputs
7.1.2 Data outputs
7.2 Global data model
7.2.1 Real-world entities
7.2.2 Relationships between entities
8 Support
8.1 Training
8.1.1 Delivery systems
8.1.2 Trainee profiles
8.1.3 Curricula
8.1.4 Training documentation
8.2 Documentation
8.2.1 Format, style presentation
8.2.2 System documentation
8.2.3 User documentation
8.2.4 Operator documentation
8.2.5 Support documentation
8.2.6 Interface documentation
8.2.7 Requirements traceability
9 Acceptance requirements
9.1 Introduction
9.2 Standards compliance
9.3 Unit test requirements
9.4 Integration test Requirements
9.5 System test requirements
9.6 Acceptance test requirements
9.6.1 Demonstration
9.6.2 Execution
9.6.3 Analysis
130
Manage Software Testing
8.3 Test Strategy Document
See section 1.8.2 in Chapter 1
for an explanation of why you want to write this. In essence you want to define:
??? The situation today
??? The top ten problems
??? The possible solutions
If this sounds difficult, then you already realize how much thinking is involved. If it sounds easy ??¦
8.3.1 Introduction
???
Purpose of this document.
This document is intended as a strategy document for the . . . project.
[
The strategy document identifies the current situation, the problem(s) posed, and one or more
solutions together with any criteria for choosing a particular solution and possible measures.
Pages:
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306