Engineering Quality Assurance Methods

When brands compare T-shirts, they often start with: Fabric weight Cotton quality Shrinkage Handfeel All important. But here is the part many founders overlook: Good fabric cannot save weak construction. Two tees can use the same 280gsm cotton jersey. Yet after repeated wear and washing: One keeps its shoulder line. The other twists at the side seam. One neckline stays flat. The other starts waving. One hem falls clean. The other looks bulky or uneven. The difference is often not the fabric. It is the seam decision behind the fabric. Examples: A seam that cannot handle stretch will fight the garment during wear. Poor edge finishing can affect how clean the inside looks over time. Wrong tension or construction around high-stress areas can distort the silhouette. A washed garment may expose stitching weakness that looked fine before laundry testing. This is why experienced product teams do not judge quality from a flat lay photo alone. They ask: How is the shoulder joined? How is the collar attached and stabilized? Will the side seams behave after wash? Is this construction chosen for the garment — or just for sewing speed? Fabric creates the first “wow.” Construction decides whether the product earns a second order. For streetwear brands, especially when retail prices keep rising, this matters. Customers may not know what seam method was used. But they know when a tee loses its shape too soon. Founders: Have you ever upgraded fabric, but still felt the finished garment did not look premium enough? #ApparelDevelopment #GarmentConstruction #SeamEngineering #ProductQuality #StreetwearBrand #FashionManufacturing #TechPackTips #SourcingWisdom #FabricVsConstruction #FromSampleToBulk #ClothingBrandInsights #PremiumBasics

During the initial phase of my career in VLSI, I realised that writing Testcases is equally important as Testbench development. A Testcase in any language be it Verilog, VHDL, SystemVerilog, and UVM is not only used to verify the functional correctness and the integrity of the design but also point out areas where the Testbench could be improved. Below are the most important category of Testcases which are most critical: [1] Functional Tests --> In this type of test, the functionality or feature of an IP/module or a subsystem is verified. [2] Register-based Tests --> RW Tests, RO/WO Tests, Default Read/Hard reset Tests, Soft reset tests, Negative RO/WO Tests, Aliasing, Broadcasting, etc [3] Connectivity Tests [4] Clock and Reset Tests [5] Boot up Tests, wake up sequence, training sequence tests. For eg. In the case of DDR – MPC Training, RD DQ Calibration, Command Bus training, Write leveling, etc [6] Command and Sequence-based Tests. [7] Overlapping and Unallocated Region tests. [8] Back-to-back data transfer-based tests. [9] UPF Tests --> Power domain, Level Shifter, clock gating, voltage domain, etc [10] Code Coverage Tests --> In this test toggle, expression, branch, FSM, and conditional coverage holes are measured, and depending on the holes, tests are being written to completely exercise the DUT. [11] Functional Coverage Tests --> In these types of test categories, the functionality of DUT is being measured with the help of bins. There are several ways to do it. If there are coverage holes, more bins are coded to cover those areas, complex scenarios are covered with cross coverage, and bins of intersect functionality. [12] Assertions are basically a check against the design. Basically, these are insertion points within the design which improve the observability and debugging ability. The above are some of the categorizations of tests that need to be applied while checking a design but to achieve all the above features, testcases are broadly classified into the following two types: [1] Directed Testcase: These are the scenarios that the verification engineers can think of or can anticipate. [2] RandomTestcase: These are the scenarios where the maximum amount of bugs can be caught. The random seeds will hit many different use cases which can not be anticipated earlier and has the probability to catch the design issues. Ideally, random tests can be classified into the following two categories: [1] Corner cases --> This is the bug that is only possible to catch when many different scenarios are processed together or they overlap and the best way to catch this type of scenario is to run more repeated regression with more seeds. [2] Stress testing -->These types of tests are useful to check the performance and the scalability of the DUT under multiple concurrent activities and unpredictable scenarios. #vlsi #asic #electricalengineering #semiconductorindustry

A few years back, I found myself in a challenging situation – reviewing an automation project that was struggling in its early stages. The team, in their haste to kick-start, had neglected a crucial part: analyzing the test cases. The frustration was real, but it was also a catalyst for change. We had to go back to basics. We revamped our test cases, ensuring they were complete with detailed steps and verification points. We built in application configurations and settings into each test case. By calling out data dependencies, we enabled the test case to run with various data sets. Compliance-critical steps were marked as 'Evidence Required', ensuring necessary screenshots were captured. Perhaps most importantly, we broke down test cases into smaller, independent functions, enhancing their reusability across different tests. This seemingly frustrating phase led to an important learning: taking the time to optimize your test cases is not wasted, but rather invested. It drastically improves the reliability and quality of your automation scripts, ensuring the success of your project. Remember, the struggle you're in today is developing the strength you need for tomorrow. Have you faced similar struggles in your projects? How did you overcome them? #testautomation #softwaretesting #qualityassurance

