The common goal of any quality assurance effort is to confirm that a product or application meets certain standards of acceptance. Depending on what is being developed, this can include protocols and protection from getting hacked, broken, taken over, overloaded or left impotent by attacks either electronic or through other forms of subterfuge. While no perfect solution is available, coming to terms with acceptable risk levels is the ultimate goal.
By setting up threatening scenarios and “what if” situations, we seek to determine just what a worst-case situation would be and how to keep the damage under control. This not only serves to protect the consumer audience, it also provides a framework of expectations and aspirations up front for engineers and developers to shoot for
Setting up processes to help recognize and classify design issues, setting up measurable goals, and guaranteeing that secure testing takes place in a methodical, systematic and thorough manner facilitates the quantification of the QA role and its associated tasks. Additionally, it provides information that can be used to determine the need for enhanced services that would ease the burden of the QA effort and, in the process, build a healthier outcome.
When possible, the effectiveness of a quality assurance management program involves three interconnected components:
Please log in or sign up below to read the rest of the article.