Who makes software validation? What are the steps of its?

Question

Fill in the X,Y,Z please.

1. Software validation has X,Y,Z steps.
2. Client have to provide X,Y,Z to the developer before starting to write software.
3. When software finished, validation completes with doing X,Y,Z (sign, approval, test pictures, logs etc.).

If we buy a general software like invoice management tool or SAP module which can modify/change for every customer, who should make the software validation?

Answer 1

Anything that you supply to a customer, you are reponsible for unless your contract of supply with them specifies otherwise. This is why software product EULAs are so long. Have a look at all of the exclusions.

There's a difference between Validation, Verification and Customer Acceptance Testing.

You'll find that a Customer will sign off a package as being Accepted after a period of acceptance testing, but that doesn't mean that they'll accept any bugs within the code. That is why you perform validation and verification testing.

If you're using a licenced SDK to produce a product and your customer is hit finacially due to bugs in your product then you'll need to prove that it isn't your code but the SDK suppliers code if you wish to avoid litigation. This is also why you have insurance.

edit - added

Remember also to only lay claim to anything that you can prove to be the case. Don't claim that your product is Windows 7 compliant or compatible unless you can prove that it is.

You only need to meet a customers quality standards if that is what you have commercially agreed to provide, although you'll find that every country stipulates that software must not be of a malicious or harmful nature and fit for purpose.