Validation Lifecycle Management
- “No Paper” Validation Infrastructure
- No Longer Limited to “Point in Time” Validation
- Manage Requirements, Specifications, Test Plans & Test Cases, Test Failures
- Manage Testing Schedules
- Manage Test Sequencing
The main objective of this post to answer the following questions. I know a picture is worth a thousand words and so I will do this with illustrations.
Can "Validation" and "DevOps" be used in the same sentence (like vCD - Validated Continuous Delivery)?
Is DevOps a viable model for validated apps in GxP Environments?
How can one ensure the "validation fidelity" in a DevOps environment?
What are the key steps involved in continuously validating a ServiceNow App?
One has to bear in mind that the underlying IaaS and PaaS infrastructure is constantly changing. In fact, the Cloud App itself is continuously changing. In the new cloud world, it does not make any value-sense to pin to an "ancient" version. Thus this Continuous Validation Framework is designed to mitigate these risks and ensure that your ServiceNow app is maintained in a validated state.
I very frequently get asked whether Azure Platform-as-a Service (PaaS which includes Serverless Architectures) can be qualified as well? Surprisingly, this question is asked even by Azure users who agree that Azure IaaS can be qualified. In this blog post I will provide a prescriptive guide to intelligently qualify Azure PaaS and maintain it in a qualified state (QS).
The million dollar question is "Can Microsoft Azure be qualified?". In this blog post I will provide a prescriptive guide on not just "how to qualify", but also how to maintain the qualified state intelligently.
The million dollar question is "Can AWS be qualified?". In this blog post I will provide a prescriptive guide on not just "how to qualify", but also how to maintain the qualified state intelligently.