| || |
I am working in a the QA in design and manufacturing company who is ISO 9001 ceritified.
Recently, there we had recruited Software engineers and started working on software projects.
The bosses wanted us to setup a new Software QA section to support this new business but everyone had a different interpretation of what Software QA is.
Does anyone has the experience and kind enough to share expertise.
a.) what is software QA
b.) what should it encompass (scope)
c.) is it like ISO 9000, meaning ensuring system compliance
d.) or is it technical as to verify the software codes.
Anyother things that we should look into ?
Hope some expert out there can help
Many thanks in advance
Re: Software QA
IMO as a QA Manager . . .
1) Software QA is all about ensuring that your delivered software exceeds the customers quality expectations. That's a customer focused definition, but I think it's important to keep site of why we're all doing this!
2) Software QA must encompass all activities within the SDLC; broadly speaking that's analysis, design, development, testing, implementation and maintenance functions. In practice, testing often becomes the focus of QA activity because it provides a visible quality check point. But remember that QA is broader than testing.
3) Ensuring compliance is part of software QA. Typically the software tester is concerned with ensuring that the software complies with specified requirements. There are also coding standards, quality metrics, etc that can be considered as compliancy issues.
4) Software QA can be highly technical when we are talking about analysing code for example. It depends on what aspect of software QA you are concerned with as to how technical the activity is though.
If I was in your situation, I would set up a system testing team whose function would be to validate the new software. In the process of doing this, the team would start to ask quality related questions and so the development team should react, organize and improve their deliverables. Hopefully you will see an improvement in the software. In the longer term you should review the entire SDLC and look carefully at all activities for improvements. Documentation, automation, requirements management, change control, project planning, etc. - these all all software development activities that should be considered from a QA perspective.
Just my own ideas - hope that's of some use.
Re: Software QA
Many thanks for sharing,
the confusion for us starts when different groups have different difination of what qa software should cover :
1.) some define the QA function as verification and validation of practices and execution of process with respect to procedures laid down
2.) while some states that QA function is to validate the software codes and structures.
any idea who is correct ?
Re: Software QA
Well I don't particularly like the first definition because there is no room for the 'improvement' of procedures "laid down". What it does have going for it is that it's potentially broad enough to encompasses all software development activities. The 2nd defintion is too narrow in focus and is more a definition of the test function.
Try this for a better definition of the Software QA and Testing functions:
SQA/Test Resource Centre
QA is concerned with the improvement of ALL development processes towards better software quality. Testing is concerned with verification and validation of the software itself and is part of the QA function.