3 ms·

but the end product is basically the same whereas in computers the end product is quite different. There was no software as a service (at least not like there i

• willyt 6y ago
  The standard contracts don't specify what you will provide, they specify how much it will cost and when it will be provided. Exactly what will be provided is different each time and is generally covered by a written specification and a set of drawings, which are referred to in the contract and are part of the agreement, but they don't form part of the standard text. The building contract itself is an agreement for managing the process for things like changes to specification, the finish date and the process for paying for completed work, rejecting poor quality work or for defining poorly specified work after the contract is in progress. It sets out who has to pay the costs of changes depending on who has caused the changes and pre agrees some of the contractor's management costs. I imagine all these things are common to software projects? The basic project management procedures specified in the contract could probably be adapted to procure a software project. But the reason you couldn't just use a building contract for software project is because it also deals with various ancillary things like how the copyright in the design is licensed to the contractor, who is responsible for complying with Site Health and Safety legislation, various construction industry specific dispute resolution procedures required by law to be agreed in the contract, consumer rights law, housing grants and regeneration act, contracts (rights of third parties) act. GDPR, blah blah blah. The legislation is the stuff that is constantly changing.