This slide is about software quality assurance and give you a brief introduction to software quality assurance .

1. PRESENTATION
SOFTWARE QUALITY ASSURANCE,
RESEARCH IN SOFTWARE ASSURANCE
Given by: Group 6
IMAD UL HASSAN
FAHEEM AMEEN
AMEER HAMZA
ASIF IBRAHIM

3. SOFTWARE QUALITY ASSURANCE AND
RESEARCH IN QUALITY ASSURANCE

4. WHAT IS SOFTWARE QUALITY ?
IEEE definition:
1. The degree to which a system, component, or process meets
specified requirements.
2. The degree to which a system, component, or process meets
customer or user needs or expectations.

5. SOME FAMOUS SOFTWARE ERRORS
Therac-25
Patriot Missile System
NASA's Mars Polar Lander
ESA's Arianne 5 Launch System
2003 Blackout

6. SOFTWARE QUALITY ASSURANCE
 IEEE Definition of. "Software Quality Assurance" A planned
and systematic pattern of all actions necessary to provide
adequate confidence that an item or product conforms to
established technical requirements. A set of activities designed
to evaluate the process by which the products are developed or
manufactured. (Aug 14, 2003)
 Conformance to software requirements is the foundation from
which software quality is measured.
 Specified standards are used to define the development criteria
that are used to guide the manner in which software is
engineered.

7. ELEMENTS OF SQA
 Standards
 Reviews and Audits
 Testing
 Errors/ Defect collection and Analysis
 Changing Management
 Education
 Vender Management
 Risk Management
 Security Management
 Safely

8. SQA TASKS
Prepare an SQA plan
Participates in SQL
Review Software Engineering activities to verify compliance with the
defined Software process
Audits designated Software work products to verify compliance with
the defined Software process
Ensure that deviation in software work and work product are
documented and handled according to documented procedure

9. GOALS , ATTRIBUTES AND METRIC
Requirement Quality
Design Quality
Code Quality
Quality
Quality Control Effectiveness

11. STATISTICAL SQA
Statistical quality assurance reflects a growing trend throughout industry to
become more quantitative about quality. For software, statistical quality assurance
implies the following steps:
 Information about software errors and defects is collected and categorized.
 An attempt is made to trace each error and defect to its underlying cause (e.g.,
nonconformance to specifications, design error, violation of standards, poor
communication with the customer).
 Using the Pareto principle (80 percent of the defects can be traced to 20
percent of all possible causes), isolate the 20 percent (the vital few).
 Once the vital few causes have been identified, move to correct the problems
that have caused the errors and defects.

12. DIFFERENCE BETWEEN SQA AND QC
SQA
Software quality
assurance (SQA) is a
process that ensures that
developed software meets
and complies with defined
or
standardized quality speci
fications.
Quality Control
 “Quality control (QC) is a
procedure or set of
procedures intended to
ensure that a manufactured
product or performed
service adheres to a defined
set of quality criteria or
meets the requirements of
the client or customer”.

13. SUMMARY
“Software quality assurance is the mapping of the managerial
precepts and design disciplines of quality assurance onto the
applicable managerial and technological space of software
engineering.” The ability to ensure quality is the measure of a
mature engineering discipline. When the mapping is
successfully accomplished, mature software engineering is the
result.

14. WHAT DOES ITS COST ?

15. THANKS