Q & QA1 Quality & Quality Assurance Advanced Software Engineering COM360 University Of Sunderland © 1999.

Slides:



Advertisements
Similar presentations
Basic Principles of GMP
Advertisements

1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
1 Continuing Evolution of U.S. Nuclear Quality Assurance Principles, Practices and Requirements PART II - A Tutorial August 2005 This document.
By Waqar Hussaian International Islamic university Islamabad.
Quality Assurance Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
Overview Lesson 10,11 - Software Quality Assurance
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
University of Sunderland CIFM03Lecture 1 1 Quality Management of IT CIFM03 Introduction.
Chapter 3 The Structure of the CMM
University of Sunderland CIFM03Lecture 5 1 QMS implementation and management CIFM03 Lecture 5.
Hazard Analysis and Critical Control Points
OHT 19.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Controlled documents and quality records Definitions and objectives.
University of Sunderland CIFM03Lecture 3 1 QMS / Standards CIFM03 Lecture 3.
Chapter 16 Software Quality Assurance
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
UNIT-II Chapter : Software Quality Assurance(SQA)
Introduction to Software Quality Assurance (SQA)
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Software Quality Assurance Activities
OHT 25.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality assurance organizational framework Top management’s quality.
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
S Q A.
Week 8 - Quality Management Learning Objectives You should be able to: §List and explain common principles of quality management (QM) §List, distinguish.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Creator: ACSession No: 15 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 Software Quality Assurance & Software Quality Control.
Georgia Institute of Technology CS 4320 Fall 2003.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
Exercise 1 Tor Stålhane IDI / NTNU. Intro The strength of ISO 9001 and many other standards is that they focus on “What shall be done” and leave “How.
ISO DOCUMENTATION. ISO Environmental Management Systems2 Lesson Learning Goals At the end of this lesson you should be able to:  Name.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Development of Quality1 Advanced Software Engineering COM360 University of Sunderland © 1998.
Integrated and Planned Enforcement of Environmental Law Phare Twinning Project CZ03/IB/EN/01 1 EMS as part of Integrated permitting and inspections Rob.
Unit 5 Operations Management Quality Improvement.
Module 2Slide 1 of 26 WHO - EDM Quality Management Basic Principles of GMP Part One.
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
SE513 Software Quality Assurance Lecture10: Documentation and Quality Records Control Galin, SQA from Theory to Education Limited.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(CSE) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
1 Definition Quality costs Plan Team Characteristics Implementation documentation Reviews & Audit Software Quality Assurance.
Personnel.
Integrated permitting and inspections
Quality Control and Quality Assurance
Software Quality Control and Quality Assurance: Introduction
Software Quality Assurance
Chapter 21 Software Quality Assurance
Management Concepts and Principles
UNIT-6 SOFTWARE QUALITY ASSURANCE
CMMI – Staged Representation
Chapter 21 Software Quality Assurance
What is software quality?
UNIT-6 SOFTWARE QUALITY ASSURANCE
SQA Role during Software Code and Unit Test Phase
Quality Measurable characteristic Cyclomatic complexity Cohesion
Software Quality Assurance
What is software quality?
Prepared and Presented By:- Abhishek Rautela
Chapter # 1 Overview of Software Quality Assurance
3. Software Quality Management
Presentation transcript:

Q & QA1 Quality & Quality Assurance Advanced Software Engineering COM360 University Of Sunderland © 1999

Q & QA2 Quality & Quality Assurance definitions cost motivation process & product QA tasks

Q & QA3 Definitions quality, software, quality assurance.

Q & QA4 Cost of Quality prevention costs appraisal costs failure costs external failure costs

Q & QA5 Development of Quality Deming, Juran, Ishikawa etc. TQM –kaizen –atarimae hinshitsu –kansei –miryokuteki hinshitsu

Q & QA6 Quality - People Motivation motivators and demotivators quality circles commitment - all levels

Q & QA7 Product vs Process good process = good product? process improvement (CMM)

Q & QA8 Quality Assurance (I) Juran defined quality assurance, in his Quality Control Handbook, as: the activity of providing to all concerned the evidence needed to establish confidence that the quality function is being performed adequately

Q & QA9 Quality Assurance (II) systematic activities providing evidence of fitness for purpose of the total software product

Q & QA10 QA activities - part 1 prepare a SQA plan participate in the definition of a project’s software development plan (and process model) review (software engineering) activities to verify compliance with defined software process

Q & QA11 QA activities - part 2 review selected (software) work products to verify compliance with specifications ensure deviations from defined activities and products are documented and handled according to defined procedures record any noncompliances regularly report to senior management

Q & QA12 Launching a SQA Programme initiate the programme identify the issues write the plan establish standards establish the function train and promote implement the plan evaluate the programme

Q & QA13 Humphrey says: The people responsible for the software projects are the only ones who can be responsible for quality. the role of SQA is to monitor the way these groups perform their responsibilities.

Q & QA14 Pitfalls: it is a mistake to think that SQA people (alone) can do anything about quality the existence of a SQA function does not ensure that the standard procedures are followed unless management periodically demonstrates its support for SQA, by following their recommendations, SQA will be ineffective unless line management requires that SQA tries to resolves their issues with project management before escalation, SQA and development will not work together effectively.