How to Write UAT Test Cases (for Business Analysts) I remember when I was a junior BA - the idea of UAT scared me. I didn’t want to admit I didn’t know where to start... So I stayed quiet and tried to figure it out on my own. Turns out, I’d built it up to be more complicated than it really is. Here’s what I learned: As a BA, your role in User Acceptance Testing (UAT) is to ensure the solution actually meets the business need… not just that it functions. To do that effectively, you need a structured approach to writing UAT test cases. Here's how I do it: 1️⃣ Start with the Requirement → Begin with a single requirement or user story. → Each requirement must be tested, and depending on how many acceptance criteria it has, you may need multiple test cases. (Think: What is the business expecting from this requirement?) 2️⃣ Review the Acceptance Criteria → Acceptance criteria define the boundary of success for a requirement. → They help you understand what “good” looks like from the business’s perspective. (Use these criteria as your guideposts for what to test) 3️⃣ Develop Test Cases Based on the Acceptance Criteria → Each acceptance criterion should translate into at least one test case. → Some may need both a positive (happy path) and negative (error or edge case) scenario. (If a criterion says “User must receive a confirmation email,” test both a valid scenario and one where the email fails) 4️⃣ Complete the UAT Template for Each Test Case → For each test case, fill in these fields: ☑ Test Description – A clear statement of what’s being tested e.g. “Test password reset email is triggered for valid email addresses” ☑ Preconditions – Any setup required before testing e.g. “User is logged out and on the login page” ☑ Test Steps – Step-by-step actions for the tester to perform e.g. Click “Forgot Password”, enter email, submit form ☑ Expected Result – What should happen if the system works correctly e.g. “User receives reset email within 2 minutes” (TIP: Keep the language business-friendly so anyone can run the test) 5️⃣ Repeat for Each Requirement → Once you've completed the test cases for one requirement, move to the next and repeat the process. → This ensures full coverage and traceability back to each business objective. 6️⃣ Review with Business Stakeholders → Once your test cases are drafted, share them with your business SMEs or stakeholders. (This step is critical - their feedback confirms that you’re testing what really matters to them) 7️⃣ Prepare for Execution → After validation, the test cases are ready to be run. → Depending on your project, UAT may be carried out by business users, or you may help execute or facilitate it as a BA. 📩 Want a copy of my UAT test case template? → Send me a message and I’ll be happy to share it with you 😊 Found this interesting? Repost to your network, and follow me → Matthew Thomas Holliday #BusinessAnalysis #UAT #BAskills #BAmethods #UATtemplate

🔍 What is PPAP and Why Does It Matter in Modern Manufacturing? In the fast-paced world of automotive and manufacturing, delivering consistent quality is non-negotiable. Whether you’re supplying a critical ADAS sensor, a mechatronic HVAC component, or a bracket on the shop floor, your customer expects one thing: reliability. That’s where PPAP – the Production Part Approval Process – steps in. ⸻ 🚗 What is PPAP? PPAP is a structured process developed by the Automotive Industry Action Group (AIAG) and is a core element of APQP (Advanced Product Quality Planning). It is mandated by IATF 16949 and widely used in automotive, aerospace, and high-tech sectors. The goal? To demonstrate that a supplier can consistently meet customer design and quality requirements, particularly when: • Launching a new part • Changing design or materials • Shifting production location or tooling • Reinstating production after a long break ⸻ 🎯 The Objective of PPAP PPAP ensures: • Product design and specs are fully understood • Manufacturing processes are repeatable and stable • All parts meet customer requirements before mass production begins ⸻ 📄 The 18 Key Elements of PPAP (Level 3 Standard Submission) A Level 3 PPAP typically includes: 1. Design Records 2. Engineering Change Documentation 3. Customer Approval (if needed) 4. DFMEA & PFMEA 5. Process Flow Diagram 6. Control Plan 7. MSA (Measurement System Analysis) 8. Dimensional Results 9. Material Test Results 10. Initial Process Study (e.g., Cp, Cpk) 11. Qualified Lab Docs 12. Appearance Approval Report (AAR) 13. Sample Production Parts 14. Master Sample 15. Checking Aids 16. Customer-Specific Requirements 17. Part Submission Warrant (PSW) Every one of these steps helps ensure product conformity, process stability, and customer confidence. ⸻ 💡 Why Should You Care? Whether you’re in Quality Engineering, Project Management, or Supply Chain, understanding PPAP: • Helps you collaborate better with OEMs and Tier-1 suppliers • Supports zero-defect initiatives and traceability • Ensures faster SOP approvals and robust risk mitigation • Builds trust with internal stakeholders and external customers ⸻ 🧠 From My Experience In my role as a Project Quality Engineer at AUTOLIV TUNISIA I’ve supported PPAP activities for steering wheels. From defining Control Plans, facilitating Run@Rate inspections, to the usageSPC tools for process stability—PPAP has been the backbone of every successful launch. ⸻ 🛠 Bonus Tip ➡️ Invest time in understanding PPAP not as a formality, but as a value-adding quality gate. When done right, it doesn’t just prevent defects—it accelerates your credibility as a supplier. Let’s exchange insights — drop your experiences in the comments 👇 #PPAP #QualityEngineering #Automotive #Manufacturing #IATF16949 #APQP #SPC #SupplierQuality #ProcessImprovement #Industry40 #EngineeringExcellence

