IEEE Standard for Software Quality Assurance Process

2. 730-2014 - IEEE Standard for
Software Quality Assurance
Processes

3. Introduction
This International Standard establishes definitions for the
various types of maintenance. This Standard provides
guidance that applies to planning, execution and control,
review and evaluation, and closure of the Maintenance
Process. This International Standard includes maintenance
for multiple software products with the same maintenance
resources. This standard is applicable to software as part of a
system as well as standalone software products. This
standard regards the field of software engineering to include
projects to develop new or enhanced products, maintenance
of existing products, and software integration projects.

4. What is SQA
A set of activities that define and assess the adequacy
of software processes to provide evidence that
establishes confidence that the software processes are
appropriate for and produce software products of
suitable quality for their intended purposes. A key
attribute of SQA is the objectivity of the SQA function
with respect to the project. The SQA function may also
be organizationally independent of the project; that is,
free from technical, managerial, and financial
pressures from the project.

5. Purpose
The purpose of this standard is to provide uniform,
minimum acceptable requirements for SQA processes
in support of a software project. In considering
adoption of this standard, regulatory bodies should be
aware that specific application of this standard may
already be covered by one or more IEEE standards
documents relating to quality assurance, definitions,
or other matters. It is not the purpose of this
document to supersede, revise, or amend existing
standards directed to specific industries or
applications.

6. Management Responsibility
Management support of the SQA function is essential for
SQA processes to be effective. This support minimally
includes:
 Management is familiar with and understands the SQA
function’s purposes, concepts, practices, and needs.
 Management provides the SQA function with an
appropriate level of skilled resources (people, equipment,
knowledge, methods, facilities, and tools) in order to
accomplish their project responsibilities.
 Management receives and acts upon information provided
by the SQA function throughout the course of a project.

7. ISO/IEC 14764 - Software
Engineering - Software Life Cycle
Processes - Maintenance

8. Introduction
This standard describes an iterative process for
managing and executing software maintenance
activities. This standard uses a process model to
discuss and depict each phase of software
maintenance. This Standard provides guidance for the
maintenance of software. The basis for the
Maintenance Process and its activities comes from the
definitions of ISO/IEC 12207. It defines the activities
and tasks of software maintenance, and provides
maintenance planning requirements

9. Maintenance Process
Maintenance is one
of the five primary
life cycle processes
that may be
performed during the
life cycle of software
(ISO/IEC 12207)

10. Maintenance Process
The Maintenance Process contains the activities and
tasks necessary to modify an existing software product
while preserving its integrity. These activities and
tasks are the responsibility of the maintainer. This
International Standard provides task-steps which are
examples of what to perform in order to implement
the maintenance activities and tasks. The maintainer
should ensure that the Maintenance Process exists and
is functional prior to development of any software
product.

11. Maintenance Process
The activities which comprise
the Maintenance Process are:
a) Process Implementation.
b) Problem and Modification
Analysis.
c) Modification Implementation
d) Maintenance
Review/Acceptance
e) Migration.
f) Retirement.

12. Type Of Maintenance
This standard include different type of maintenance which are mention
below
Adaptive Maintenance
The modification of a software product, performed after delivery, to keep
a software product usable in a changed or changing environment
Corrective Maintenance
The reactive modification of a software product performed after delivery
to correct discovered problems
Perfective Maintenance
The modification of a software product after delivery to detect and
correct latent faults in the software product before they are manifested
as failures
preventive maintenance
The modification of a software product after delivery to detect and
correct latent faults in the software product before they become
operational faults

13. Maintenance Strategy
The strategy prepares for the human and material resources
required to provide software maintenance for software
products. Maintainers should monitor the development
effort for maintainability. Results from maintainability
analyses should be used as aids in planning for
maintenance. This analysis should be provided as input
into development of the maintenance strategy. The
software maintenance strategy should consist of the
following elements:
 Maintenance concept
 Maintenance plan
 Resource analysis

14. Thank you