See section B.5 in Appendix B. If the specification is purely
textual consider modeling it using some requirements specification tool. You will be unhappily
surprised how many bugs the specification contains.
If you realize that the specifications are grossly inadequate and that nothing will be done in
time to improve them, have a senior member of your team write a better version. See [Gervasi]
and section 8.2.1 for examples. See [Kwan] for some interesting horror stories of what happens
if you don??™t.
2.
Identify the usability-testing requirements
(see section B.12 in Appendix B) in terms of:
a. The usability requirements in the requirements specification, with particular attention paid to
user-critical moments (
?????¦press this button at the wrong moment, Sunshine, and??¦???
)
b. The user population and some definition of their talents (
?????¦he can??™t walk and chew gum at
the same time??¦???
)
FIGURE 6.2
A PERT chart of the system definition phase
15-5-90 1-5-90
1-5-90 1-5-90
2000
De?¬?nition
2100
Requirements
analysis
2200 Investigation
of technical
uncertainty
2600 Detailed
project planning
2400 Technical
speci?¬?cation
preparation
2300 Task
analysis and HCl
de?¬?nition
2500 Detailed
system
modeling
End
31-5-90
1-8-90 30-8-90 2-7-90
86
Manage Software Testing
c. The possible environments or circumstances in which the users might be trying to use the
system (
?????¦if the prime minister would kindly remove her handbag from my keyboard??¦???
)
d.
Pages:
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235