QA FAQ:

1. What is 'Software Quality Assurance'?
2. What is 'Software Testing'?
3. What are some recent major computer system failures caused by software bugs?
4. Does every software project need testers?
5. Why does software have bugs?
6. How can new Software QA processes be introduced in an existing organization?
7. What is verification? validation?
8. What is a 'walkthrough'?
9. What's an 'inspection'?
10. What kinds of testing should be considered?
11. What are 5 common problems in the software development process?
12. What are 5 common solutions to software development problems?
13. What is software 'quality'?
14. What is 'good code'?
15. What is 'good design'?
16. What is SEI? CMM? CMMI? ISO? Will it help?
17. What is the 'software life cycle'?
18. What makes a good Software Test engineer?
19. What makes a good Software QA engineer?
20. What makes a good QA or Test manager?
21. What's the role of documentation in QA?
22. What's the big deal about 'requirements'?
23. What steps are needed to develop and run software tests?
24. What's a 'test plan'?
25. What's a 'test case'?
26. What should be done after a bug is found?
27. What is 'configuration management'?
28. What if the software is so buggy it can't really be tested at all?
29. How can it be known when to stop testing?
30. What if there isn't enough time for thorough testing?
31. What if the project isn't big enough to justify extensive testing?
32. How does a client/server environment affect testing?
33. How can World Wide Web sites be tested?
34. How is testing affected by object-oriented designs?
35. What is Extreme Programming and what's it got to do with testing?