How can new Software QA processes be introduced in an existing

Organization?

A lot depends on the size of the organization and the risks involved. For large organizations

with high-risk (in terms of lives or money) projects, serious management buy-in is required

and a formalized QA process is necessary.

Where the risk is lower, management and organizational buy-in and QA implementation may

be a slower, step-at-a-time process. QA processes should be balanced with productivity so

as to keep bureaucracy from getting out of hand.

For small groups or projects, a more ad-hoc process may be appropriate, depending on the

type of customers and projects. A lot will depend on team leads or managers, feedback to

developers, and ensuring adequate communications among customers, managers,

developers, and testers.

In all cases the most value for effort will be in requirements management processes, with a

goal of clear, complete, testable requirement specifications.

What is verification? validation?

Verification typically involves reviews and meetings to evaluate documents, plans, code,

requirements, and specifications. This can be done with checklists, issues lists,

walkthroughs, and inspection meetings.

Validation typically involves actual testing and takes place after verifications are completed.

Дата добавления: 2015-08-27