??? (Related to Requirements
completeness below)
100% Ensure that as soon as a
requirements baseline document
be established that all related
bugs are raised with a reference
to it.
Requirements completeness
??” there are no definitions
available of the product as a
whole.
Insufficient test coverage of the system
as a whole showing up in high levels
of Support and casually-found bugs
50% Extend the product
documentation to become
useable as requirements
specifications. Ensure that release
specification is integrated with
that documentation. Match all
product parts against one or
more documents
Testing ??” system. It is not
possible to system-test any
part of a new feature quickly:
bugs may only be evident after
some feature has been usable
for some time.
It is rare that > 10 bugs are found per
day.
25% Can only be resolved slowly by
ensuring that test coverage is
greater with each release.
Planning ??” beta testing. No
beta test has so far been
undertaken which has yielded
any useful feedback.
Bugs found in the field are quite
different to those found in-house.
40% Plan for greater involvement by
users, who are selected and
supported with more care than
hitherto.
Support interferes with
development schedules
Decreasing productivity as developers
have to context-switch continually.
60% Ensure that the only Support
requests accepted are those which
are replicated by Support, or
which are priority 1 category and
require a hotfix.
Pages:
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348