Quality Measurable characteristic Cyclomatic complexity Cohesion

Slides:



Advertisements
Similar presentations
1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Advertisements

More CMM Part Two : Details.
SOFTWARE Quality Management
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
Software Quality Assurance
Overview Lesson 10,11 - Software Quality Assurance
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
University of Sunderland CIFM03Lecture 1 1 Quality Management of IT CIFM03 Introduction.
Software Quality Assurance Instructor: Dr. Jerry Gao.
DATE: 28/11/2012 INSTRUCTOR: HANIF ULLAH Tutorial 7.
Chapter 16 Software Quality Assurance
Chapter 16 Software Quality Assurance
Overview Software Quality Software Quality and Quality Assurance
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
UNIT-II Chapter : Software Quality Assurance(SQA)
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Quality Assurance Activities
Cost of Quality - COQ MGMT-5060 Operations Management.
Software Quality Assurance
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Chapter 8 Software Quality Assurance
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.
CS3100 Software Project Management Week 26 - Quality Dr Tracy Hall.
S Q A.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
Software Project Management Lecture # 12. Outline Chapter 26 – Quality Management  What is Quality?  Meaning of Quality in Various Context  Software.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 Software Quality Assurance. 2 Quality Concepts - 1 Variation control is the heart of quality control Software engineers strive to control the – process.
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.
Software Quality assurance SQA – SWE 333
JAMINAN KUALITAS PERANGKAT LUNAK NUR CAHYO WIBOWO.
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.
Software reviews Cost impact of software defects Defect amplification model Review metrics and their use – Preparation effort (E p ), assessment effort.
Software Engineering Lecture 8: Quality Assurance.
Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 26 Quality Management Software Engineering: A Practitioner’s Approach, 6/e Chapter 26 Quality.
CS223: Software Engineering Lecture 36: Software Quality.
1 Definition Introduction and key stages Steps and standards used Plan Team Characteristics Implementation documentation Reviews & Audit Software Quality.
1 Definition Quality costs Plan Team Characteristics Implementation documentation Reviews & Audit Software Quality Assurance.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
Software Quality Control and Quality Assurance: Introduction
Software Quality Assurance
Software Quality Management
CIS 375 Bruce R. Maxim UM-Dearborn
Software Engineering (CSI 321)
CS223: Software Engineering
Software Quality Assurance
Software Verification and Validation
Software Project Management
SOFTWARE PROCESS AND PROJECT METRICS
Software Quality Assurance
Chapter 21 Software Quality Assurance
Quality Quality is “a characteristic or attribute of something.”
UNIT-6 SOFTWARE QUALITY ASSURANCE
Software Quality Assurance
Chapter 21 Software Quality Assurance
Chapter 26 Quality Management
UNIT-6 SOFTWARE QUALITY ASSURANCE
Error Tracking Defect removal efficiency DRE = E / (E+D)
Software Quality Assurance
Software Engineering I
Chapter 26 Quality Management
Chapter # 1 Overview of Software Quality Assurance
Software Engineering: A Practitioner’s Approach, 6/e Chapter 26 Quality Management copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For.
Quality Management By Prakash G Asnani
3. Software Quality Management
Presentation transcript:

Quality Measurable characteristic Cyclomatic complexity Cohesion Coupling Quality of design Requirements, specifications, and design Quality of conformance Implementation – if it follows the design then the resulting system meets its goals – conformance quality is high Are there any other issues? Glass User satisfaction = compliant product + good quality + delivery within budget and schedule DeMarco – “A product quality is a function of how much it changes the world for the better”

Recap

Software Engineering II Lecture 27 Fakhar Lodhi

Cost of quality Cost of prevention, appraisal, and failure Prevention Quality planning Formal technical reviews Test equipment Training Appraisal – includes activities to gain insight into the product condition In-process and inter-process inspection Testing

Failure cost Internal failure cost Rework Repair Failure mode analysis External failure cost Complaint resolution Product return and replacement Help-line support Warranty work Law suits Cost increases as we go from prevention to detection to internal failure to external failure

A case A total of 7053 hours were spent inspecting 200,000 lines of code with the result that 3112 potential defects were prevented. Assuming a programmer cost of $40 per hour, the total cost of preventing 3112 defects was $382,120, or roughly $91 per defect

Compare these numbers to the cost of defect removal once the product has been shipped to the customer. Suppose that there had been no inspections, and the programmers had been extra careful and only one defect one 1000 lines escaped into the product shipment. That would mean that 200 defects would still have to be fixed in the field. As an estimated cost of $25000 per fix, the cost would be $5 Million or approximately 18 times more expensive than the total cost of defect prevention Quality translates to cost savings and an improved bottom line.

Quality Control Variation control is the heart of quality control Resource and time estimation Test coverage Variation in number of bugs Variation in support From one project to another we want to minimize the predicted resources needed to complete a project and calendar time.

Quality Control Involves series of inspection, reviews, and tests Includes feedback loop Combination of measurement and feedback Combination of automated tools and manual interaction

SQA Activities Involves two different groups Software engineers who do the technical work SQA group who is responsible for QA planning, oversight, record keeping, analysis, and reporting

SQA Group Activities SQA Group develops an SQA plan for the project during project planning Plan is reviewed by all stake holders Plan includes the identification of: Evaluations to be performed Audits and reviewed to be performed Standards that are applicable to the project Procedures for error reporting and tracking Documents to be produced by the SQA group Amount of feedback provided to the software project team

SQA Group participates in the development of the project’s software process description The software team selects the process SQA reviews the process description for compliance with the organizational policies, internal software standards, externally imposed standards, and other parts of the software project plan

SQA Group reviews software engineering activities to verify compliance with the defined software process Identifies, documents, and tracks deviations from the process and verifies that the corrections have been made

SQA Group audits designated software work products to verify compliance with those defined as part of the software process Reviews selected work products, identifies, documents, and tracks deviations; verifies that corrections have been made; and reports the results of its work to the project manager

Ensures that deviations in software work and work products are documented and handled according to the documented procedures. Deviations may be encountered in the project plan, process description, applicable standards, or technical work products

Records any non-compliance and reports to senior management Non-compliant items are recorded and tracked until they are resolved. Coordinates the control and management of change and helps to collect and analyze software metrics