Quality

The awarding of a contract for a new system may (or may not) have a grey area in the conditions that refers to quality. That can mean different things to different people. You may offer the highest quality work imaginable, but if your client demands a bespoke system next week for almost zero cost (eg no finance for R&D, or testing, etc.) then there will probably be a disagreement regarding the quality of the system produced.

All parties subject to the terms of the contract must be aware of the quality expectations of the system and the requirements needed to match that expectation with suitable results.

All parties must be clear as to the quality of the finished system.

Such requirements may include:

• Time.

• R&D Budget to assess requirements and build analytical models.

• Sufficient time for development.

• Sufficient resource to employ the skilled people to create the new system.

• Sufficient time for testing and integration.

There is also the risk that indeterminate factors could come into play that compromise quality:

• A lead developer being killed in an accident.

• human error (back up failure).

• fire, flood, earthquake, hurricane etc.