Contracting for Software

Custom programs are very expensive; risks are high. The quality of software depends on how well the buyer can define his needs. A checklist is presented for those considering to have their computer software prepared by a third party. Suggestions from the author include: attaching software expectations to the contract; defining information fields; establishing target dates for the programmer. The article also covers documentation, training, warranty, and who will actually own the software. Author suggests finding tested, canned yet flexible software packages with established, satisfied users.