Software QC The Bare Necessities Mike Avison Bradford Royal Infirmary.

Slides:



Advertisements
Similar presentations
Software change management
Advertisements

INSE - Lecture 16  Documentation  Configuration Management  Program Support Environments  Choice of Programming Language.
Configuration Management
Building an EMS Database on a Company Intranet By: Nicholas Bollons Sally Goodman.
Step-by-Step Guide to Using the Toolkit and Where to Begin Health Information Technology Toolkit for Chiropractic Offices.
ISO in Histopathology Louise O’Callaghan MSc FAMLS
Audit of IT Systems SARQA / DKG Scandinavian Conference, October 2002, Copenhagen Sue Gregory.
Natural Resource Publications Management Publishing Reports in the Natural Resource Technical Report (NRTR), Natural Resource Report (NRR), and Natural.
IMS Systems Analysis and Design Communication and Documentation: Additional Notes on Written Reports.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Project Report1 Dave Inman Project report. Project Report2 Ways to write a report Top down: Write the structure of the report (maybe use the web templates.
CSE Information Systems 1 Communication and Documentation: Additional Notes on Written Reports.
OHT 14.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality infrastructure components The need for procedures and.
Principles of Procedural Programming
Documents and Records-Writing a Quality Manual-Module 16 1 Quality Manual Structure and Contents Quality Manual Structure and Contents - optional.
Application Software: Essentials for knowledge workers
LOGO AA Roundup March 30, Can we have a copy of your procedures? The first question the auditor’s ask:
5.2 Personnel Use competent staff Supervise as necessary
What is AuditWin? AuditWin is the most comprehensive premium audit software in the industry. With AuditWin you may receive pre-audit information, perform.
Instructions and forms
Database Auditing Models Dr. Gabriel. 2 Auditing Overview Audit examines: documentation that reflects (from business or individuals); actions, practices,
Spreadsheet Management. Sarbanes-Oxley Act (SOX, 2002) Requires “an effective system of internal control” for financial reporting in publicly- held companies.
Wizards, Templates, Styles & Macros Chapter 3. Contents This presentation covers the following: – Purpose, Characteristics, Advantages and Disadvantages.
This chapter is extracted from Sommerville’s slides. Text book chapter
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
CW-V1 SDD 0201 Principals of Software Design and Development Introduction to Programming Languages.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
IDigBio is funded by a grant from the National Science Foundation’s Advancing Digitization of Biodiversity Collections Program (Cooperative Agreement EF ).
Data management in the field Ari Haukijärvi 2nd EHES training seminar.
Registering a systematic review on PROSPERO. PROSPERO: International prospective register of systematic reviews Web based Free to register Free to search.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
California State University, Northridge Certification Process Team B Carlos Guzman John Kramer Stacey LaMotte University of Phoenix.
NYSFAAA Conference October 20, 2010 Adams Mark Hotel Buffalo, NY.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Elements of a Data Management Plan: Roles and Responsibilities Ruth Duerr National Snow and Ice Data Center Version 1.0 Review Date.
COURSE OUTLINE. COURSE OBJECTIVE Students will learn the following Basic concept of knowledge management Knowledge management technology Creativity Process.
U.S. Department of Agriculture eGovernment Program eGovernment Working Group Meeting February 11, 2004.
Copenhagen, 7 June 2006 Toolkit update and maintenance Anton Cupcea Finsiel Romania.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
ICCA Continuing Education Committee Report ICCA Board Meeting Kansas City, MO October 19, 2009.
PowerSchool State-specific custom field Migration to Extended Schema tables (What I have to do this summer) June 17, 2015.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 7 What Can Computers Do For Me?. How important is the material in this chapter to understanding how a computer works? 4.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
Best Practices for Inventory Control Patricia Hanson Biological Administrator I Florida Department of Agriculture and Consumer Services Food Microbiology.
S19: Documentation of fieldwork. Session Objectives ♂ In the last session, we have discussed the standards of documentation and the standard files to.
ITIL® Service Asset & Configuration Management Foundations Service Transition Thatcher Deane 02/17/2010.
WHO - PSM Basic Principles of GMP Documentation - Part 1 Workshop on GMP and Quality Assurance of HIV products Shanghai, China 28 Feb - 4 March 2005 Maija.
Chapter 16 Staff training and certification. Outline The objectives of training and certification The training and certification process Determine professional.
IPolicy Authoriser User Guide. General Information What is iPolicy? iPolicy is a web based document control software system designed for storage of policies.
Information Systems Development
Software Configuration Management
Software Configuration Management
The Organisation As A System An information management framework
The COSMO Coding Standards Some Highlights
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Information Systems Development
Regulatory Binder: Maintaining Essential Study Documentation
SharePoint Essentials Toolkit
Documentation for Developers
Computer Science The 6 Programming Steps.
Configuration management
The Survival Plan.
The COSMO Coding Standards Some Highlights
How to Cease your Service
HOW TO DOWNLOAD & INSTALL TomTom Home For Mac & Windows.
Presentation transcript:

Software QC The Bare Necessities Mike Avison Bradford Royal Infirmary

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”

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

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

Top level

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

Inventory

Bottom Level

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

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

Training Log (users) User trained - Date

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

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