SQA

Software quality assurance (SQA) is a method of

ensuring that all software engineering processes,
methods, activities and work items are monitored
and conform to established standards.
Software Quality Assurance (SQA) is simply a
way to assure quality in the software. It is the set
of activities which ensure processes, procedures as
well as standards are suitable for the project and
implemented correctly.
Software Quality Assurance is a process which
works parallel to development of software. It
focuses on improving the process of development
of software so that problems can be prevented
before they become a major issue. Software
Quality Assurance is a kind of Umbrella activity
that is applied throughout the software process.
Generally the quality of the software is verified by
the third party organization like
international standard organizations.
•software’s portability
•software’s usability
•software’s reusability
•software’s correctness
•software’s maintainability
•software’s error control

Software Quality Assurance has:

1.A quality management approach
2.Formal technical reviews
3.Multi testing strategy
4.Effective software engineering technology
5.Measurement and reporting mechanism
Major Software Quality Assurance Activities:

1.SQA Management Plan:

Make a plan for how you will carry out the sqa
through out the project. Think about which set of
software engineering activities are the best for
project. check level of sqa team skills.

2.Set The Check Points:

SQA team should set checkpoints. Evaluate the
performance of the project on the basis of
collected data on different check points.

3.Multi testing Strategy:

Do not depend on a single testing approach. When
you have a lot of testing approaches available use
them.
4. Change Impact:
The changes for making the correction of an error
sometimes re introduces more errors keep the
measure of impact of change on project. Reset the
new change to change check the compatibility of
this fix with whole project.

5. Manage Good Relations:

In the working environment managing good
relations with other teams involved in the project
development is mandatory. Bad relation of sqa
team with programmers team will impact directly
and badly on project. Don’t play politics.
Benefits of Software Quality Assurance
(SQA):

1.SQA produces high quality software.

2.High quality application saves time and cost.
3.SQA is beneficial for better reliability.
4.SQA is beneficial in the condition of no
maintenance for a long time.
5.High quality commercial software increase
market share of company.
6.Improving the process of creating software.
7.Improves the quality of the software.
8.It cuts maintenance costs. Get the release right
the first time, and your company can forget about
it and move on to the next big thing. Release a
product with chronic issues, and your business
bogs down in a costly, time-consuming, never-
ending cycle of repairs.
Disadvantage of SQA:

There are a number of disadvantages of quality

assurance. Some of them include adding more
resources, employing more workers to help
maintain quality and so much more.
Software Quality Assurance (SQA) plan:

A Software Quality Assurance Plan revolves around making

sure that the product or service teaches the market trouble
and bug-free. It should also meet the requirements defined in
the SRS (software requirement specification).

The purpose of an SQA plan is three-fold. It comprises the

following:

•Establishing the QA responsibilities of the team in question

•Listing areas of concern that need to be reviewed, audited
and looked at
•Identifies the SQA work products.

An SQA plan will work alongside the standard development,

prototyping, design, production, and release cycle for a
software product or service. For easy documentation and
referencing, an SQA plan will have different sections like
purpose, references, configuration and management,
problem reporting and corrective actions, tools, code
controls, testing methodology, and more.
SQA activities/Tasks:

These are, quite simply put, a set of activities common to normal SQA operations.
1. Creating the plan
It consists of the engineering activities to be carried out, and ensuring the right skill
mix in the team. It also lays out the specifics of the actions to be taken in different
situations as well as the tools and procedures specific to the plan.
2.Checkpoint lists
Evaluation of quality of activities at each project stage. This means that there are
regularly scheduled inspections and adherence to the schedule.
3.Executing formal technical reviews
FTRs are used to evaluate the design and quality of the product prototype. Quality
requirements and design quality for the prototype are discussed in meetings with
the technical staff.
4.Multi-testing strategy
Adopting multiple testing approaches to cover all bases and ensure the best
possible quality.
5.Process adherence
Designers, developers, and other technical staff must conform to established
processes and employ defined procedures. It comprises the following:
Product Evaluation – the product is evaluated against the specifications laid out in the project
management plan. Process Monitoring – verifies that the steps taken in software development are
correct and match the steps against the documentation.
6. Control changes
Manual and automated control tools are used for validating change requests, evaluating
the nature of change, controlling and if required, arresting the change effect. In effect, this
makes sure that the software being developed does not stray too far from the outlines.
7. Measuring Change Impact
If defects are found, the concerned department issues a fix. The QA team then determines
the change and the extent of the change brought by the fix. The change should be stable
and should be compatible with the whole project. There are software quality metrics that
allow managers and developers to observe these activities and monitor changes
throughout the SDLC of the product or service.
8. SQA Audits
The audit inspects the entire SDLC process to the established procedure laid out in the SQA
plan. Non-compliance and missed faults can be unearthed and fixed due to this.
9. Record and report keeping
Keeping SQA documentation and information with associated stakeholders. This includes
audit reports, test results, reviews, change request documentation, and other
documentation generated during the entire SDLC.
10. Relationship management
Managing and interfacing between the QA and the development team, thus keeping roles
in check and responsibilities ahead of the individual.
SQA objectives/goals and metrics:

