Testing is done, the software is released.
What could go wrong?
Audits and auditors!
The reality that everyone in a regulated industry faces.
You can mitigate potential problems by preparing a Validation Pack that contains:
- User requirements
- Supporting documentation (internal and external – User Manuals, Maintenance Manuals, Administration Manuals, and so on)
- Vendor data (Functional Specifications, FAT, SAT, Validation Protocols)
- Design documentation; Executed protocols
- An archive copy of the software (including libraries, data, and so on)
- Protocol execution results
- The test report
- A known bug list with impact assessment
Then, when the auditor asks whether the software has been validated, present the Validation Pack (or at least take them to the relevant library).
You’ll make his or her day.
