5 million dollars. And
(when it realized that it was about to suffer major, indefensible litigation) the Big European
Corporation ???forgave the debt.???
W
126
Manage Software Testing
competent technical writer or a literate tester. Grab every document you can and write Testing??™s own
requirements specification. An example
Requirements Specification Table of Contents
is listed in section
8.2.2. And here??™s how you write it:
1. Take the software out of the box in whatever form it comes and document how you install it.
Then starting with the screen you see first, describe everything on it like the example shown in
Figure 8.1
(assume that you have found a part of some user guide and are working from that).
2. Remember that every single control on every screen has a value (
On/Off, 100 < x > 100
) and a
status (
Usable/Greyed out
). See the next section for a way of describing this.
3. In your requirements specification, rewrite the screen and description shown in Figure 8.1 to look
like Figure 8.2.
4. Use the notation shown in the next section if it helps or invent your own. If you include screenshots,
show the software version number, since interfaces change.
5. Where pressing some button causes some screen to appear (as it usually will), create a separate
subsection for that screen, and call it ???Dialog Window (
),??? ensuring that name> is what you read on the title bar of the screen.
Pages:
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300