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

Slides:



Advertisements
Similar presentations
Design Constraints For Engineering Projects
Advertisements

SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
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.
1 Software Testing and Quality Assurance Lecture 33 – Software Quality Assurance.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
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.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Software Quality Assurance For Software Engineering && Architecture and Design.
Introduction to Computer Technology
Product Lifecycle Management Cost of Quality Pasi Kaipainen, Mika Huhta.
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 Quality SEII-Lecture 15
Software Project Management Fifth Edition
Chapter 15 Systems Development
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
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Mission Assurance Concepts and Discussion NEPTUNE Power CoDR Richard Kemski June 10, 2002.
Engineering System Design
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
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.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
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.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
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.
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.
CSE 303 – Software Design and Architecture
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
Chapter 2: Development process and organizations
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Designing Goods and Services Chapter 3, Part 1. MGMT 326 Foundations of Operations Introduction Strategy Quality Assurance Capacity, Facilities, & Work.
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.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
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.
Module 13 Reliability 1. Key Dimensions of Quality Performance – primary operating characteristics Features – “bells and whistles” Reliability – probability.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Product Lifecycle Management
ITIL: Service Transition
Table of Contents: Design
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Engineering Processes
Quality by Design (QbD)
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 1Quality by Design (QbD), FICCI, 19th Jan 2012

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

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

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.Joseph M. Juran Based on FTR Philosophy 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 20124

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

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

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

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

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

Quality Attributes 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 IP protection and market sustainance Predictability/ forecasting of failure & Obsolescence of Electronics and SW components Ergonomics & Usability Hardware to Software transition Time Quality Cost Customer/ Market Quality by Design (QbD), FICCI, 19th Jan

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 Interoperability Multifeatured Look and Feel Intelligence & decision making protocols Redundancy Planning Quality by Design (QbD), FICCI, 19th Jan

Quality Attributes Technology Enthusiasts VisionariesPragmatistsConservativesSkeptics Customers want Technology & Performance Customers want Solutions & Convenience Customers & User community Quality by Design (QbD), FICCI, 19th Jan

Quality Attributes Product Reliability & Obsolescence Bathtub Curve Obsolescence Proactive Obsolescence planning Reactive Obsolescence planning Quality by Design (QbD), FICCI, 19th Jan

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

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

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

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

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

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

Quality by Design (QbD), FICCI, 19th Jan