UNIT 3

1. Write a short note on the defect Management process.

Ans:
● It's all about finding and fixing bugs, not just for the testing team but for
everyone involved in the software development.
● The process involves identifying, documenting, prioritizing, fixing, and
validating defects or issues found during the testing or development
phases.
● Defect Management Process:
1. Identification:
Defects are identified through various testing phases, user feedback,
or even during development.
2. Logging:
Once identified, defects are logged into a defect tracking system.
3. Prioritization:
Defects are prioritized based on their impact on the software.
4. Assignment:
Defects are assigned to the respective development or testing teams
responsible for fixing them.
5. Fixing:
Development teams work on fixing the defects by modifying the code
or addressing the issues identified.
6. Verification:
Testers verify that the reported defects are fixed and retest the
affected functionality to ensure the resolution did not introduce new
issues.
7. Closure:
Once verified, the defects are marked as closed, indicating that the
issue has been successfully addressed.
8. Reporting:
Defect management involves generating reports to analyze trends,
identify common issues, and improve the overall software
development process.

2. Explain the complexity matrices.

Ans:
● Complexity metrics are like measuring the difficulty of software, helping us
understand the complexity of the code and its potential impact on
maintainability and quality.
 ● A complexity measure is a cyclomatic complexity in which the complexity
of a module is the number of independent cycles in the flow graph of the
module.
● Supermarket Example:
1. For example, there is a supermarket next to the place I live.
2. They are good at dealing with complexity. If you buy fruit, there you
don’t need to weigh them yourself, the cashier will do it for you.
3. Compare this to other supermarkets where you need to find the
electronic weights that are working and pick the right number
4. In a traditional supermarket, the choice of products is identical, but
the whole experience feels more complex.
● Complexity metrics are valuable because they help developers and teams
identify areas of code that might be challenging to understand, test, or
maintain.
● Measuring complexity helps teams figure out which parts of the code might
be tricky.

3. What are the advantages of the ISO 9000 standard?

Ans:
● ISO 9000 is like a quality manual for businesses, providing a set of
standards to follow.
● Here are some advantages:
1. Improved Quality:
Following ISO 9000 standards ensures a focus on quality
management, leading to better products or services.
2. Enhanced Customer Satisfaction:
By meeting ISO 9000 standards, businesses can increase customer
confidence and satisfaction
3. International Recognition:
Achieving ISO 9000 certification provides international recognition
4. Reduced Costs:
Improved processes and quality management can lead to cost
savings by minimizing errors, rework, and waste.
5. Better Decision-Making:
With a focus on continuous improvement, ISO 9000 helps
organizations make informed decisions based on data and feedback.
6. Risk Management:
ISO 9000 encourages organizations to identify and manage risks
effectively, promoting a proactive approach to potential issues.
 4. Explain briefly and any 3 reliability matrices.
Ans:
● Reliability metrics are like health checkups for software—they assess the
system's dependability and consistency.
● Here are three common reliability metrics:
1. Mean Time Between Failures (MTBF):
a. MTBF is like predicting how long your car will run smoothly
before experiencing issues.
b. It measures the average time between system failures. The
higher the MTBF, the more reliable the system is considered.
c. MTBF= MTTF + MTTR
2. Mean Time to Failure (MTTF):
a. MTTF is like estimating how long a lightbulb will last.
b. It represents the average time a system can be expected to run
before the first failure occurs.
c. Like MTBF, a higher MTTF indicates better reliability.
3. Availability:
a. Availability is like knowing how often your favorite coffee
shop is open.
b. It quantifies the percentage of time a system is operational and
available for use.
c. High availability indicates a reliable and accessible system.
d. Availability = [MTTF / (MTTF + MTTR)] x 100%

5. How to use defects for process improvement.

Ans:
● Using defects for process improvement is like turning setbacks into
opportunities for growth.
● Identification and Logging:
Identify and log defects systematically during the testing phase.
● Root Cause Analysis:
Investigate the root causes of defects. Understand why they
occurred—whether it's a coding error, unclear requirements, or a
miscommunication.
● Categorization and Prioritization:
Categorize defects based on their nature and prioritize them.
● Implement Corrective Actions:
Develop and implement corrective actions based on the root cause
analysis.
● Continuous Monitoring:
 Continuously monitor the effectiveness of implemented corrective actions.
● Iterative Process:
Regularly review and refine the defect management and resolution process
based on ongoing feedback and experiences.

6. Explain in brief software quality factors.

