1 Software Quality Assurance COMP 4004 Notes Adapted from S. Som é, A. Williams.

Slides:



Advertisements
Similar presentations
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Advertisements

Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
The Chaos Report © The Standish Group 1995.
PERTEMUAN - 2 SOFTWARE QUALITY. OBJECTIVES After completing this chapter, you will be able to: ■ Define software, software quality and software quality.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
Chapter 8 Representing Information Digitally.
CHAPTER 1 Introduction to SQA.
©Ian Sommerville 2000CS 365 Ariane 5 launcher failureSlide 1 The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani University of Bozen- Bolzano Lesson 4 – Software Testing.
Overview Lesson 10,11 - Software Quality Assurance
1 SWE Introduction to Software Engineering Lecture 28 – Introduction to Software Testing.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
Modern Software Development Fawzi Emad Chau-Wen Tseng Department of Computer Science University of Maryland, College Park.
ARIANE 5 FAILURE ► BACKGROUND:- ► European space agency’s re-useable launch vehicle. ► Ariane-4 was a major success ► Ariane -5 was developed for the larger.
1 CMSC 132: Object-Oriented Programming II Software Development I Department of Computer Science University of Maryland, College Park.
Software Quality Assurance
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 13 CASE Tools and their Effect on Software Quality.
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
What is Software Quality? Chapter 2. Pressman's definition of "Software Quality" Conformance to explicitly stated functional and performance requirements,
 Software Software  Program vs Software Products Program vs Software Products  Software Characteristics Software Characteristics  Software Crisis.
©Ian Sommerville 2004Software Engineering Case Studies Slide 1 The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its.
Citadel Security Software Presents Are you Vulnerable? Bill Diamond Senior Security Engineer
System Software Integration Testing Mars Polar Lander Steven Ford SYSM /05/12.
USS Yorktown (1998) A crew member of the guided-missile cruiser USS Yorktown mistakenly entered a zero for a data value, which resulted in a division by.
Software Quality Assurance & Testing Mistake in coding is called error, Error found by tester is called defect, Defect accepted by development team then.
Achieving Better Reliability With Software Reliability Engineering Russel D’Souza Russel D’Souza.
Chapter 2 What is software quality ?. Outline What is software? Software errors, faults and failures Classification of the causes of software errors Software.
Managing Software Quality
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Information System Economics IT PROJECT MANAGEMENT.
The Ariane 5 Launcher Failure
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
SE513 Software Quality Control Lecture01: Introduction to Software Quality Assurance Galin, SQA from Theory to Education Limited.
Software is:  Computer programs, procedures, and possibly associated documentation and data relates to the operation of a computer system. [IEEE_Std_ ]
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
Introduction to Software Quality Assurance
Chapter 1 Introduction.
The Ariane 5 Launcher Failure June 4th 1996 Total failure of the Ariane 5 launcher on its maiden flight.
Introduction to Software Testing
INVARIANTS EEN 417 Fall When is a Design of a System “Correct”? A design is correct when it meets its specification (requirements) in its operating.
16 October Reminder Types of Testing: Purpose  Functional testing  Usability testing  Conformance testing  Performance testing  Acceptance.
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
Tutorial 1: Date: 19/09/2012 Instructor: Hanif Ullah
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
1 Chapter 1 The Product. 2 What is Software?  Pressman Instruction (computer programs) Data Structures Documents  Sommerville Software is computer programs.
Chapter 3: Software Project Management Metrics
Software Requirements and Design Khalid Ishaq
Testing software Team Software Development Project.
Software Defects.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(UIT), M.S(S.E) AAU Denmark Assistant Professor Department.
Software Engineering. Acknowledgement Charles Moen Sharon White Bun Yue.
CptS 401 Adam Carter. Final Review  Similar structure to the midterm: Multiple choice Matching (probably quotes from Daemon) Essay  Most questions will.
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.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
1 Chapter 1 The Software Quality Challenge. 2 The uniqueness of software quality assurance  DO you think that there is a bug-free software?  Can software.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
Lecture#1 Introduction….Cont Software Quality Engineering Subject : 19(A/B) – {Assignment /Query}
1 Chapter 1- Introduction How Bugs affect our lives What is a Bug? What software testers do?
CASE Tools and their Effect on Software Quality
Software Verification and Validation
SEVERITY & PRIORITY RELATIONSHIP
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
What is software quality?
What is software quality?
Software Quality Assurance 2015
© Oxford University Press All rights reserved.
Presentation transcript:

1 Software Quality Assurance COMP 4004 Notes Adapted from S. Som é, A. Williams

Introduction to Software Quality Assurance Left: The Ariane 501 rocket’s guidance computer software just threw an unchecked exception. [Image source: European Space Agency]

