Software QA/Testing
Glossary and Technical FAQs
|
|
Q: How do you introduce a new software QA process?
A: It depends on the size of the organization and the risks involved.
For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary.
For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand.
For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers.
Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable.
Q: What is the role of documentation in QA?
A: Documentation plays a critical role in QA. QA practices should be documented, so that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals should all be documented. Ideally, there should be a system
for easily finding and obtaining of documents and determining what document will have a particular piece of information. Use documentation change management, if possible.
[Continued on next page...]
Q: Do you like this site?
A:
Link to this page! From a forum, from a web site, or from a blog!
|
______________________________________________________
|