Ans:
● Software quality factors are like the ingredients that contribute to the
overall goodness of a product.
● Software quality factors.
1. Functionality:
Functionality measures how well the software performs its intended
tasks and features.
2. Reliability:
Reliability assesses how dependable and consistent the software is in
delivering its functionality.
3. Usability:
it measures how user-friendly and accessible the software is for its
intended users.
4. Efficiency:
it evaluates how well the software utilizes resources like memory
and processing power to perform tasks.
5. Maintainability:
it measures how easily the software can be updated, enhanced, or
fixed over time.
6. Portability:
It assesses how well the software can run across different
environments and platforms.
7. Security:
It measures how well the software protects data, prevents
unauthorized access, and maintains the integrity of information.
8. Scalability:
it assesses how well the software can handle increased workload and
adapt to growing user demands.
9. Compatibility:
It measures how well the software interacts with other systems,
devices, and software.
10.Testability:
It evaluates how easily the software can be tested to ensure it meets
quality standards.
 7. What is 6 sigma explains its four steps.
Ans:
● Six Sigma is a structured approach to finding the root cause of more
complex problems.
● The term "Six Sigma" refers to the goal of achieving a level of performance
where only 3.4 defects per million opportunities are allowed.
● Dive into the data to identify the root causes of defects or variations.
● Implement changes to address the root causes. It's like fine-tuning an
instrument to get the perfect sound.
● The four steps of the Six Sigma methodology are often summarized by the
acronym DMAIC, which stands for Define, Measure, Analyze, Improve, and
Control.
1. Define:
In this step, it's like identifying the recipe you want to perfect. Define
the problem, the goals of improvement, and the scope of the project.
2. Measure:
This step is like taking precise measurements in cooking. Measure
the current performance of the process using data and metrics.
3. Analyze:
Similar to analyzing the flavors in a dish, this step involves
identifying root causes of issues. Analyze the data collected to
understand the factors contributing to the problem.
4. Improve:
It's like adjusting the recipe to enhance its taste. In the Improve
phase, develop and implement solutions to address the identified
issues.

8. FTR explains its objective.

Ans:
● Que 14 unit 2 same ans

9. Explain types of quality cost.

Ans:
● Que 12 unit 2 same ans

10.Explain sqa and software reliability in brief.

Ans: Unit 1 que 1 (SQA)
● Software reliability:
 1. It refers to the probability of the software performing its intended
functions without failures over a specified period and under defined
conditions.
2. In simpler terms, software reliability measures how dependable and
consistent a software system is in delivering its functionality without
unexpected errors or breakdowns.
3. To enhance software reliability, development teams focus on
improving code quality, conducting thorough testing, and
implementing measures to identify and address potential issues
early in the development process.

11.Explain challenges in SQA and background issues in SQA .

Ans:
● Challenges in SQA (Software Quality Assurance):
1. Changing Requirements:
Frequent changes in project requirements can make it challenging to
maintain consistency in testing and ensure that the software meets
evolving expectations.
2. Communication Gaps:
Ineffective communication between development and testing teams
may result in misunderstandings, affecting the overall quality of
testing.
3. Complex Technologies:
Rapid advancements in technology introduce complexities in testing
4. Global Collaboration:
Collaboration among globally distributed teams introduces
challenges related to time zones
● Background issues in SQA .
1. Insufficient Training:
Inadequate training programs for testers can result in a lack of
expertise and proficiency in utilizing modern testing techniques and
tools.
2. Limited Resources:
Organizations may allocate limited resources to SQA, leading to
challenges in conducting comprehensive testing activities.
3. Fragmented Processes:
Fragmented and disconnected testing processes may result in
inconsistencies and gaps in the overall quality assurance approach.
4. Tool and Technology Dependency:
 Over Reliance on specific testing tools or technologies without a
holistic understanding of testing principles can limit the
effectiveness of SQA efforts.

12.Explain defect management and its life cycle.

Ans:
● Que 1 Unit 3
● Life cycle:

1. New: This is the first state of a defect in the Defect Life Cycle. When
any new defect is found, it falls in a ‘New’ state
2. Assigned: In this stage, a newly created defect is assigned to the
development team to work on the defect.
3. Open: Here, the developer starts the process of analyzing the defect
and works on fixing it, if required.
4. Fixed: When the developer finishes the task of fixing a defect by
making the required changes then he can mark the status of the
defect as “Fixed”.
5. Pending Retest: Pending Retest is a status assigned to a defect after
the developer fixes it.
6. Retest: At this point, the tester starts the task of retesting the defect to
verify if the defect is fixed accurately by the developer as per the
requirements or not.
7. Reopen: If any issue persists in the defect, then it will be assigned to
the developer again for testing and the status of the defect gets
changed to ‘Reopen’.
8. Verified: If the tester does not find any issue in the defect after being
assigned to the developer for retesting
 9. Closed: When the defect does not exist any longer, then the tester
changes the status of the defect to “Closed”.

13.Explain in a brief quality improvement tool.

