Click to edit Master text styles CSM 32152 Management of Software Project Software Quality Assurance Lecture - 03.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

Click to edit Master title style. Click to edit Master subtitle style.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Configuration Management
ANSI/ASQ E Overview Gary L. Johnson U.S. EPA
ACCOUNTING INFORMATION SYSTEMS
Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Chapter 9: Basic Information Systems Concepts. Definitions u A system is a set of interrelated components that must work together to achieve some common.
Stepan Potiyenko ISS Sr.SW Developer.
Total Quality Management
Systems Design. Analysis involves understanding and documenting user requirements in a clear and unambiguous way. It focuses on the business side and.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
How ISO 9001 Fits Into The Software World? Management of Software Projects and Personnel CIS 6516 March 6, 2006 Prepared by Olgu Yilmaz Swapna Mekala.
Chapter 24 - Quality Management
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Copyright © 2002 by Harcourt, Inc. All rights reserved. Topic 28 : Total Quality Management By Zhu Wenzhong.
Software Engineering EE323 Y.F. Fung Office: CF605 Consultation hours: Wednesday 6pm-7:30pm.
Introduction to Quality, Cost & Delivery
Software Quality Management
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
Systems Analysis and Design
1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
CLEANROOM SOFTWARE ENGINEERING.
Software Quality Assurance Lecture 4. Lecture Outline ISO ISO 9000 Series of Standards ISO 9001: 2000 Overview ISO 9001: 2008 ISO 9003: 2004 Overview.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
CSE 303 – Software Design and Architecture
Quality Control Project Management Unit Credit Value : 4 Essential
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Important informations
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
Creator: ACSession No: 15 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 Software Quality Assurance & Software Quality Control.
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
Chapter 7 Software Engineering Introduction to CS 1 st Semester, 2015 Sanghyun Park.
Quality Management.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
Cmpe 589 Spring 2006 Lecture 1. Software Quality  Definable and measurable Quality: –Conformance to requirements, non- conformance is a defect –Fitness.
1 Quality Attributes of Requirements Documents Lecture # 25.
KUFA UNIVERSITY Department of Computer Science 06/12/2015.
1 Software Quality Assurance Prof.M.D.Acharya. 2 Organization of this Lecture: zIntroduction Quality Engineering. zQuality control and Quality Assurance.
Software Engineering Lecture # 1.
Focus on design principles and on a process for doing design = To produce a precise, complete, high- quality foundation for product implementation.
Chapter 16 Managing costs and quality
OOAD UNIT V B RAVINDER REDDY PROFESSOR DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING.
Lecture#1 Introduction….Cont Software Quality Engineering Subject : 19(A/B) – {Assignment /Query}
IM111 – Lecture 111 Industrial & Management Engineering Department Industrial Relations IM 111 Dr Yehia Youssef.
Chapter – 8 Modern Management Concepts. BUSINESS PLAN In the Business Plan, the manager determines how the business will be established, what is the purpose.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
OPERATIONS & TECHNOLOGY MANAGEMENT (JMP 5023) MANAGING QUALITY & SIX SIGMA.
 The concept of Quality is very broad and can be defined in various way:  From the customer point of view: (Specification Quality) › Quality is the.
 System Requirement Specification and System Planning.
Software Quality Control and Quality Assurance: Introduction
Cmpe 589 Spring 2008 Lecture 1.
QUALITY ASSURANCE AND CONTROL
Software Verification and Validation
Software Verification and Validation
Software Verification and Validation
SEVERITY & PRIORITY RELATIONSHIP
Chapter 18 Maintaining Information Systems
Software Quality Engineering
The Systems Engineering Context
Quality Management Perfectqaservices.
Software life cycle models
Software Quality Assurance (Lecture 14)
Chapter # 8 Quality Management Standards
Software Maintenance Part1 Introduction. Outlines What Is Software Maintenance Purposes of Maintenance Why We Need It Maintenance Difficilties Some Tips.
Presentation transcript:

Click to edit Master text styles CSM Management of Software Project Software Quality Assurance Lecture - 03

Click to edit Master text styles Importance of Software Quality Increasing criticality of software The intangibility of software Accumulating errors during software development

Click to edit Master text styles Software Quality Quality product is defined in terms of its fitness of purpose. For software products, fitness of purpose is usually interpreted in terms of satisfaction of the requirements laid down in the SRS document The traditional concept of quality as “fitness of purpose” for software products is not wholly satisfactory.

Click to edit Master text styles Software Quality The modern view of a quality associates with a software product several quality factors such as the following: Portability Usability Reusability Correctness Maintainability

Click to edit Master text styles Software Quality Portability: A software product said to be portable, if it can be easily made to work in different OS environments, in different machines, with other software products, etc. Usability: A software product has good usability, if different categories of users (i.e. both expert and novice users) can easily invoke the functions of the product. Reusability: A software product has good reusability, if different modules of the product can easily be reused to develop new products.

Click to edit Master text styles Software Quality Correctness: A software product is correct, if different requirements as specified in the SRS document have been correctly implemented. Maintainability: A software product is maintainable, if errors can be easily corrected as and when they show up, new functions can be easily added to the product, and the functionalities of the product can be easily modified, etc.

Click to edit Master text styles Software Quality Management System A quality management system (often referred to as quality system) is the principal methodology used by organizations to ensure that the products they develop have the desired quality. A quality system consists of the following: Managerial Structure and Individual Responsibilities. Quality System Activities.

Click to edit Master text styles Managerial Structure and Individual Responsibilities A quality system is actually the responsibility of the organization as a whole. However, every organization has a separate quality department to perform several quality system activities. The quality system of an organization should have support of the top management. Without support for the quality system at a high level in a company, few members of staff will take the quality system seriously.

Click to edit Master text styles Quality System Activities Auditing of projects Review of the quality system Development of standards, procedures, and guidelines, etc. Production of reports for the top management summarizing the effectiveness of the quality system in the organization.

Click to edit Master text styles Evolution of quality management system The usual method to produce quality products was to inspect the finished products to eliminate defective products. Quality systems of organizations have undergone through four stages of evolution.

Click to edit Master text styles Evolution of quality management system The initial product inspection method gave way to quality control (QC). Quality control focuses not only on detecting the defective products and eliminating them but also on determining the causes behind the defects. Thus, quality control aims at correcting the causes of errors and not just rejecting the products.

Click to edit Master text styles Evolution of quality management system The next breakthrough in quality systems was the development of quality assurance principles. The basic premise of modern quality assurance is that if an organization’s processes are good and are followed rigorously, then the products are bound to be of good quality. The modern quality paradigm includes guidance for recognizing, defining, analyzing, and improving the production process.

Click to edit Master text styles Evolution of quality management system Total quality management (TQM) advocates that the process followed by an organization must be continuously improved through process measurements. TQM goes a step further than quality assurance and aims at continuous process improvement. TQM goes beyond documenting processes to optimizing them through redesign. A term related to TQM is Business Process Reengineering (BPR). BPR aims at reengineering the way business is carried out in an organization.

Thank you