4M CONDITION CHECKLIST FOR MANUFACTURING PROCESS 4M Condition Table specifically tailored for the manufacturing sector, focusing on production process control, machine reliability, material conformity, and operator discipline. 1. Man (Operator) The operator is at the heart of any manufacturing process. Ensuring their readiness and discipline is critical. Operators must be trained and certified for the specific machines or tasks they handle. They should have clear awareness of safety procedures, quality standards, and work instructions. Physical and mental fitness must be monitored to avoid fatigue-related errors. Proper use of PPE (Personal Protective Equipment) such as gloves, helmets, and goggles is mandatory. Adherence to 5S and standard operating procedures (SOPs) ensures a clean and organized work area. 2. Machine (Equipment) The condition of machines directly affects production performance and product quality. Machines should be well-maintained, with preventive maintenance done as per schedule. Tools, jigs, and fixtures must be properly set and in good working condition. Safety systems like guards and emergency stops must be functional at all times. Machines should be free from abnormal noise, vibration, or leakage, indicating stable health. Critical spares must be available to avoid production delays due to breakdowns. 3. Material (Raw and In-process) Material quality and handling significantly influence the final product outcome. All materials must be received as per BOM (Bill of Materials) specifications and verified through incoming inspection. Proper labeling and traceability (batch number, lot number) must be maintained. Storage conditions should be appropriate to avoid damage, contamination, or rust. FIFO (First In, First Out) must be followed to manage shelf life and batch usage. Material must be available in the right quantity at the right time to prevent stoppages. 4. Method (Process) A standardized and controlled method ensures consistency and reduces variation. SOPs or work instructions must be available at the workplace and strictly followed. All process parameters (like temperature, pressure, torque) should be defined and monitored. In-process quality checks should be performed and recorded regularly. Cycle time and takt time must be maintained as per planning. Any changes in methods or processes must be documented through change control procedures.

𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗖𝗔𝗣𝗔: A Powerful Tool for Sustainable Quality Improvement In any manufacturing, product quality and consistency are critical. But despite best efforts, issues do occur — a deviation in production, a packaging defect, or a market complaint. This is when 𝗖𝗔𝗣𝗔 becomes more than just a process — it becomes a commitment to continuous improvement. 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗖𝗔𝗣𝗔? 𝗖𝗔𝗣𝗔 stands for Corrective and Preventive Action — a systematic method to: • Identify the root cause of a problem • Take actions to fix it • Prevent it from happening again It’s a key component of any robust Quality Management System (𝗤𝗠𝗦) and essential for operational excellence. 𝗪𝗵𝘆 𝗶𝘀 𝗖𝗔𝗣𝗔 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹? • Ensures product quality and consumer safety • Reduces recurring issues and production downtime • Supports regulatory and certification compliance (ISO, BRC, FDA, etc.) • Enhances team accountability and cross-functional learning • Builds long-term trust with consumers and stakeholders 𝗧𝗵𝗲 𝗖𝗔𝗣𝗔 𝗣𝗿𝗼𝗰𝗲𝘀𝘀: 𝗦𝘁𝗲𝗽 𝗯𝘆 𝗦𝘁𝗲𝗽 𝟭. 𝗣𝗿𝗼𝗯𝗹𝗲𝗺 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 • Receive and log the issue (complaint, audit non-conformance, or deviation). • Understand where, when, and how it was discovered. 𝟮. 𝗖𝗼𝗿𝗿𝗲𝗰𝘁𝗶𝗼𝗻 (𝗜𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲 𝗔𝗰𝘁𝗶𝗼𝗻) • Isolate the affected product or batch. • Inform relevant stakeholders and prevent further distribution. 𝟯. 𝗥𝗼𝗼𝘁 𝗖𝗮𝘂𝘀𝗲 𝗔𝗻𝗮𝗹𝘆𝘀𝗶𝘀 • Use structured tools: 5 Whys, Fishbone Diagram, Pareto Analysis • Focus on identifying the true systemic issue, not just symptoms. 𝟰. 𝗖𝗼𝗿𝗿𝗲𝗰𝘁𝗶𝘃𝗲 𝗔𝗰𝘁𝗶𝗼𝗻𝘀 • Implement targeted solutions to eliminate the root cause. • Examples: process change, retraining, equipment upgrade, supplier improvement. 𝟱. 𝗣𝗿𝗲𝘃𝗲𝗻𝘁𝗶𝘃𝗲 𝗔𝗰𝘁𝗶𝗼𝗻𝘀 • Assess risk across related areas. • Strengthen controls, modify SOPs, or introduce new checks to stop similar issues elsewhere. 𝟲. 𝗘𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲𝗻𝗲𝘀𝘀 𝗖𝗵𝗲𝗰𝗸 • Track KPIs and monitor trends. • Audit the implemented changes and ensure sustainability of results. 𝟳. 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗘𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 • Record all findings, actions, and decisions. • Good documentation ensures traceability and supports future audits or reviews. 𝗥𝗲𝗮𝗹-𝗪𝗼𝗿𝗹𝗱 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: A detergent pouch was reported leaking in distribution: • Correction: Recalled affected pouches and halted dispatch. • Root Cause Analysis: Identified sealing temperature inconsistency due to worn-out heating elements. • Corrective Action: Replaced machine components and retrained operators. • Preventive Action: Introduced new validation steps before every shift and added an automated sealing sensor. • Verification: No leakage reported in 3 months of follow-up data. #CAPA #QualityManagement #FMCG #Manufacturing #Compliance #RootCauseAnalysis #ContinuousImprovement #OperationalExcellence #QMS #ProblemSolving #AuditReady

Get this part right in your earthing studies. Rubbish model in = Rubbish values out. Correct! Real soils consist of multiple layers with varying resistivities. Not often 2 layers, rarely 1 layer. So, model your soil as multilayered. Multilayer soil modelling is a crucial process in earthing system design that involves: 1. Taking field measurements:    - Using Wenner or Schlumberger methods    - Measuring apparent soil resistivity at various electrode spacings    - Capturing resistivity variations with depth 2. Developing an equivalent soil model:    - Creating a simplified representation of the actual soil structure    - Typically using 2 to 5 layers with different resistivities    - Each layer is characterised by its thickness and resistivity 3. Fitting the model to measurements:    - Using specialised software (e.g., SafeGrid, CDEGS) to analyse data    - Adjusting layer parameters to match field measurements    - Minimizing the difference between model and measured values 4. Assessing model accuracy:    - Calculating Root Mean Square Error (RMSE)    - Aiming for RMSE below 15% for a good fit    - The lower the RMSE, the better the model 5. Applying the model:    - Using the multilayer model in earthing system calculations    - Improving the accuracy of grid resistance, touch voltages, and step voltages predicted Accurate soil modelling significantly impacts earthing system performance and safety.

6 Core Tools = Strong Foundation of Quality If we want zero rejection and smooth production, we must follow these tools daily on shop floor. 1) APQP – Plan Before Work Starts Team meeting, method final, machine setup, operator training. Good start = Good production. 2) PPAP – Customer Approval Make sample → Check dimensions → Prepare documents → Send to customer → Take approval. This builds trust. 3) FMEA – Stop Problems Before They Happen Go step-by-step and ask, What mistake can happen here? Take action before issue reaches customer. 4) Control Plan – Same Checking Method for All Write what to check and how to check. Keep sheet near machine. No confusion. No shortcuts. 5) MSA – Reliable Checking If measurement is not correct, whole process looks wrong. Check variation. Calibrate tool. Train people. 6) SPC – Control Variation Record values regularly on chart. If value moves near limit, adjust early. This avoids rework and rejection. Quality is not at final inspection. Quality starts from planning and discipline in process. Save it. Read again. Use daily. This will help your shop floor run smoother. #production #quality #manufacturing #shopfloor #lean #continuousimprovement #6coretools #engineerkamentor