本文发表在 rolia.net 枫下论坛Software QA has two levels of meaning which depends on the company's definition.
QA can assure the software product quality from two level.
1, Focus on Test
At this level, QA's responsibilities are to test software, find defects, track defect and make sure all defects are resolved in all releases.
2, Process Improvement
In order to better assure the quality, at this level, QA is mainly responsible for defining process used by the project, making sure defined process are followed, improving process. There're a lot of techniques could be used for these purposes, e.g. analyze the test result to identify how to improve coding process, analyze the field test data to decide how to improve system test process and so on. There're also standards which are well accepted by industrial.
Nowadays, most common standards for QA in North America is CMM which is software process guideline defined by SEI at CMU. However, ISO9003 is still perferred by a lot of European companies. IEEE, ISO and US Military they also have standards and templates for detailed area for example design, project plan and so on.
Small to intermedia size companies, they normally combine these two roles together and give focus on testing. I found most QA positions are about test in Canada.
In big company, the software team's size could be very huge, e.g. 200+. One project could involve 1000+ software engineers from different locations and departement. Therefore, they will have dedicated QA focusing more on process instead of testing, like Motorla, Nokia.
Hope my information help. Enjoy更多精彩文章及讨论，请光临枫下论坛 rolia.net
QA can assure the software product quality from two level.
1, Focus on Test
At this level, QA's responsibilities are to test software, find defects, track defect and make sure all defects are resolved in all releases.
2, Process Improvement
In order to better assure the quality, at this level, QA is mainly responsible for defining process used by the project, making sure defined process are followed, improving process. There're a lot of techniques could be used for these purposes, e.g. analyze the test result to identify how to improve coding process, analyze the field test data to decide how to improve system test process and so on. There're also standards which are well accepted by industrial.
Nowadays, most common standards for QA in North America is CMM which is software process guideline defined by SEI at CMU. However, ISO9003 is still perferred by a lot of European companies. IEEE, ISO and US Military they also have standards and templates for detailed area for example design, project plan and so on.
Small to intermedia size companies, they normally combine these two roles together and give focus on testing. I found most QA positions are about test in Canada.
In big company, the software team's size could be very huge, e.g. 200+. One project could involve 1000+ software engineers from different locations and departement. Therefore, they will have dedicated QA focusing more on process instead of testing, like Motorla, Nokia.
Hope my information help. Enjoy更多精彩文章及讨论，请光临枫下论坛 rolia.net