P. 1
IEEE - Software Quality Assurance Plan Template

IEEE - Software Quality Assurance Plan Template


|Views: 14,055|Likes:
Published by Kapil Samadhiya
IEEE - Software Quality Assurance Plan Template:
This document is very useful for all Software Testing Professionals. You can get clear concept of Software Testing / Quality Assurance.


Kapil Samadhiya
IEEE - Software Quality Assurance Plan Template:
This document is very useful for all Software Testing Professionals. You can get clear concept of Software Testing / Quality Assurance.


Kapil Samadhiya

More info:

Published by: Kapil Samadhiya on Oct 21, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less






In-process audits of a sample of the design are held to verify consistency of the design,

(1) Code versus design documentation

(2) Interface specifications (hardware and software)

(3) Design implementations versus functional requirements

(4) Functional requirements versus test descriptions

There are three types of in-process audits, software audits, walkthroughs, and inspections.
Software audits are independent evaluations of software activities and software work products by
software quality assurance, in or order to verify conformance to software process and product
standards. Walkthroughs are informal design review meetings held principally by software
project managers to elicit comments and feedback on their design solutions. Inspections are
expertly facilitated evaluations of software products by domain experts, namely software

- 46 -

engineers, to evaluate their conformance to requirements and identify software defects for
mandatory correction.

The three types of in-process audits are each unique, while very complementary. SQA audits
verify conformance to software process and product standards. Software project manager
walkthroughs are open forums for evaluating software designs, and software engineering
inspections are expert forums for directly improving software quality.

• Software Audit: The objective of software auditing is to provide an objective compliance
confirmation of products and processes to certify adherence to standards, guidelines,
specifications, and procedures. Audits are performed in accordance with documented plans
and procedures. The audit plan establishes a procedure to conduct the audit and for follow-up
action on the audit findings. In performing the audit, audit personnel evaluate software
elements and the processes for producing them against objective audit criteria, such as
contracts, requirements, plans, specifications, or procedures, guidelines, and standards. The
results of the audit are documented and are submitted to the management of the audited
organization, to the entity initiating the audit, and to any external organizations identified in
the audit plan. The report includes a list of the items in noncompliance or other issues for
subsequent review and action. When stipulated by the audit plan, recommendations are
reported in addition to the audit results.

• Walkthrough: A walkthrough is an informal design review meeting in which the manager,
supervisor, or technical lead that’s directly responsible for creating or designing a product,
verbalizes the intended operational flow, functional flow, and/or rationale and justification for
selecting technologies, a technical architecture, a detailed design, or a specific solution to
satisfy the product’s requirements or specifications, with other managers, engineers, and
technical specialists (in order to defend the design concept, solicit a critique of the approach,
or solicit design alternatives). In short, walkthroughs are intended for managers to solicit
design alternatives (without any mandatory action on behalf of the manager or product

• Inspection: An inspection is a highly structured and facilitated meeting in which independent
technical experts analyze and examine each of the individual product characteristics one-by-
one, in order to identify defects, non-conformances to requirements and specifications, non-
conformances to standards, non-conformances to numerical tolerances, operational and
functional failures, and/or safety hazards, without the presence of managers, supervisors, or
technical leads, without any defense from the author or creator of the product, and without
any consideration of design alternatives, design critiques, or any subjective improvements to
the product’s design by the examiners (in order identify defects for later mandatory correction
and enable early validation of the product using internal technical experts before it is
delivered). In short, inspections are for technical experts to identify defects that must be
corrected (but, not suggest design alternatives or subjective improvements to the product).

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->