Ans:
● It's a systematic approach or technique used to analyze and improve the
quality of a system, process, or product.
● These tools facilitate decision-making, problem-solving, and continuous
improvement. Examples include:
1. Pareto Analysis:
a. Similar to a magnifying glass, it prioritizes issues by focusing
on the most significant factors contributing to problems.
b. It helps in directing efforts where they can have the most
impact.
2. Scatter Diagrams:
a. An analytical tool that helps identify relationships between
variables.
b. It's like connecting the dots to understand correlations and
make informed decisions.
3. Six Sigma:
a. Like a precision tool, Six Sigma is a comprehensive
methodology for minimizing defects and variations in
processes.
b. It provides a structured approach to achieving high-quality
results.
4. Cause- Effect Diagram:
a. Like a detective tool, it helps identify and analyze the potential
causes of a problem, allowing teams to address root causes
rather than symptoms.
5. Run Chart:
a. A Run Chart is like a timeline visualizing data points over
time.
b. It helps track trends, patterns, and variations in a process or
phenomenon.

14.Explain scatter diagrams in detail.

Ans:
● A scatter diagram, also known as a scatter plot or scatter graph, is a visual
representation of the relationship between two variables.
 ● It's like a map that helps you explore how changes in one variable might be
associated with changes in another.

● Example:
Consider a scatter diagram comparing the hours of study (x-axis) and exam
scores (y-axis) for a group of students. If there is a positive correlation, it
suggests that more study hours are associated with higher exam scores.
● scatter diagrams are powerful tools for visually exploring relationships
between two variables.
● They provide a quick and intuitive way to understand patterns and trends
in data, aiding decision-making and further analysis.

15.Explain run charts.

Ans:
● A run chart is a line graph of data plotted over time.
● By collecting and charting data over time, you can find trends or patterns
in the process.
● Because they do not use control limits, run charts cannot tell you if a
process is stable.
● However, they can show you how the process is running.
● The run chart can be a valuable tool at the beginning of a project, as it
reveals important information about a process before you have collected
enough data to create reliable control limits.
 ● Example:
1. Consider a run chart tracking the response times of a customer
support system over several weeks.
2. The chart would display data points for each week, showing whether
response times are consistent, improving, or showing signs of
deterioration.

16.What is TQM?
Ans:
● TQM ( Total Quality management )
● This management approach is used to simplify supply chain management,
as well as to detect, reduce or remove errors.
● TQM can have a beneficial effect on employee and organizational
development.
● It's all about everyone in the company working together to make things
better all the time.
● To properly execute on TQM methods, the entire organization needs to
operate as a single unit in the pursuit of excellence.
● TQM is like having a winning strategy that involves everyone in the
company, focusing on making customers happy, improving all the time, and
working together for success.
● Total quality management aims to hold all parties involved in the
production process accountable for the overall quality of the final product
or service.
 17.Explain pareto diagrams with examples.
Ans:
● Pareto Analysis is a powerful quality and decision-making tool.
● If implemented properly, it will help in identifying the major pitfalls in any
process flow which in turn improves the quality of the product/business.
● It is an excellent visualization tool to visualize the issues quickly.
● Example:

● The Pareto chart considers the percentage of frequency (or measure) and
cumulative percentage of measures to draw a line along with bars.
● Pareto charts are the best chart to do the analysis of the bulk of data.
● Basically these graphs give statistical information on a bulk of information
for each category.

18.Explain the following: a) ISO b) ISO 9000 c) ISO 9000 series

Ans:
● ISO (International Organization for Standardization):
1. ISO is like a big global team that creates rules everyone can follow.
2. These rules make sure things are safe, work well, and everyone
speaks the same language when it comes to quality and standards.
● ISO 9000:
1. ISO 9000 is like a set of guides that help companies do things better.
2. It's not one specific rule but a bunch of guidelines on how to manage
quality
● ISO 9000 Series:
1. The ISO 9000 series is like a collection of those guides in the toolkit.
Each guide focuses on a different aspect of quality management.
 2. For example, one guide (ISO 9001) is all about making sure
customers are happy with what a company does, while another (ISO
9004) gives advice on achieving long-term success.
● In a nutshell, ISO is a team creating global standards, ISO 9000 is a toolkit
for companies to improve, and the ISO 9000 series is a collection of guides
in that toolkit.

19.Explain Probability of Failure on Demand.

Ans:
● Probability of Failure on Demand (PFD) is like a measure that tells us how
likely something is to go wrong when it's needed.
● It's commonly used in the context of safety systems, especially in industries
where ensuring the reliability of safety mechanisms is critical.
● Probability of Failure on Demand (PFD):
1. What it Measures:
PFD tells us how likely it is for a safety system to not work when we
really need it to.
2. Imagine a Safety System:
Think of a safety system like the superhero of machines.
3. Calculating the Chances:
Smart people use complex math to figure out these chances.
4. Why it Matters:
In serious jobs, like handling dangerous chemicals or flying planes,
knowing the PFD helps make sure systems are super reliable.
● Example
1. Imagine a safety system that stops a big machine from getting too
hot. PFD would tell us how likely it is for this safety system to not do
its job when the machine is about to overheat