SQA ensures high quality software by defining activities and functions throughout development. SQA makes sure factors contributing to software success, like meeting organizational needs, are managed. SQA involves following standards, reviews, testing, error analysis, change management, education, vendor management, security, and risk management. Statistical SQA aims to quantify quality by collecting defect data, categorizing it, and addressing frequent causes. Software reliability refers to the ability of software to function as required over time without failure.

1. Software Quality Assurance (SQA)

2. To be discussed
● Element of SQA
● Statistical SQA
● Software Reliability
● Vocabulary: Software, quality, Software quality,
assurance, Statistics, Pareto principle,
Capability Maturity Model (CMM) and ISO 9000 ser
ies
.

3. SQA Defined
The activities and functions designed and
implemented by stakeholders to ensure that a
high quality software is produced throughout the
software development process.

4. Why SQA
The key to software success is its ability to
meet an organization’s need and not its ability
to work.
SQA is there to ensure that factors which
contribute to software success are highly
managed and controlled to meet the prime
purpose of software development.

5. Elements of SQA
● Standards: SQA must ensure that software engineering
standards (IEEE, ISO 9000 series, CMMI models etc..)
imposed by stakeholders or S.E organizations are met and
conformed to.
● Review and audit: Reviews are done by SQA personnel
to ensure quality guidelines are followed in software
production
● Testing: SQA ensures that this quality control activity is
efficiently performed in a way that will enable the
software perform its primary function.
● Error Detection, collection and analysis: SQA collects
and analyses error data to better understand how some
errors come about and how best to eliminate.
● Change management: Ensuring efficient change
management practices to boost software quality and
minimise impacts of software failure

6. ● Education : SQA organization proposes and sponsors educational
programs for Software Engineers, their managers and other stakeholders.
● Vendor management: Out of the three software categories acquired from
external vendors, the SQA personnel must suggest quality practices to be
adhered to by vendor and also add quality mandates to contract terms.
● Security: SQA ensure that the appropriate technology is used to protect
the software data at all levels.
● Safety: Assessment of the effect is performed by SQA personnel and
necessary steps are taken to reduce risk.
● Risk management: SQA organization ensures that risk management
activities are properly Conducted and emergencies are also well prepared
for.
Elements of SQA
--- Gideon T. Rasmussen

7. Statistical quality assurance depicts an emerging trend for software
organizations to become more quantitative about quality.
STEPS:
● Information about software is collected and categorized
● An attempt is made to trace each defect to its underlying cause
● Using the pareto principle (80% of the defects can be traced to
20% of the causes)
● Rectify problems caused by the vital few
Statistical SQA

8. Date: 2012
•Study: 5,400 large scale IT projects ($15M)
•Findings: 17% IT projects go so bad that it threatens the very existence of the company
•Average: 45% over budget, 7% over time while delivering 56% less value than predicted
Source: McKinsey & Company in conjunction with the University of Oxford
Date: Dec 2010
•Survey shows an incredible 70% of organizations have suffered at least one project failure in
• the prior 12 months
•50% of respondents also indicated that their project failed to consistently achieve what they
set out to achieve
Source: KPMG (New Zealand)
Date: Oct 2008
Type of survey : Survey of 1,500 change management executives
Only 40% of projects met schedule, budget and quality goals
Best organizations are 10 times more successful than worst organizations
Biggest barriers to success listed as people factors: Changing mindsets and attitudes – 58%.
Corporate culture – 49%. Lack of senior management support – 32%.
Underestimation of complexity listed as a factor in 35% of projects
Statistical Software Surveys

9. ● According to IEEE standard, Software reliability is
defined as the ability of a system or component to
perform its required functions under stated conditions
for a specified Period of time.
● Software reliability is therefore a measure of the
probability of a software failure occurring.
Software Reliability

10. Aggarwal, K., & Singh, Y. (2007). Software
Engineering (3rd ed.). New Age international
Publishers.
References
Thank