answersLogoWhite

0

Following are the seven QC tools - Quality Control tools or Quality Circle tools (since they are used in Circles): 1. Check sheet (Data Collection sheet) 2. Bar chart, Pie chart, Histogram 3. Pareto Analysis (ABC analysis) 4. Cause and Effect diagram (Fishbone diagram) 5. Control Charts 6. Scatter Diagrams 7. Stratification analysis In addition to these 7 tools, Brainstorming is sometimes referred to as an OLD QC tool. For detailed reading, refer - TQM by JAYAKUMAR by SUGANTHI - Prentice hall

User Avatar

Wiki User

17y ago

What else can I help you with?

Continue Learning about Engineering

Is test link is better than QC?

No, Testlink is not better than QC (it would be a shame in regards to QC price !) byt XStudio is nearly as powerfull than QC for 50 times cheaper !


Where is the jacques Cartier bridge located?

in Montreal QC in Canada


What function would a QC Operator use to stop a batch from being uploaded to the RMS?

unrelease


Quality assurance and quality control?

From my experience in QA, this is one of the most common misconceptions in the field - people think Quality Assurance and Quality Control are the same thing. They're absolutely not, and understanding the difference is crucial for anyone working in software development. Quality Assurance (QA) is proactive - it's about preventing defects before they happen. QA focuses on establishing processes, standards, and procedures that ensure quality is built into the product from the beginning. Think of it as creating a framework that makes it nearly impossible for bad code to reach production. Quality Control (QC) is reactive - it's about detecting and fixing defects after they occur. QC involves testing, inspecting, and validating the finished product to catch issues before they reach users. The key differences I see in practice: Timing: QA happens throughout the entire development lifecycle, while QC typically occurs at the end during testing phases. Focus: QA is process-oriented (how we build software), while QC is product-oriented (what we actually built). Approach: QA asks "Are we following the right processes?" while QC asks "Does this product work correctly?" Examples from my experience: QA activities: Writing coding standards, establishing review processes, creating test strategies, setting up CI/CD pipelines QC activities: Running test cases, performing code reviews, conducting user acceptance testing, bug reporting The relationship: QC is actually a subset of QA. You can't have effective quality control without solid quality assurance processes in place first. In practice, both are essential. Great QA processes reduce the number of defects QC needs to catch, but you still need QC as your safety net. Teams that only focus on one usually struggle with quality issues - either they're constantly firefighting bugs (weak QA) or they're shipping products with obvious defects (weak QC).


Meaning of driving tools?

driving tools is driving tools! thank you!