Identify review moments for each package of work and update the supplier quality plan (see
section 8.21).
7. Agree a contract for the work.
The critical questions are:
??? Who writes the system and acceptance tests: the system supplier, another supplier, or the customer?
??? How are non-functional requirements to be defined, managed, and tested?
??? How are reviews to be coordinated between supplier and customer?
??? How can the customer agree that the supplier??™s non-functional test-bed is comparable to the
customer??™s working environment? (It can??™t be exact: but at least you should be able to get a
populated database and the sets of transactions for several days to be fed in.)
??? How does the supplier get access to the information he needs? Does he have access to a person
with sufficient clout to get that information?
??? What are the quality gates (quality milestones)? Here are some suggestions:
??“ The requirements specifications are reviewed and signed-off by the customer.
??“ The draft design documents are received and reviewed internally by the customer, and signed-off.
??“ The code is unit-tested and the test results sent and signed-off by the customer.
??? The supplier??™s system test has been completed, the customer has assessed the results, and
determined if the remaining outstanding bugs represent sufficient grounds for accepting the
release.
10.2.4 Monitor the Supplier
10.2.4.1 Process
1.
Pages:
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402