Objectives What is Software Quality? Why is Software Quality important? What is Software Quality Assurance ? Software Quality factors Elements of Software Quality Assurance Development and quality plans Process Maturity models

What is Software ? According to the IEEE Software is: –Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.

Software Errors, software faults and software failures Bug/defect/fault consequence of a human error. –Results in non-conformance to requirements. –Manifests as failure in running software. Software development process software fault software failure software error

Nine Causes of Software Errors Faulty requirements definition. Client-developer communication failures. Deliberate deviations from software requirements. Logical design errors. Coding errors. Non-compliance with documentation and coding instructions. Shortcomings of the testing process. User interface and procedure errors. Documentation errors.

When are defects introduced? The majority of defects are introduced in earlier phases. –Requirements are the top factor in a project’s success or failure. Phase% of defects % effort to fix Requirements5682 Design2713 Code71 Other104

Cost of fixing defects Relative cost of fixing defects –benchmark: cost at requirements phase = 1 Phase foundCost ratio Requirements1 Design3 – 5 Coding10 Unit / integration testing System / acceptance testing30 – 70 Production

What is Software Quality ? Conformance to requirements. Narrowest sense of software quality. –Lack of bugs. –Low defect rate (# of defects/size unit) –High reliability (number of failures per n hours of operation). –Mean Time To Failure (MTTF): probability of failure-free operation in a specified time.

What is Software Quality ? According to the IEEE: Software quality is: 1.The degree to which a system, component, or process meets specified requirements. 2.The degree to which a system, component, or process meets customer or user needs or expectations.

What is Software Quality ? According to Pressman: Software quality is: Conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.

Importance of Software Quality Software is a major component of computer systems (about 80% of the cost) – used for –Communication (e.g. phone system, system). –Health monitoring. –Transportation (e.g. automobile, aeronautics). –Economic exchanges (e.g. e-commerce). –Entertainment. –etc. Software defects are extremely costly in term of –money –reputation –loss of life

Importance of Software Quality Notable consequences of software errors: –1988 shooting down of Airbus 320 by the USS Vincennes - cryptic and misleading output displayed by tracking software. –1991 patriot missile failure - inaccurate calculation of time due to computer arithmetic errors. –London Ambulance Service Computer Aided Dispatch System – several deaths. –On June 3, 1980, the North American Aerospace Defense Command (NORAD) reported that the U.S. was under missile attack. –First operational launch attempt of the space shuttle, whose real-time operating software consists of about 500,000 lines of code, failed - synchronization problem among its flight-control computers. –9 hour breakdown of AT&T's long-distance telephone network - caused by an untested code patch.

Importance of Software Quality Ariane 5 explosion June 4, 1996 –First flight of the European Ariane 5 launcher crashed about 40 seconds after takeoff. –Cost was about half a billion dollars. –Explosion was the result of a software error: –Uncaught exception due to floating-point error: conversion from a 64-bit integer to a 16-bit signed integer applied to a larger than expected number. –Module was re-used without proper testing from Ariane 4. –Error was not supposed to happen with Ariane 4. –No exception handler.

Importance of Software Quality Mars Climate Orbiter - September 23, 1999 –Mars Climate Orbiter, disappeared as it began to orbit Mars. –Cost about $US 125-million. –Failure due to error in a transfer of information between a team in Colorado and a team in California. –One team used imperial units (e.g., inches, feet and pounds) while the other used metric units for a key spacecraft operation.

Importance of Software Quality Mars Polar Lander - December, 1999 –Mars Polar Lander, disappeared during landing on Mars. –Failure most likely due to unexpected setting of a single data bit. –Defect not caught by testing. –Independent teams tested separate aspects.

Importance of Software Quality Internet viruses and worms –Blaster worm (US$ 525 million) –Sobig.F (US$ 500 million – 1 billion) Exploit well known software vulnerabilities –Software developers do not devote enough effort to applying lessons learned about the causes of vulnerabilities. –Same types of vulnerabilities continue to be seen in newer versions of products that were in earlier versions. Usability problems

Importance of Software Quality Monetary impact of poor software quality (Standish group ) 175,000 software projects/year - Average Cost per project –Large companies - $US 2,322,000 –Medium companies - $US 1,331,000 –Small companies - $US 434, % of projects canceled before completed. –cost $81 billion

Importance of Software Quality 52.7% of projects exceed their budget - costing 189% of original estimates. –cost $59 billion 16.2% of software projects completed on-time and on-budget (9% for larger companies). Large companies - delivered systems have approximately only 42% of originally-proposed features and functions. 78.4% of smaller companies projects get deployed with at least 74.2% of their original features and functions.