Quality Management. Managing the quality of the design process and final

Similar documents
Subject : Computer Science. Paper : Software Quality Management. Module : Quality Management Activities Module No: CS/SQM/15

SWEN 256 Software Process & Project Management

Software Quality. A Definition of Quality. Definition of Software Quality. Definition of Implicit Requirements

International Standard ISO/IEC 9126

Introduction to Software Engineering

Process Improvement. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 28 Slide 1

Software Quality Management

WORK PLAN AND IV&V METHODOLOGY Information Technology - Independent Verification and Validation RFP No IVV-B

Introduction to Software Engineering

GAIA. GAIA Software Product Assurance Requirements for Subcontractors. Name and Function Date Signature 15/09/05 15/09/05 15/09/05 15/09/05 15/09/05

9. Verification, Validation, Testing

Quality Management Chapter 14

Business Context of ISO conform Internal Financial Control Assessment

BEGINNERS GUIDE TO ISO 9001 : 2000

QuEST Forum. TL 9000 Quality Management System. Requirements Handbook

Quick Guide: Independent Verification in TCO Certified

INTEGRATING ISO 9000 METHODOLOGIES WITH PROJECT QUALITY MANAGEMENT

ISO 9001 Quality Management Systems

GENERAL PRINCIPLES OF SOFTWARE VALIDATION

Mission Success in Complex Environments (MSCE)

General Guidance for Developing, Documenting, Implementing, Maintaining, and Auditing an SQF Quality System. Quality Code. SQF Quality Code, Edition 8

Response to Consultation on Governance Arrangements for the UPI: Key Criteria and Functions

JOURNAL OF OBJECT TECHNOLOGY

Supplier Quality Survey

EVANS CAPACITOR COMPANY

Quality Manual. Specification No.: Q Revision 07 Page 1 of 14

THE WAY TO A ZERO DEFECT BONDING PROCESS

Internal Audit Checklist System & Process Compliance Auditing

Desk Audit of. Based on Federal Transit Administration (FTA) Quality Assurance and Quality Control Guidelines FTA-IT

Guideline. Operational Risk Management. Category: Sound Business and Financial Practices. No: E-21 Date: June 2016

Developing Software Quality Plans a Ten Step Process. Phil Robinson Lonsdale Systems. Software Quality Plans. We all agree that you need one

SOLUTION BRIEF IDENTITY AND ACCESS GOVERNANCE. Simplify Identity Governance and Reduce Risk With the CA Identity Suite

The Value of Asset Management to an Organization

Supporting Credibility and Trust in Emerging Forms of External Reporting

Project Quality Management

TGL Fabrication Co.,Ltd. A growing Company with a growing reputation. Horizontal Load Testing & Inspection Services.

Guidelines for Testing Maturity

An Information Model for Software Quality Measurement with ISO Standards

Seminar 06 Chapter 5 - Part 1

Advantages and Disadvantages of. Independent Tests. Advantages. Disadvantages

Changes to the SCAMPI Methodology and How to Prepare for a SCAMPI Appraisal

Software Quality Metrics. Analyzing & Measuring Customer Satisfaction (Chapter 14)

Risk Management Beyond CMMI Level 5

Technische Universität München. Software Quality. Management. Dr. Stefan Wagner Technische Universität München. Garching 18 June 2010

Book Outline. Software Testing and Analysis: Process, Principles, and Techniques

An Overview of Software Reliability

reasons to invest in a CMMS

ENVIRONMENTAL AUDITING GUIDE TD 16/16/E

NATO REQUIREMENTS FOR DELIVERABLE QUALITY PLANS

QUESTIONS NUMBER ONE (Total marks 20) NUMBER TWO (Total marks 20) NUMBER THREE

Managing Successful Projects with PRINCE2

Fundamentals of Quality

3 PART THREE: WORK PLAN AND IV&V METHODOLOGY (SECTION 5.3.3)

ISO 9001 Telarc Q-Base

PRINCE2 - Quality Management Strategy

SOLAR KEYMARK SPECIFIC SCHEME RULES ANNEX E: FACTORY PRODUCTION CONTROL INFORMATIVE BASED ON ISO 9001 STANDARD COVERING THE PRODUCTION LINE

Position Statement. Product compliance and evidence of suitability

Building quality into the software from the. Keeping and. the software. software life cycle

Requirements Validation and Negotiation

Practical Risk Management: Framework and Methods

Software Quality Aspects of Software Project Management

