The software verification checklist will help in capturing the information related to.
- The level of skills, competency and qualification in performing the assigned responsibilities by the author.
- Sufficient authority (e.g. Read access to prerequisite materials and write access to the current document) has been given to author.
- The verification specification specify the methods to be used for the verification, and include:
o Review or analysis checklists, or
o Simulation scenarios, or
o Test cases, test data and test objects.
- For testing, the specification of each test case include the following:
o A unique identification;
o The reference to the version of the associated work product to be verified;
o the preconditions and configurations;
o the environmental conditions, if appropriate;
o The input data, their time sequence and their values;
o The expected behavior which includes output data, acceptable ranges of output values, time behavior and tolerance behavior; and
o The criteria to determine the test case as passed or failed.
- For testing, the test cases been grouped according to the test methods to be applied, considering the following aspects:
o The required test equipment or test environment;
o The logical and temporal dependencies; and
o The resources.
- For testing, the test cases been reviewed by a different person other than the author(s) of the work product to be verified.
- The software unit design and the implemented software unit been verified to provide evidence for: “compliance of the source code with its design specification”.
- The software unit design and the implemented software unit been verified to provide evidence for: “compliance with the specification of the hardware-software interface”.
The further supporting documents are available and in useful state (e.g. Approved, or sufficient stable draft)?
- The software unit design and the implemented software unit been verified to provide evidence for: “confidence in the absence of unintended functionality and properties”.