The role of documentation in QA:
Generally, the larger the team/organization, the more
useful it will be to stress documentation, in order to
manage and communicate more efficiently. (Note that
documentation may be electronic, not necessarily in
printable form, and may be embedded in code comments, may
be embodied in well-written test cases, user stories, etc.)
QA practices may be documented to enhance their
repeatability. Specifications, designs, business rules,
configurations, code changes, test plans, test cases, bug
reports, user manuals, etc. may be documented in some form.
There would ideally be a system for easily finding and
obtaining information and determining what documentation
will have a particular piece of information. Change
management for documentation can be used where appropriate.
For agile software projects, it should be kept in mind that
one of the agile values is "Working software over
comprehensive documentation", which does not mean 'no'
documentation. Agile projects tend to stress the short term
view of project needs; documentation often becomes more
important in a project's long-term context.
Thanks & Regards
| || Guest |