Software Assessement

Information Required

1. A working copy of the software or spreadsheet with access to the underlying code.
2. A list of references to guidance, codes or standards that have been used in the production of the software.
3. A list of assumptions made in the software.

Development Process

1. Review of all equations with current SCI guidance and with relevant codes and standards.
2. Review of all assumptions with reference to SCI guidance and relevant codes and standards.
3. Review of software from a practical point of view, checking inputs and outputs for clarity, and considering any possible alterations that will improve the performance of the software.
4. Review of error handling routines and checks
5. Review of output.
6. SCI report detailing findings of stages 1 to 5 in order that alterations can be made to the software (if required) before a review of the final version.
7. Comparison of software with an independent set of calculations to verify the output.
8. SCI technical report detailing steps 1 to 7 and confirming the version of the software that has been SCI Assessed.

Administrative Issues

1. The SCI report will be stored electronically in the corporate archive. A hard copy will be retained in store by the SCI library.
2. A version number must be clearly displayed as part of the software, and a copy of this version of the software will be retained by SCI and referred to in the license agreement. Changes to the software will need to be registered and confirmed with SCI as a new version number.