In our previous post (Sequel: Software Quality Assurance for the PTV xServer) we touched on the subject of what quality can mean for us. So let us now look into specific ways of assuring quality.
First: testing. Just as functionality is not the only aspect of quality, testing is not the only aspect of quality assurance. Indeed, some would argue that testing is not part of quality assurance at all, but rather of quality control. Let’s recall that quality control comes after the fact while quality assurance is preventive. On the other hand, early quality control can in itself be considered a quality assurance method, so testing should indeed include both.
Of course, the PTV xServer product line is tested on multiple levels, but this is really only one part of our quality assurance efforts. In fact, there’s a lot more to be done than testing. Let’s elaborate on that.
First, the tools represent the most important aspect of quality assurance. Well, actually, no, they do not. This is, again, the naïve answer. Sorry.
Tools alone are not sufficient: you also need the right methods to know how to apply them.
Methods alone are not sufficient either: you also need a good process that triggers their application.
Equally, processes alone are not sufficient: you need skilled people who know how to apply the process, and of course, how to make optimal choices.
But let’s begin with the tools and work our way up from there.
Find out more about the tools as a major aspect of quality assurance in the post that will be published next week.