KARPAGAM ACADEMY OF HIGHER EDUCATION
CLASS: I B.Sc. CS (AI&DS) & I B.Sc. CS (Cog Sys), COURSE CODE: 22ADU101,22CGU101
BATCH-2022-2025
COURSE NAME: Problem Solving Techniques
Unit II- Programming Construction Tools
Unit II
Programming Construction Tools:
Programming Construction Tools Problem Analysis, Process Analysis, Conceptual Development of
Solution. Development Tools: Algorithm – definition, practical examples, properties, representation,
algorithms vs programs. Algorithm: Types of Algorithms, Algorithm of Analysis, Advantage and
Disadvantage of Algorithm, Complexity of Algorithm, Big-O Notation.
Programming construction tool:
Problem Analysis:
Problem analysis begins by identifying and collecting information about known needs, issues and
problems. Generally, this information has been gathered previously in questionnaires, workshops and
focus groups. Generate a list of problems. Remove redundancy from the list of problems by placing the
first problem statement in a category. Read the second problem statement. Ask the question: "Is it similar
to the first?" If so, place it in the same category, and go to the next problem statement. If not, place it in its
own category, and go on to the next problem statement. Repeat this process until all problem statements
have been placed in a category.
The goal of problem analysis is to gain a better understanding of the problem being solved before
developing a solution.
Prepared by S.Sumathi, Asst Prof, Dept of Computer Science, KAHE P a g e 1 | 20
, KARPAGAM ACADEMY OF HIGHER EDUCATION
CLASS: I B.Sc. CS (AI&DS) & I B.Sc. CS (Cog Sys), COURSE CODE: 22ADU101,22CGU101
BATCH-2022-2025
COURSE NAME: Problem Solving Techniques
Unit II- Programming Construction Tools
There are five useful steps that can be taken to gain a better understanding of the problem before
developing a solution.
1. Pareto Chart
A Pareto chart is a histogram or bar chart combined with a line graph that groups the frequency or cost of
different problems to show their relative significance. The bars show frequency in descending order, while
the line shows cumulative percentage or total as you move from left to right.
The Pareto chart example above is a report from layered process audit software that groups together the
top seven categories of failed audit questions for a given facility. Layered process audits (LPAs) allow you
to check high-risk processes daily to verify conformance to standards. LPAs identify process variations
that cause defects, making Pareto charts a powerful reporting tool for analyzing LPA findings.
Pareto charts are based on Pareto’s law, also called the 80/20 rule, which says that 20% of inputs drive
80% of results.
2. 5 Whys
The 5 Whys is a method that uses a series of questions to drill down into successive layers of a problem.
The basic idea is that each time you ask why, the answer becomes the basis of the next why. It’s a simple
tool useful for problems where you don’t need advanced statistics, so you don’t necessarily want to use it
for complex problems.
One application of this technique is to more deeply analyze the results of a Pareto analysis. Here’s an
example of how to use the 5 Whys:
Problem: Final assembly time exceeds target
Why is downtime in final assembly higher than our goal? According to the Pareto chart, the biggest
factor is operators needing to constantly adjust Machine A
Why do operators need to constantly adjust Machine A? Because it keeps having alignment
problems
Why does Machine A keep having alignment problems? Because the seals are worn
Why are Machine A’s seals worn? Because they aren’t being replaced as part of our preventive
maintenance program
Prepared by S.Sumathi, Asst Prof, Dept of Computer Science, KAHE P a g e 2 | 20
, KARPAGAM ACADEMY OF HIGHER EDUCATION
CLASS: I B.Sc. CS (AI&DS) & I B.Sc. CS (Cog Sys), COURSE CODE: 22ADU101,22CGU101
BATCH-2022-2025
COURSE NAME: Problem Solving Techniques
Unit II- Programming Construction Tools
3. Fishbone Diagram
A fishbone diagram sorts possible causes into various categories that branch off from the original problem.
Also called a cause-and-effect or Ishakawa diagram, a fishbone diagram may have multiple sub-causes
branching off of each identified category.
4. Scatter Plot Diagram
A scatter plot or scatter diagram uses pairs of data points to help uncover relationships between variables.
A scatter plot is a quantitative method for determining whether two variables are correlated, such as testing
potential causes identified in your fishbone diagram.
Making a scatter diagram is as simple as plotting your independent variable (or suspected cause) on the x-
axis, and your dependent variable (the effect) on the y-axis. If the pattern shows a clear line or curve, you
know the variables are correlated and you can proceed to regression or correlation analysis.
5. Failure Mode and Effects Analysis (FMEA)
Failure mode and effects analysis (FMEA) is a method used during product or process design to explore
potential defects or failures. An FMEA chart outlines:
Potential failures, consequences and causes
Current controls to prevent each type of failure
Severity (S), occurrence (O) and detection (D) ratings that allow you to calculate a
risk priority number (RPN) for determining further action
Prepared by S.Sumathi, Asst Prof, Dept of Computer Science, KAHE P a g e 3 | 20
CLASS: I B.Sc. CS (AI&DS) & I B.Sc. CS (Cog Sys), COURSE CODE: 22ADU101,22CGU101
BATCH-2022-2025
COURSE NAME: Problem Solving Techniques
Unit II- Programming Construction Tools
Unit II
Programming Construction Tools:
Programming Construction Tools Problem Analysis, Process Analysis, Conceptual Development of
Solution. Development Tools: Algorithm – definition, practical examples, properties, representation,
algorithms vs programs. Algorithm: Types of Algorithms, Algorithm of Analysis, Advantage and
Disadvantage of Algorithm, Complexity of Algorithm, Big-O Notation.
Programming construction tool:
Problem Analysis:
Problem analysis begins by identifying and collecting information about known needs, issues and
problems. Generally, this information has been gathered previously in questionnaires, workshops and
focus groups. Generate a list of problems. Remove redundancy from the list of problems by placing the
first problem statement in a category. Read the second problem statement. Ask the question: "Is it similar
to the first?" If so, place it in the same category, and go to the next problem statement. If not, place it in its
own category, and go on to the next problem statement. Repeat this process until all problem statements
have been placed in a category.
The goal of problem analysis is to gain a better understanding of the problem being solved before
developing a solution.
Prepared by S.Sumathi, Asst Prof, Dept of Computer Science, KAHE P a g e 1 | 20
, KARPAGAM ACADEMY OF HIGHER EDUCATION
CLASS: I B.Sc. CS (AI&DS) & I B.Sc. CS (Cog Sys), COURSE CODE: 22ADU101,22CGU101
BATCH-2022-2025
COURSE NAME: Problem Solving Techniques
Unit II- Programming Construction Tools
There are five useful steps that can be taken to gain a better understanding of the problem before
developing a solution.
1. Pareto Chart
A Pareto chart is a histogram or bar chart combined with a line graph that groups the frequency or cost of
different problems to show their relative significance. The bars show frequency in descending order, while
the line shows cumulative percentage or total as you move from left to right.
The Pareto chart example above is a report from layered process audit software that groups together the
top seven categories of failed audit questions for a given facility. Layered process audits (LPAs) allow you
to check high-risk processes daily to verify conformance to standards. LPAs identify process variations
that cause defects, making Pareto charts a powerful reporting tool for analyzing LPA findings.
Pareto charts are based on Pareto’s law, also called the 80/20 rule, which says that 20% of inputs drive
80% of results.
2. 5 Whys
The 5 Whys is a method that uses a series of questions to drill down into successive layers of a problem.
The basic idea is that each time you ask why, the answer becomes the basis of the next why. It’s a simple
tool useful for problems where you don’t need advanced statistics, so you don’t necessarily want to use it
for complex problems.
One application of this technique is to more deeply analyze the results of a Pareto analysis. Here’s an
example of how to use the 5 Whys:
Problem: Final assembly time exceeds target
Why is downtime in final assembly higher than our goal? According to the Pareto chart, the biggest
factor is operators needing to constantly adjust Machine A
Why do operators need to constantly adjust Machine A? Because it keeps having alignment
problems
Why does Machine A keep having alignment problems? Because the seals are worn
Why are Machine A’s seals worn? Because they aren’t being replaced as part of our preventive
maintenance program
Prepared by S.Sumathi, Asst Prof, Dept of Computer Science, KAHE P a g e 2 | 20
, KARPAGAM ACADEMY OF HIGHER EDUCATION
CLASS: I B.Sc. CS (AI&DS) & I B.Sc. CS (Cog Sys), COURSE CODE: 22ADU101,22CGU101
BATCH-2022-2025
COURSE NAME: Problem Solving Techniques
Unit II- Programming Construction Tools
3. Fishbone Diagram
A fishbone diagram sorts possible causes into various categories that branch off from the original problem.
Also called a cause-and-effect or Ishakawa diagram, a fishbone diagram may have multiple sub-causes
branching off of each identified category.
4. Scatter Plot Diagram
A scatter plot or scatter diagram uses pairs of data points to help uncover relationships between variables.
A scatter plot is a quantitative method for determining whether two variables are correlated, such as testing
potential causes identified in your fishbone diagram.
Making a scatter diagram is as simple as plotting your independent variable (or suspected cause) on the x-
axis, and your dependent variable (the effect) on the y-axis. If the pattern shows a clear line or curve, you
know the variables are correlated and you can proceed to regression or correlation analysis.
5. Failure Mode and Effects Analysis (FMEA)
Failure mode and effects analysis (FMEA) is a method used during product or process design to explore
potential defects or failures. An FMEA chart outlines:
Potential failures, consequences and causes
Current controls to prevent each type of failure
Severity (S), occurrence (O) and detection (D) ratings that allow you to calculate a
risk priority number (RPN) for determining further action
Prepared by S.Sumathi, Asst Prof, Dept of Computer Science, KAHE P a g e 3 | 20
