The code fragments
vi. The system and unit test designs and tests
vii. Any test scripts
viii. Details of how to set up tests
d. A matrix relating features and tests to illustrate the degree of coverage so far accomplished
(see section 15.2 in Chapter 15 for an example).
e. Metrics defined and used.
f. Dependencies (of the feature and its implementation).
g. Details of bugs found against each feature.
h. References.
18. Write and agree a common glossary of terms.
The critical questions are:
??? Do you have persons on the bridgehead teams who are in control of the respective sides? How do
you know they are in control?
??? Is there an overall relationship contract in place?
??“ Does it include provisions for liquidated damages?
??“ Is it enforceable in the supplier??™s country?
??“ Has it been reviewed by the customer test function (if any)?
??“ Does it identify:
??? Who writes the requirements specification and the approach to be taken?
??? The deliverables?
??? The stage payments and the criteria for their payment?
??? What sanctions are available if the supplier fails to deliver to time and of acceptable quality?
??? Who writes the acceptance tests?
??? The process of acceptance?
??? How the supplier reports progress to the customer, how often, and against what?
??? What the supplier team reporting structure is?
??? How specification changes and contract extensions are to be accommodated?
??? Performance standards each party must maintain?
??? Termination triggers, consequences, and process?
??? The Quality Management System to be adhered to throughout the relationship and how
this QMS will evolve, and be certified?
??? Third-party or other COT software to be incorporated in the final product?
??? Who will be in charge of the acceptance testing of delivered systems?
??? Security issues?
??? Intellectual property rights?
??? Are any milestones likely to be cited in liquidated damages litigation?
??? Is the customer or the supplier responsible for writing the acceptance tests? If the supplier is
responsible, who is in charge of reviewing and accepting them?
??? What are the fall-back (backsourcing) positions at each stage of the contract, for the customer,
and the supplier organizations in the event that the whole process fails?
??? How will the customer monitor the supplier such that the customer gets early warning of problems?
Will there be a prototype available for demonstration? Will there be a set of proof-of-concept
fragments?
??? How will the supplier access updated copies of the customer??™s operating environment and be
notified of the changes?
??? Is there an agreed audit process and standard whereby the customer will audit the supplier?
??? What redress will the customer have if any third party or COT software fails?
??? (How) can the supplier fake the metrics?
??? Will the communication links become overloaded?
Outsourcing
195
10.
Pages:
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400