Quality by Design (QbD)

Slides:



Advertisements
Similar presentations
Design Constraints For Engineering Projects
Advertisements

Performance Evaluation Using the Balanced Scorecard
Chapter 4 Quality Assurance in Context
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Intuitive Design Inc. New Product Development Progress March 25, 2006 Prepared for: Company Management Team Dave Leis.
ITIL: Service Transition
TALOS Total ATM Life-cycle operational Solution. The Cost equation Life cycle costs are high Life cycle costs are complex Life cycle costs involve all.
Sami Aly Issues in Telecommunications3 February 2002 Development Plan 1.Product & Releases, evolution (Time line) 2.Features roll out 3.System.
Prof. Seppo Virtanen TUT PURESAFE Final Conference Tuesday 20 January 2015, 14:20 – 14:40 RAMS Methods and Tools: From LHC to FCC.
1 Software Testing and Quality Assurance Lecture 33 – Software Quality Assurance.
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
Quality by Design (QbD) N. Vidyashankar 1Quality by Design (QbD), FICCI, 19th Jan 2012.
Notion of a Project Notes from OOSE Slides - modified.
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
ES305: Virtual Tools in Engineering Design: The Eng. Design Process James Carroll, Associate Professor Electrical and Computer Engineering.
Designing Products and Processes with a Future. What does it take? Involve the customer Meet with the customer Listen to customer Educate the customer.
Introduction to Computer Technology
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Software Project Management Fifth Edition
Relex Reliability Software “the intuitive solution
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Laudon & Laudon: Canadian Edition
Engineering System Design
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
111 Notion of a Project Notes from OOSE Slides – a different textbook used in the past Read/review carefully and understand.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
Note Excerpts from Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
About Quality Pre paired By: Muhammad Azhar. Scope What is Quality Quality Attributes Conclusion on software Quality Quality Concepts Quality Costs.
Senior Design II proposal A step-by-Step review. What is Senior Design?  Senior Design is a sequence of two courses during two consecutive semesters.
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
Software Safety Case Why, what and how… Jon Arvid Børretzen.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Operations Management - 5 th Edition Chapter 3 Roberta Russell.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Defining Design Goals and Design Requirements © 2013 Project Lead The Way, Inc.Engineering Design and Development.
Smart Home Technologies
Reliability Applied to KM3NET
The Second Annual Medical Device Regulatory, Reimbursement and Compliance Congress Presented by J. Glenn George Thursday, March 29, 2007 Day II – Track.
Chapter 12 The Network Development Life Cycle
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Studio 5. Need Analysis SPRING 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.
Skills and products portfolio an overview Lorenzo Martinelli – Business Development Contact:
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
Design Process Design process is a collection of procedures and habits that help teams design better products.
The Rotation Sleeve System Triangle Equipment AS in co-operation with Ericsson Saab Avionics AB The EXPRO Group.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Product Lifecycle Management
2012 Spring Simulation Interoperability Workshop
Software Quality Engineering
Table of Contents: Design
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software Quality Engineering
Integrating Quality Activities in the Project Life Cycle
Engineering Processes
Introduction to Software Testing
Testing web applications
Engineering Processes
THE PROCESS OF INTERACTION DESIGN
Design Constraints For Engineering Projects
Chapter 2: Development process and organizations
Chapter 1: Software and Software Engineering
Presentation transcript:

Quality by Design (QbD) N. Vidyashankar Quality by Design (QbD), FICCI, 19th Jan 2012

Product Development Lifecycle System Requirements Design Development Integration V&V Quality by Design (QbD), FICCI, 19th Jan 2012

Opportunities to accomplish Quality Quality by Plan not a chance !!!! & 1:10:100:1000 rule Cost of Defect fix Low Customer Satisfaction Brand Image Market Value Cost of defect fix Reliability Gross Margin Desired objective Correcting at the Point of Use- Repairs/ Replacements Quality Control- Testing/ Inspection Quality Assurance- Reviews, Proto typing, simulation, modeling, etc Design High Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD) Quality by Design (QbD) is a concept first outlined by well-known quality expert Joseph M. Juran who believed that quality could be planned, and that most quality crises and problems relate to the way in which quality was planned in the first place. Proactive & risk based approach for predictable & predefined quality Planning quality into the process A leading indicator for better controls & to handle quality crises and problems early in the cycle Quality by Design (QbD), FICCI, 19th Jan 2012

