Who makes software validation? What are the steps of its? -
fill in x,y,z please.
- software validation has x,y,z steps.
- client have provide x,y,z developer before starting write software.
- when software finished, validation completes doing x,y,z (sign, approval, test pictures, logs etc.).
if buy general software invoice management tool or sap module can modify/change every customer, should make software validation?
anything supply customer, reponsible unless contract of supply them specifies otherwise. why software product eulas long. have @ of exclusions.
there's difference between validation, verification , customer acceptance testing.
you'll find customer sign off package being accepted after period of acceptance testing, doesn't mean they'll accept bugs within code. why perform validation , verification testing.
if you're using licenced sdk produce product , customer hit finacially due bugs in product you'll need prove isn't code sdk suppliers code if wish avoid litigation. why have insurance.
edit - added
remember lay claim can prove case. don't claim product windows 7 compliant or compatible unless can prove is.
you need meet customers quality standards if have commercially agreed provide, although you'll find every country stipulates software must not of malicious or harmful nature , fit purpose.
Comments
Post a Comment