1. Software QC The Bare Necessities Mike Avison Bradford Royal Infirmary

2. Scope of this lecture Present very basic QC method –Broadly in line with NPL Software Integrity Level system –More detailed guidance available soon from IPEM report 86 “Quality Control of Gamma Camera Systems” Suggestions of “House Style”

3. Basic QC Method Uses any PC office suite (spreadsheet and word processor) Tracks software development Facilitates maintenance –Backup location –Listing Notes Authorities –Who can develop / use software

4. Structure Example: 3 programs in QC system Policy Inventory Project File Error Log Training Log Project File Error Log Training Log Project File Error Log Training Log Top Level Bottom Level

5. Top level

6. Policy 1. Justified Circumstances How do you decide you need a software application 2. Type of development What kinds of software do we write 3. Research and Development Proposal Finance / ethics 4. Staff Qualifications 5. Prescribed Methods and Tools Language(s) House Style 6. Contents of individual Project File 7.Inventory Location / who updates it 8. Error Log Location / what goes in / why 9. Participation in external software audit and in benchmarking The Policy for my section is just 2½ pages

7. Inventory

9. Bottom Level

10. Project File Project file for: 1.The author and person responsible for the software. 2.Outline plan 2.1.Clinical requirement 2.2.Basic required operation of the program 2.3.Platform 2.4.Expected operation of the program 2.5Specifications for tests 3.Software Location: 4.Test results. 5.Training records of staff expected to use the software 6.Archive location of the software, and instructions for reloading it. 7.Authorised maintenance staff 8.Method of operation 9.Applicability and limitations

11. Error Log Date of maintenance request Reason (bug / extension) Action Testing Release date New version number

12. Training Log (users) User trained - Date

13. So much for Control - How about Quality? House style –Programming guides naming of variables use of sub-programs use of loops –Pitfalls unique to NM File selection Orientation of views Left / Right error trapping Effect of noise on highly complex algorithms Record version on hardcopy Record operator initials on hardcopy

14. GOOD NEWS It really does not take long This simple system is likely to satisfy the BNMS quality auditor.