3 ms·
But what makes 'software QA' fundamentally different than 'non-software QA' to give it the problems you foresee?
by Eisenstein 3y ago
But what makes 'software QA' fundamentally different than 'non-software QA' to give it the problems you foresee?
- vegetablepotpie 3y agoFundamentally different problems. Manufacturing process builds identical widgets using standard equipment. Widgets are inspected to confirm they are within spec. Frequentist statistics are used to determine when widgets are consistently out of spec. When this happens, equipment is inspected and repaired as a corrective action. This process is well defined and linear. Software produces bespoke, non-standard widgets to address domain specific needs. At the end of the day, software developers are defining a process for machines to follow. If you want to control quality in the software development , aside from having perfect domain knowledge for a particular project, the only way to do it do it is to define an arbitrary process for developers to follow and track adherence to it. This may have no impact, or be a hindrance. It will never add value because it will never be abstract enough to be appropriate for every domain.
- nikau 3y agoBecause every QA is something new for development barring regression testing. An equivalent software QA to building planes would be to verify a known process with existing tooling.