Interpretations of Quality Meeting Specifications Features Perception Easy Maintenance Fitness for use Cost Time Satisfaction QUALITY Safety Standards compliance Regulations Experience Look & Feel Aesthetics Performance Quality by Design (QbD), FICCI, 19th Jan 2012

Target Quality Profiling- A Perspective Market Regulations Corporate Social Responsibility Customer Research HRM) Installation & Service Business insights Engineering Manufacturability Suppliers Purchasing Competitor(s) Quality by Design (QbD), FICCI, 19th Jan 2012

Critical Decision Factors Clarity on Product Roadmap Intended Use Hardware v/s software budgeting in System Design Target Markets(s) Make-Buy, Inhouse- Outsource decision Standardization activities Budgeting between Hardware & Software Change Mgt Process automation v/s resource intensive processes Quality by Design (QbD), FICCI, 19th Jan 2012

Attributes contributing to Product Quality Quality by Design (QbD), FICCI, 19th Jan 2012

Critical to Quality (CTQ) Explicit Requirements Implicit Requirements Getting all the Product Requirements is the first step to plan for Quality Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD), FICCI, 19th Jan 2012 Quality Attributes Time Quality Cost Customer/ Market Tradeoff between Q-C-T Innovations or New Technologies available Involving all relevant stake holders for inputs/ requirements & clear acceptance criteria Quick design realisation timelines (Design throughput time)- Early entry to capture market, staying in market Predictability/ forecasting of failure & Obsolescence of Electronics and SW components Ergonomics & Usability Hardware to Software transition Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD), FICCI, 19th Jan 2012 Quality Attributes Joint Development and design modularity Globalisation & localisation requirements- Design anywhere and Build anywhere Miniaturisation of components- size, weight, interfaces, interop, Packaging, storaging & handling Designing for Abuse/ misuse Multifeatured Look and Feel Intelligence & decision making protocols Redundancy Planning Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD), FICCI, 19th Jan 2012 Quality Attributes Customers & User community Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD), FICCI, 19th Jan 2012 Quality Attributes Environmental Conditions salt content Emi/ emc temperature humidity vibrations Antistatic packaging Current/ voltage variations moisture shock Altitudes & pressure contamination Quality by Design (QbD), FICCI, 19th Jan 2012 more……

Social Responsibility & Sustainability reporting Quality Attributes Social Responsibility & Sustainability reporting (RoHS, ECO, REACH, WEEE, Battery disposal ) Regulations Safety Security & Privacy Radiation Sterlisation Quality by Design (QbD), FICCI, 19th Jan 2012

Process Approach to Product Quality Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD), FICCI, 19th Jan 2012 Process Approach ISO 9001 Process Model There is no GOOD or BAD process Quality by Design (QbD), FICCI, 19th Jan 2012

Process Quality Assurance Process definitions to be aligned with Skills & competency of staff to achieve defined criteria Unambiguous design inputs including analysis of Field experiences/ performances including similar products in markets Detailed Risk evaluation and mitigation Alternative design evaluations Design reviews at each product development stages by early involvement of all stakeholders Prototyping & feasibility tests, Simulation, DEMOs, BETA models, DFSS, Design of Experiments (DOE), Brainstorming, Design calculations, FMEA, Fault Tree Analysis, Inhouse tests Quality by Design (QbD), FICCI, 19th Jan 2012

Process Quality Assurance Early tests- Burn-in Tests, Accelerated tests- Stress, reliability, endurance, Environmental tests (corrosion, Design qualification for safety & efficacy including Product type tests and product certifications User Experience/ Field tests followed by Field performance analysis and design improvements Closed loop process controls & performance improvements Process & domain trainings to staff Strong Change Management process Quality by Design (QbD), FICCI, 19th Jan 2012

Quality by Design (QbD), FICCI, 19th Jan 2012 Q&A Quality by Design (QbD), FICCI, 19th Jan 2012