University Alliance response to the consultation on the second Research Excellence Framework

Quality Management System Guidance. ISO 9001:2015 Clause-by-clause Interpretation

Audit Documentation. HKSA 230 Issued February Effective for audits of financial information for periods beginning on or after 15 June 2006

How Business Analysis Can Improve Sales and Marketing Outcomes

Correspondence Between ISO 13485:2016 and 21 CFR Part 820 QMS Requirements

Customer service. Chartered Institute of Internal Auditors. 26 October What is customer service? 1 Chartered Institute of Internal Auditors

INF 3121 Software Testing - Lecture 05. Test Management

Requirements Elicitation

Ingegneria del Software II academic year: Course Web-site: [

AS9003A QUALITY MANUAL

Aluminum Electrolytic Capacitors

Learning Resource. Babcock International Group. Allocate and monitor the progress of work.

ENERGY PERFORMANCE PROTOCOL QUALITY ASSURANCE SPECIFICATION

DEVELOP QUALITY CHARACTERISTICS BASED QUALITY EVALUATION PROCESS FOR READY TO USE SOFTWARE PRODUCTS

0 Introduction Test strategy A Test Strategy for single high-level test B Combined testing strategy for high-level tests...

Instruction Guide. Version 2.0 Last Updated: August Praesidium All rights reserved.

Standards Harmonization Process for Health IT

Translate stakeholder needs into strategy. Governance is about negotiating and deciding amongst different stakeholders value interests.

Quality Manual ISO 9001:2015 Quality Management System

Certified Human Resources Professional (CHRP) Competency Framework

Project Report Template (Sem 1)

IBM Watson Analytics Data Refinement. For Personal and Professional editions of Watson Analytics

BASICS OF SOFTWARE TESTING AND QUALITY ASSURANCE. Yvonne Enselman, CTAL

Certification of Safety-Critical Software Under DO-178C and DO-278A

To get the most out of this tutorial, it is good to have a basic understanding of the Software Development Life Cycle (SDLC).

V&V and QA throughout the M&S Life Cycle

ISTA & Package Testing

BEGINNER S GUIDE TO ISO 9001 : Quality Management System Requirements Explained

Frameworx 11 Certification Report Business Process Framework Release 9.0

Facilities Controller Job Description

UKPHR guidance on CPD scheme for practitioners

On the management of nonfunctional requirements

ISO 9000 Certification

Humantech Environmental Management System Manual

Requirements Engineering


WHITE PAPER. Food Safety, From Farm to Fork. A Best-Practice Approach to Implementing a Food Safety Management System

INTLCO Training Guide. We Train Professionals TM INTLCO All Rights Reserved

The Impact of Quality Culture on Quality Risk Management. FDA Perspective on Quality Culture; how it Impacts Risk Management

Transcription:

Quality Management Managing the quality of the design process and final product

Objectives To introduce the quality management process and key quality management activities To explain the role of standards in quality management To explain the concept of a design metric To explain how measurement may be used in assessing design quality

Topics covered Quality assurance and standards Quality planning Quality control Design measurement and metrics

Quality management Concerned with ensuring that the required level of quality is achieved in a product Involves defining appropriate quality standards and procedures and ensuring that these are followed Should aim to develop a quality culture where quality is seen as everyone s responsibility

What is quality? Quality, simplistically, means that a product should meet its specification This is problematical for engineering systems Contradictions between customer quality requirements eg. A trade off may exist between efficiency and reusability, etc. Engineering requirements are difficult to specify in an unambiguous way Product specifications are often inconsistent among different manufacturers

Quality management activities Quality assurance Establish organizational procedures and standards for quality Quality planning Select applicable procedures and standards for a particular project and modify these as required Quality control Ensure that procedures and standards are followed by the design team Quality management should be separate from project management to ensure independence

ISO 9000 International set of standards for quality management Applicable to a range of organizations from manufacturing to service industries ISO 9001 applicable to organizations which design, develop and maintain products ISO 9001 is a generic model of the quality process. Must be instantiated for each organization

ISO 9000 certification Quality standards and procedures should be documented in an organizational quality manual External body may certify that an organisation s quality manual conforms to ISO 9000 standards Customers are, increasingly, demanding that suppliers are ISO 9000 certified

ISO 9000 and quality management ISO 9000 quality models instantiated as Organization quality manual documents Organization quality process is used to develop instantiated as Project 1 quality plan Project 2 quality plan Project 3 quality plan Project quality management Supports

Quality assurance and standards Standards are the key to effective quality management They may be international, national, organizational or project standards Product standards define characteristics that all components should exhibit Process standards define how the product should be used, assembled, or manufactured

Importance of standards Encapsulation of best practice- avoids repetition of past mistakes Framework for quality assurance process - it involves checking standard compliance Provides continuity - new staff can understand the organisation by understanding the standards applied

Problems with standards Not seen as relevant and up-to-date by engineers Involve too much bureaucratic form filling Unsupported by software tools so tedious manual work is involved to maintain standards

Standards development Involve practitioners in development. Engineers should understand the rationale underlying a standard Detailed standards should have associated tool support. Excessive clerical work is the most significant complaint against standards Review standards and their usage regularly. Standards can quickly become outdated and this reduces their credibility amongst practitioners

Documentation standards process product (defined by organizations and company itself) Interchange Identification Structure Presentation Updates

Process and product quality The quality of a developed product is influenced by the quality of the production process

Practical process quality Define process standards such as how reviews should be conducted, configuration management, etc. Monitor the development process to ensure that standards are being followed Report on the process to project management

Quality planning A quality plan sets out the desired product qualities and how these are assessed and define the most significant quality attributes It should define the quality assessment process It should set out which organisational standards should be applied and, if necessary, define new standards

Quality plan structure Product introduction Product plans Process descriptions Quality goals Risks and risk management Quality plans should be short, succinct documents If they are too long, no-one will read them

Engineering quality attributes Safety Understandability Portability Security Testability Usability Reliability Adaptability Reusability Resilience Modularity Efficiency Robustness Complexity Learnability

Quality control Checking the product development process to ensure that procedures and standards are being followed Quality reviews

Quality reviews The principal method of validating the quality of a process or of a product Group examined part or all of a process or system and its documentation to find potential problems There are different types of review with different objectives Inspections for defect removal (product) Reviews for progress assessment(product and process) Quality reviews (product and standards)

Types of review Review type Principal purpose Design or program To detect detailed errors in the design or inspections code and to check whether standards have been followed. The review should be driven by a checklist of possible errors. Progress reviews To provide information for management about the overall progress of the project. This is both a process and a product review and is concerned with costs, plans and schedules. Quality reviews To carry out a technical analysis of product components or documentation to find faults or mismatches between the specification and the design, code or documentation. It may also be concerned with broader quality issues such as adherence to standards and other quality attributes.

Quality reviews A group of people carefully examine part or all of a system and its associated documentation. Code, designs, specifications, test plans, standards, etc. can all be reviewed. Documents may be 'signed off' at a review which signifies that progress to the next development stage has been approved by management.

Review functions Quality function - they are part of the general quality management process Project management function - they provide information for project managers Training and communication function - product knowledge is passed between development team members

Quality reviews Objective is the discovery of system defects and inconsistencies Any documents produced in the process may be reviewed Review teams should be relatively small and reviews should be fairly short Review should be recorded and records maintained

Engineering measurement and metrics Engineering measurement is concerned with deriving a numeric value for an attribute/property of a product or process Example Robustness:-sensitivity analysis Reliability-statistical analysis of samples (Weibull analysis)

Metrics assumptions The relationship exists between what we can measure and what we want to know This relationship has been formalized and validated It may be difficult to relate what can be measured to desirable quality attributes Theoretical assumptions Simulation model assumptions

The measurement process A measurement process may be part of a quality control process Data collected during this process should be maintained as an organizational resource Once a measurement database has been established, comparisons across projects become possible

Product measurement process Choose measurements to be made Analyse anomalous components Select components to be assessed Identify anomalous measurements Measure component characteristics

Data collection A metrics programme should be based on a set of product and process data Data should be collected immediately (not in retrospect) and, if possible, automatically

Data accuracy Don t collect unnecessary data The questions to be answered should be decided in advance and the required data identified Tell people why the data is being collected It should not be part of personnel evaluation Don t rely on memory Collect data when it is generated not after a project has finished

Measurement analysis It is not always obvious what data means Professional statisticians should be consulted if available Data analysis must take local circumstances into Data analysis must take local circumstances into account

Key points Quality assurance procedures should be documented in an organizational quality manual Engineering standards are an encapsulation of best practice Reviews are the most widely used approach for assessing product quality

Key points Measurement gathers information about both the process and the product Product quality metrics should be used to identify potentially problematical components