Software warranty and technical support

Software warranty and technical support

November 21, 2012

Customers who order software development work often face the challenge of supporting and maintaining the finished product.

Warranty obligations


According to current international practices, a manufacturer (or contractor) has the right to set a warranty period for his product (work or, service). This is a period, during which he is prepared to deal with the client's problems and complaints regarding the product's quality. A warranty entails an obligation to eliminate any defects in the operation of a product or its construction, which may arise due to a production fault. In other words, during the warranty period, the developer must fix all software defects within the agreed time period, provided that the following conditions are met:

01 Document with bug Documented evidence of a system failure or fault is given.
02 Development Proof that the failure occurred due to a development fault is given.
03 Book with check mark There has been a proper usage of the software in accordance with the manual.
04 Screwdriver and cross mark No unwarranted interference with the software package has taken place on the client's part.
05 document and question The subject of the client's complaint is covered in the requirements specification.

According to the law, warranties oblige the developer to eliminate only those defects which arise as a result of his own error(s). Analysis and additional work is required to correct faults and it may be some time before a given piece of software is returned to the client. If the failure is deemed to be the fault of the client, then the developer is not obliged to resolve any defects or provide a new version of the software.

Technical support

Technical support

It stands to reason that warranty support and maintenance is not suitable for continuously operating services since it takes too long and can cause user/client loss. Moreover, the warranty support model is not intended for software which requires a high level of reliability.

EDISON offers technical support not as a substitute for a warranty but as a means of fully satisfying the client's needs. Technical support differs from a warranty, in that the developer commits to eliminating all defects, including those caused by the client or those which go beyond the scope of the requirements specification. The developer is also obliged to resolve defects and problems in the shortest possible time. Technical support may also include configuring the software, setting up a hotline, monitoring its functionality, training staff to work with the product, etc.

To visually demonstrate this point, the specifics of warranty obligations and technical support have been presented in the table below.

Warranty Technical support
Cost of service A typical year-long warranty amounts to 15% of the development cost. This is paid additionally, according to the number of working hours spent.
Defect resolution Only covers defects which occur due to development error(s), the subject of which appears in the requirements specification. All defects are covered.
The speed of client claim processing Up to several weeks from the day the claim is received and analysis is conducted. Instant response. Correction will be conducted in the shortest time possible. Round-the-clock work is also possible.
Product customisation The returned product has the same properties outlined in the requirements specification. The product is reworked so that optimal performance can be achieved when completing specific tasks.
Consulting services According to the specification. Available upon request.
The possibility of modernising the product and expanding its functionalities Not provided. Can be conducted, but only after an additional agreement has been concluded. Provided.

EDISON offers several models of cooperation, and provides technical support (which is usually paid for by the hour). Individual terms can also be considered and should be discussed with the project manager.