How to Approach Verification and Validation for Cloud Software
This is a podcast episode titled, How to Approach Verification and Validation for Cloud Software. The summary for this episode is: Why is verification and validation (V&V) confusing and challenging for many medical device professionals? In today’s new episode of the Global Medical Device Podcast, Jon Speer and his guest Brad Graves, Principal Project Manager at The RND Group explore key aspects of the verification and validation topic and provide helpful clarification to medical device professionals about V&V cloud-based software. Some of the highlights of the show include: - Verification demonstrates that you designed the product correctly. Validation confirms you designed the correct product. - V&V are distinct, but interrelated activities. For example, a product can pass verification, but fail validation. Also, verification can be a product’s validation. - V&V Protocols, Approaches, and Tools: Involve product definition, requirements, risks, application and operating systems, and test cases. - Does all software require validation? Medical device software must be verified and validated, but software that supports medical devices may only require verification or validation. - Advantages and Disadvantages: Cloud software is easy to install, highly portable and scalable, but allocation of servers and additional IT staff are not necessary. - How can rules and regulations for computer and software validation be managed? Cloud changes are out of your control, but guidance is available on how to make or isolate changes via structures, architectures, and containers.