NHS Wales Informatics Service Enhances Software Application Testing

Transcription

1 NHS Wales Informatics Service Enhances Software Application Testing Presenter: Date: Location: Paul Malcolm & Rachael Wettach March 7th, 2012 BCS SIGIST, London Agenda 1. NHS Wales Informatics Service (NWIS) 2. What NWIS is not! 3. Challenges 4. Desires 5. Solution The Test Framework 1. Test Framework lifecycle 2. Test Framework deliverables 3. Test Framework strategy 4. Test framework plans 5. Case / scripts 6. Traceability matrix 7. Clinical Risk Process 6. Benefits 7. Results 8. Simpl role 2 1

2 NWIS CLIENT: NHS Wales Informatics Service PROJECT DATE: What NWIS is not Research Annual software bugs survey list 2011, Business Computing World 4 2

3 Challenges Multiple projects with multiple delivery types Lack of a common standard evident across projects Project teams unsure of expectations Complex project structures involving in-house teams, HSW, BSC, NHS Trusts, third party vendors Had contractors for specific jobs, bringing in their own knowledge, who didn t work in the Wales way Confusion around stakeholders responsibilities Issues identified during and after release Lack of resources. 5 Desires Enhance existing quality assurance Apps that meet needs Application testing consistency Max patient safety Adaptable approach Rigorous testing 6 3

4 The NWIS Test Framework What is it? Principles? Not prescriptive Testing good practice Provides guidelines Risk based Provides consistency Aligned with Clinical Risk Management Process Techniques, Tools and Templates Testing should start early The cost of fixing issues rises as the project progresses 7 The Test Lifecycle Requirements/ Specification Test strategy Test plans Test Lifecycle Test Cases/Scripts Test results/reports Contingency Strategise Plan Design Execute Evaluate 8 4

5 Test deliverables TEST STRATEGY TEST PLANS TEST CASES & SCRIPTS TRACEABILITY MATRIX HOW WHAT THE DETAIL VERIFICATION Define and document the overall approach to testing for the project - how are we going to test? Define and document the plan for each phase of testing what are we going to test? Define and document the tests and steps to verify that the requirements are met by the deliverable Map each requirement to one or more test cases to ensure all the requirements have associated tests 9 Test strategy (the how) Strategies provide the overall approach - How are we going to test? The aim and scope of the testing The overall test approach The risks and mitigation activities The assumptions The test phases and test types required The test resources required The high level test schedule The test milestones Defect/issue management 10 5

6 Test strategy (the how) Strategies: High level Will be updated throughout the project Are the responsibility of the project Should be written as early as possible within the lifecycle of the project Should be aligned with Patient Safety Should be written with assistance from technical and clinical resources Ideally written by an experienced testing resource Must be signed off by the project board 11 Test plans (what) Plans provide the detailed scope of the testing What are we going to test? Per Phase SIT, OAT, UAT Aim and scope of the test phase Assumptions, Risks and Contingencies What type of testing will be undertaken What areas of the system will be tested Tasks and responsibilities of all parties The Entry and Exit Criteria Test Resource (Environment, Data) requirements The test schedule 12 6

7 Test plans (what) Test Plans: Provide a lower level of detail Should be written with assistance from an experienced testing or technical resource Should be signed off by the project team 13 Test cases / scripts (the detail) Cases and Scripts outline the tests required the detailed steps Test Cases are high-level Outline of the tests Indicate which areas of the application will be tested Indicate what test types will be performed Test Scripts are very detailed The steps to follow The expected results of each steps Any data required to verify the test 14 7

8 Traceability matrix (Verification) Traceability Matrix maps back to requirements Verifies each requirement is tested Enables each test case to be mapped backwards Provides stakeholders with confidence Identifies which test cases verify which requirements Identifies what phase the requirements will be tested 15 Clinical Risk Process Risk Log Workshop More Risk log Workshops Clinical Risk and Safety Assessment Plan Risk Assessment Log Clinical Risk Assessment Report Clinical Safety Case Reports Pre-release Stage Report Certification Test Strategy incl Risk Assessment Test Planning update Risk Assessment Test Case/Script Preparation with Traceability Test Summary Reports Validate Test Exit Criteria 16 8

9 Benefits NWIS Research Laboratories, Swansea University NHS Wales Informatics Service s office 17 Results Internal External REFINING PROCEDURES CONSISTENT APPROACH FRAMEWORK EXPECTATIONS GUIDANCE QUALITY ASSURANCE PROCEDURES REDUCES DEVELOPMENT TIME RIGHT FIRST TIME 18 9

10 Simpl s role IDENTIFY CREATE RESOURCE RECRUIT ROLL-OUT 19 The Team Paul Malcolm EMEA Regional Director Rachael Wettach Test manager 20 10

11 Get in Touch FINDUS! GOOGLEMAPS ADDRESS: Adam House, 7-10 Adam Street The Strand, London WC2N 6AA PHONE: WWW: p-uk.html 21 11