Software Quality Assurance (SQA) Monitor the methods and standards used during the software development and verify their correct usage. What is Quality?

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
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.
ISO 9000 Quality Standards ISO 9000 describes quality assurance elements in generic terms that can be applied to any business. It treats an enterprise.
Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
Group 7 - Chapter 3 Steven Shroyer - Introduction, ad hoc, level 2 Xiao Jingshan - Levels 3 and 4 Dusting Marker - Level 5 and example companies Definintions.
More CMM Part Two : Details.
How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Quality Management System
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
School of Computing, Dublin Institute of Technology.
Capability Maturity Model (CMM) in SW design
Chapter 3 The Structure of the CMM
Configuration Management
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
ISO 9000 Certification ISO 9001 and ISO
Capability Maturity Model
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
SQA Work Procedures.
CEN 4935 Senior Software Engineering Project Joe Voelmle.
Ships in Service Training Material A-M CHAUVEL QMS Terms & Definitions 2009.
Objectives 4 Understand the ISO standards. Why are standards required? 4 Need standards to ensure that a term means the same for all 4 Need company standards.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
UNIT-II Chapter : Software Quality Assurance(SQA)
Introduction to Software Quality Assurance (SQA)
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
N By: Md Rezaul Huda Reza n
Software Quality Assurance Activities
Safety-Critical Systems 6 Safety and Quality Management and Certification T
Lec#3 Project Quality Management Ghazala Amin. 2 Quality Specialist-Job responsibility Responsibilities Reports monitoring and measurement of processes.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
SQA System Overview Chapter 4. Where we have been so far, Where we are going Where do software errors come from? What is quality? How can quality be measured?
S Q A.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
Quality Concepts within CMM and PMI G.C.Reddy
Georgia Institute of Technology CS 4320 Fall 2003.
@2002 Copyright, Itreya Technologies CMMI kick off July 2005.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Process: A Generic View
Michael Campe U.S. Army Aviation and Missile Command NDIA TID Technical Information Division Symposium Royal Sonesta Hotel, New Orleans, LA August 2003.
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…
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
Software Engineering (CSI 321) Software Process: A Generic View 1.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
Software Quality Control and Quality Assurance: Introduction
Software Configuration Management (SCM)
CS4311 Spring 2011 Process Improvement Dr
Software Quality Assurance (SQA)
UNIT V QUALITY SYSTEMS.
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Definitions.
A possible solution: Personal Software Process (PSP)
CMMI – Staged Representation
THE SOFTWARE PROCESS (revisited)
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Chapter # 8 Quality Management Standards
Capability Maturity Model
Software Reviews.
Presentation transcript:

Software Quality Assurance (SQA) Monitor the methods and standards used during the software development and verify their correct usage. What is Quality? - some definitions are: Client satisfaction No-Defects Fulfillment of all requirements

Objectives of the SQA Improve software quality through monitoring the process and the product. Make sure the standards and procedures are followed correctly and completely. Make sure that when procedures and standards are not being followed, that this is known to Project Management, and corrections are made.

SQA Plan 1. Purpose 2. Reference Documents 3. Administration 4. Documentation 5. Standards, Procedures and conventions 6. Revisions y Audits 7. Software Configuration Management 8. Report of problems and corrective actions taken 9. Tools, techniques and methods 10. Code control 11. Control of Media 12. Control of providers 13. Collection of records, maintenance and y retention

Quality Models CMM ISO-9000 SPICE

All models Agree on: Improvement has to be based on adjustments to the process and not on blaming people. Improvement has to be measured and its implementation constantly checked. Improvement requires constant investment, rewards and incentives. Improvement is a contínuous process. If the level insatisfaction is not high enough, then things will not change.

Capability Maturity Model (CMM) 1.Initial 2.Repeatable 3.Defined 4.Managed 5.Optimizing Disciplined process Standard and consistent process Predictable process Continuously improving process Not repeatable process

Key-aspects to improve the software Process Level 2: Requirement Administration Project Planning Plan follow-up Quality Control Configuration Management Level 3:Emphasis on organization processes Definition of processes Training Program Integral Administration Coordination between Groups Peer Revisions Level 4:Analysis and measurement of processes Quality Administration Level 5:Defect Prevention Technological Innovation Administration of process changes

ISO-9000 ISO : International Organization for Standartization Is a series of generic norms for the construction, operation and documentation of systems fro the administration of quality The 9000 series was elaborated in 1977 and first published in It contains 5 sets of norms: –ISO 9000 –ISO 9001 –ISO 9002 –ISO 9003 –ISO 9004

The ISO-9000 Norms ISO 9000 ISO 9001 ISO 9002 ISO 9003 ISO 9004 Model to assure quality of production and deployment Model to assure the quality of project development, production, installation and technical assistance Guidelines for the selection and use of the ISO-9000 Norm series. Model to guarantee quality in the inspection and final tests Guidelines for the quality administration

Quality System “It‘s the structure, the responsibilities, the procedures, the processes and the organization resources required to practice the administration of quality to comply with the objectives established in the Quality Policy.”(ISO 8402) “It‘s a mechanism that coordinates and controls the activities necessary to obtain the required quality in a product or service. It includes every element of an organization that is involved directly or indirectly with the development of the product or service”. (TickIT)

SPICE S oftware P rocess I mprovement & C apability d E termination It is an ISO project to develop an international standard for the Evaluation of the Software Process. Starts in counties participate.

SPICE Model Process Evaluation Determination of Capabilities Identifies the appropriate of Leads to Identifies changes to Leads to Is subject to Can originate Improvement of the Process