0i

THE LITTLE FLOWER’S COLLEGE

Academic Year : 2021-2022

Topic
Ch3:Software Quality Assurance
 What is Quality?
• Quality defines to any measurable characteristics such as correctness,
maintainability, portability, testability, usability, reliability, efficiency,
integrity, reusability, and interoperability.
 Quality Assurance: Quality Assurance is the preventive set of activities that
provide greater confidence that the project will be completed successfully.
 Quality Assurance focuses on how the engineering and management
activity will be done?
• As anyone is interested in the quality of the final product, it should be
assured that we are building the right product.
• It can be assured only when we do inspection & review of intermediate
products, if there are any bugs, then it is debugged. This quality can be
enhanced.
 How to do Quality Assurance: Complete Process
• Quality Assurance methodology has a defined cycle called PDCA cycle or Deming
cycle. The phases of this cycle are:
1. Plan
2. Do
3. Check
4. Act
 These above steps are repeated to ensure that processes followed in the
organization are evaluated and improved on a periodic basis. Let’s look into the
above QA Process steps in detail –
1. Plan – Organization should plan and establish the process related objectives
and determine the processes that are required to deliver a high-Quality end
product.
2. Do – Development and testing of Processes and also “do” changes in the
processes
3. Check – Monitoring of processes, modify the processes, and check
whether it meets the predetermined objectives
4. Act – A Quality Assurance tester should implement actions that are
necessary to achieve improvements in the processes
• An organization must use Quality Assurance to ensure that the product is
designed and implemented with correct procedures. This helps reduce
problems and errors, in the final product.
 Need of SQA:
• Traceability of Errors:
• Cost efficient
• Flexible solutions
• Better customer service
• Innovation and creativity
• Software principles
• Multiple
• Software Quality Assurance Standards
• In general, SQA may demand conformance to one or more standards.
• Some of the most popular standards are discussed below:
• ISO 9000: This standard is based on seven quality management principles
which help the organizations to ensure that their products or services are
aligned with the customer needs’.
• 7 principles of ISO 9000 are depicted in the below image:
 Various SQA Techniques include:
• Auditing: Auditing involves inspection of the work products and its related information to
determine if the set of standard processes were followed or not.
• Reviewing: A meeting in which the software product is examined by both the internal
and external stakeholders to seek their comments and approval.
• Code Inspection: It is the most formal kind of review that does static testing to find bugs
and avoid defect growth in the later stages. It is done by a trained mediator/peer and is
based on rules, checklist, entry and exit criteria. The reviewer should not be the author
of the code.
• Design Inspection: Design inspection is done using a checklist that inspects the below
areas of software design:
• General requirements and design
• Functional and Interface specifications
• Conventions
• Requirement traceability
• Structures and interfaces
• Logic
• Performance
• Error handling and recovery
• Testability, extensibility
• Coupling and cohesion
• Simulation: Simulation is a tool that models the real-life situation in order
to virtually examine the behavior of the system under study.
• Functional Testing: It is a QA technique which verifies what the system
does without considering how it does. This type of black box
testing mainly focuses on testing the system specifications or features.
• Standardization: Standardization plays a crucial role in quality assurance.
It decreases the ambiguity and guesswork, thus ensuring quality.
• Static Analysis: It is a software analysis that is done by an automated tool
without actually executing the program. This technique is highly used for
quality assurance in medical, nuclear and aviation software. Software
metrics and reverse engineering are some popular forms of static analysis.
• Walkthroughs: Software walkthrough or code walkthrough is a kind of
peer review where the developer guides the members of the
development team to go through the product and raise queries, suggest
alternatives, make comments regarding possible errors, standard
violations or any other issues.
• Path Testing: It is a white box testing techniques where the complete
branch coverage is ensured by executing each independent path at least
once.
• Stress Testing: This type of testing is done to check how robust a system is
by testing it under heavy load i.e. beyond normal conditions.
• Six Sigma: Six Sigma is a quality assurance approach that aims at nearly
perfect products or services. It is widely applied in many fields including
software. The main objective of six sigma is process improvement so that
the produced software is 99.76 % defect free.
Thank you..!!