The software quality
assurance plan
Every project must have a quality plan. The quality plan
will be presented as a section in the project plan. It is drawn up by the
project manager at the start of the project and should be agreed with the
project sponsor.
You would expect the quality plan to contain the following
elements:
Statement of the quality control organisation
Identification of
specific standards and methods that will be used
Definition of the quality control procedures; this is
aligned to the Work Breakdown Structure
Specification of quality milestones
Detail of unusual features
Change control and configuration management
Detail of acceptance procedures
Specification of quality assurance procedures
The software quality assurance plan (SQAP), like the
software configuration plan, is also part of the overall software project
development plan.
The SQAP documents which resources are needed, how they
should be used and which standards and procedures will be applied during the
project.
The SQAP then becomes the mandate for the quality assurance
group during project development. The issuance of this plan is the
responsibility of the project manager, though in large projects it will usually
be delegated to the quality assurance manager.
The SQAP may appear as a separate document or as a section
within the project development plan, and may include the configuration
management plan (if this has not been documented separately).
Table 5 contains a list of the main subjects covered in the
SQAP. When any of these subjects is covered elsewhere, such as in the software
configuration management plan (SCMP), it can be omitted from the SQAP and
replaced by a pointer to the document in which it is covered.
However, the SCMP and the SQAP are concerned with different
aspects of the controlled items. The SCMP is primarily concerned with the format
of controlled items while the SQAP is more involved with the contents of
controlled items.
The SQAP must cover subcontractors, vendors and suppliers,
irrespective of whether or not these external entities have their own quality
assurance organization.
In any project, the quality of external components is
ultimately the concern of the project manager and the SQA organization. When a
system fails, it usually makes little difference whether the failure is due to
an externally developed component or an in-house developed component.
The plans for supervising these external groups must be
adapted to the type of external components being provided (off the shelf or new
development) and the type of organization (do they have their own quality
assurance organization?).
0 Comments
Please do not enter any spam link in the comment box.