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 question is "Can Amazon AWS or Microsoft Azure be qualified so that I Life Science companies can run validated apps on it?"
Cloud releases updates and changes at such great velocities that leaves all validation specialists continuously wondering on how to qualify it. Traditional strategies including GAMP 5 was never designed to address continuous changes. These models were designed for a "waterfall" world and not an "agile" one. It is not possible to qualify an infrastructure where changes are released without release notes with such an outdated mindset and toolset.