Peter Farrell-Vinay
"Manage Software Testing"
From a
strategy document
may write a plan to do something or a specification of a
product.
] The Glossary section (at the end of this document) contains all words or phrases having
a special meaning in this document.
???
Intended audience.
This document is intended for use by the Test and/or the development team
and other project stakeholders.
???
Background.
[
Describe the events which led up to writing this document.
]
???
Scope.
[
The issues central to the strategy and the limits of interest of the strategy document.
]
???
Related documents.
[
Cite any documents referred to by the strategy document or which might be of
ancillary interest.
]
???
Conventions.
[
Text in italics is meant for guidance only.
]
???
Assumptions.
[List the assumptions on which the strategy is based (Return On Investment,
Market Value Added, value to customers, value to ). As the document evolves,
hopefully this list will grow and become a major focus of concern as the basis of change to the
strategy.]
FIGURE 8.4
Requirements specification table of contents (continued)
5 Constraints
5.1 Software design constraints
5.1.1 Reliability
5.1.1.1 Accuracy
5.1.1.2 Resilience
5.1.1.3 Consistency
5.1.2 Reusability
5.1.3 Testability
5.1.3.1 Communicativeness
5.1.3.2 Self-descriptiveness
5.1.3.3 Structuredness
5.1.4 Portability
5.1.4.1 Device-independence
5.1.4.2 Self-containedness
5.
Pages:
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307