SQA metrics are the indicators that measure the

progress and performance of your SQA objectives.
For example, a SQA metric could be the defect
density, which is the number of defects per unit of
code or functionality.
SQA Goals, Attributes, and Metrics:

Requirement quality :
The correctness, completeness, and consistency of the requirements model will have a
strong influence on the qualityof all work products that follow.
SQA must ensure that the software team has properly reviewed the requirements model to achieve a high level of
quality.

Design quality : Every element of the design model should be assessed y the software team to ensure that it
exhibits high quality and that the design itself conforms to requirements.

Code quality : Source code and related work products must conform to local coding standards and exhibit
characteristics that will facilitate maintainability.

Quality control effectiveness : A software team should apply limited resources in a way that has the highest
likelihood of achieving a high–quality result. SQA analyzes the allocation of resources for reviews and testing to
assess whether they are being allocated in the most effective manner.
 Software quality goals, attributes, and metrics
Goal Attribute Metric
Requirement Ambigully Number of ambiguous modifiers (e.., many, large,
quality human–friendly)
Completeness Number of TBA, TBD

Understandabi Number of sections/subsections

lity
Volatility Number of changes per requirement Time (by
activity) when change is requested
Traceability Number of requirements not traceable to
design/code
Model clarity Number of UML models
Number of descriptive pages per model
Number of UML errors
Design quality Architectural Existence of architectural model
integrity Number of components that trace to architectural
Component model
completeness Complexity of procedural design
Average number of pick to get to a typical function
or content
Layout appropriateness
Number of patterns used
Interface
complexity

Patterns

Cont….
Code quality Complexity Cyclomatic complexity
Maintainability Design factors (Chapter 8)
Understandability Percent internal comments
Variable naming conventions
Percent reused components
Reusability Readability index
Documentation
QC Resource Staff hour percentage per
effectiveness allocation activity
Completion rate Actual vs. budgeted
Review completion time
effectiveness See review metrics
Testing Number of errors found and
effectiveness criticality
Effort required to correct an
error
Origin of error
 Six Sigma in Software Engineering

Six Sigma is the process of producing high and

improved quality output. This can be done in two
phases – identification and elimination. The cause
of defects is identified and appropriate elimination
is done which reduces variation in whole
processes. A six sigma method is one in which
99.99966% of all the products to be produced have
the same features and are of free from defects.
Characteristics of Six Sigma:

The Characteristics of Six Sigma are as follows:

1. Statistical Quality Control:

Six Sigma is derived from the Greek Letter ? which denote
Standard Deviation in statistics. Standard Deviation is used for
measuring the quality of output.

2. Methodical Approach:
The Six Sigma is a systematic approach of application in DMAIC
and DMADV which can be used to improve the quality of
production. DMAIC means for Design-Measure- Analyze-Improve-
Control. While DMADV stands for Design-Measure-Analyze-
Design-Verify.

3. Fact and Data-Based Approach:

The statistical and methodical method shows the scientific basis
of the technique.
4. Project and Objective-Based Focus:
The Six Sigma process is implemented to focus on
the requirements and conditions.

5. Customer Focus:
The customer focus is fundamental to the Six
Sigma approach. The quality improvement and
control standards are based on specific customer
requirements.

6. Teamwork Approach to Quality

Management:
The Six Sigma process requires organizations to
get organized for improving quality.
 IEEE

What Is The Full Form Of IEEE?

The full form of IEEE is the Institute of Electrical

and Electronics Engineers.

IEEE is a technical professional society dedicated

to advancing tech and innovation. IEEE serves
scientists, engineers, and professionals involved in
all areas of science and technology. It mainly
focuses on Electronics & Communication
Engineering, Electrical Engineering, Information
Technology, and Computer Engineering.
Headquartered in New York in the USA, it is an
association with non-profit organization.
IEEE has sponsored programs to honor achievers
for over a century. IEEE praises dedicated
individuals, colleges, and leaders who make a
positive impact on their profession and tech as a
whole.
Purpose:

The activities described in this standard are

intended to enable the software project to use the
SQA processes to produce and collect evidence
that form the basis for giving a justified statement
of confidence that the software product conforms
to its established requirements. 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 or
ANSI (American National Standards Institute)
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.