Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.

Slides:



Advertisements
Similar presentations
CS 795 – Spring  “Software Systems are increasingly Situated in dynamic, mission critical settings ◦ Operational profile is dynamic, and depends.
Advertisements

Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Dependability ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
Term Paper OLOMOLA,Afolabi( ). Dependability Modellling.
1 Software Testing and Quality Assurance Lecture 36 – Software Quality Assurance.
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
Software Testing and Quality Assurance
1 Software Testing and Quality Assurance Lecture 37 – Software Quality Assurance.
SIM5102 Software Evaluation
The Infeasibility of Quantifying the Reliability of Life-Critical Real-Time Software.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 9 Title : Reliability Reading: I. Sommerville, Chap. 16, 17 and 18.
Testing Metrics Software Reliability
SENG521 (Fall SENG 521 Software Reliability & Testing Defining Necessary Reliability (Part 3b) Department of Electrical & Computer.
1 Software Testing and Quality Assurance Lecture 5 - Software Testing Techniques.
CIS 376 Bruce R. Maxim UM-Dearborn
Software Testing and QA Theory and Practice (Chapter 15: Software Reliability) © Naik & Tripathy 1 Software Testing and Quality Assurance Theory and Practice.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Critical Systems Specification 3 Formal Specification.
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
Software Integration and Documenting
Overview Software Quality Assurance Reliability and Availability
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Software Project Management
ECE355 Fall 2004Software Reliability1 ECE-355 Tutorial Jie Lian.
Chapter 22. Software Reliability Engineering (SRE)
SOFTWARE RELIABILITY MODELING
Software faults & reliability Presented by: Presented by: Pooja Jain Pooja Jain.
Software Reliability Growth. Three Questions Frequently Asked Just Prior to Release 1.Is this version of software ready for release (however “ready” is.
Software Reliability Categorising and specifying the reliability of software systems.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
ECE 355: Software Engineering
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 15 Software Reliability
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
Software Reliability SEG3202 N. El Kadri.
Performance Evaluation of Computer Systems Introduction
1 Performance Evaluation of Computer Systems and Networks Introduction, Outlines, Class Policy Instructor: A. Ghasemi Many thanks to Dr. Behzad Akbari.
Testing -- Part II. Testing The role of testing is to: w Locate errors that can then be fixed to produce a more reliable product w Design tests that systematically.
I/O Computer Organization II 1 Introduction I/O devices can be characterized by – Behavior: input, output, storage – Partner: human or machine – Data rate:
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Software Reliability (Lecture 13) Dr. R. Mall. Organization of this Lecture: $ Introduction. $ Reliability metrics $ Reliability growth modelling $ Statistical.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Statistical Software Quality Assurance Implies –Information about defects is collected and categorized –An attempt is made to trace each defect to underlying.
Reliability & Maintainability Engineering An Introduction Robert Brown Electrical & Computer Engineering Worcester Polytechnic Institute.
Software Testing and Quality Assurance Software Quality Assurance 1.
CS 505: Thu D. Nguyen Rutgers University, Spring CS 505: Computer Structures Fault Tolerance Thu D. Nguyen Spring 2005 Computer Science Rutgers.
Fault Tolerance Benchmarking. 2 Owerview What is Benchmarking? What is Dependability? What is Dependability Benchmarking? What is the relation between.
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 Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
SENG521 (Fall SENG 521 Software Reliability & Testing Overview of Software Reliability Engineering Department of Electrical.
Software Reliability [Kehandalan Perangkat Lunak] Catur Iswahyudi.
 Software reliability is the probability that software will work properly in a specified environment and for a given amount of time. Using the following.
1 Introduction to Engineering Spring 2007 Lecture 16: Reliability & Probability.
Slide (Ch.22) 1 Tian: Software Quality Engineering Software Quality Engineering: Testing, Quality Assurance, and Quantifiable Improvement Jeff Tian Chapter.
Software Metrics and Reliability
Hardware & Software Reliability
Fault Tolerance & Reliability CDA 5140 Spring 2006
Software Reliability Definition: The probability of failure-free operation of the software for a specified period of time in a specified environment.
Software Reliability PPT BY:Dr. R. Mall 7/5/2018.
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
Software Reliability: 2 Alternate Definitions
Software Reliability Models.
Software Test Termination
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
Critical Systems Validation
Software reliability CS 560 Lecture 15.
Software Reliability (Lecture 12)
Progression of Test Categories
System Testing.
CSC3050 – Computer Architecture
Presentation transcript:

Ch. 1

 High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle

 Measurement  Impacts of design, process, architecture & environment  Corrective/preventative techqniues

 A software system is an interacting set of software subsystems that is embedded in a computing environment that provides inputs to the software system and accepts service (outputs) from the software.

 Expected service (or "behavior") of a software system is a time-dependent sequence of outputs that ◦ agrees with the initial specification from which the software implementation has been derived (for the verification purpose), ◦ or which agrees with what system users have perceived the correct values to be (for the validation purpose).

 A failure occurs when the user perceives that the program ceases to deliver the expected service. ◦ The user may choose to identify several severity levels of failures, such as: catastrophic, major, and minor

 An outage is a special case of a failure that is defined as a loss or degradation of service to a customer for a period of time

 The cause of the failure or the internal error is said to be a fault. ◦ May be identified or hypothesized

 A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition.  Or, a human action that results in software containing a fault.

 Execution time (a.k.a., CPU time)  Calendar time  Clock time ◦ Ignores periods when the system is not running

 The cumulative failure function (also called the mean value function) denotes the average cumulative failures associated with each point of time. ◦ The failure intensity function represents the rate of change of the cumulative failure function.  The failure rate function (also called the rate of occurrence of failures) is defined as the probability that a failure per unit time occurs in the interval [t, t + M], given that a failure has not occurred before t.  The mean time to failure (MTTF) function represents the expected time that the next failure will be observed. ◦ (a.k.a MTBF, mean time between failures.)

 mean time to repair (MTTR) is the expected time until a system will be repaired after a failure is observed.  Availability is the probability that a system is available when needed. ◦ Availability = MTTF / (MTTR + MTTR)

 The operational profile of a system is defined as the set of operations that the software can execute along with the probability with which they will occur.

 Failure count (failures per time period)  Time between failures (interfailure time)  Conversion is possible ◦ TBF -> FC by counting ◦ FC ->TBF by random distribution over interval

 Estimation  Prediction

 specifies the general form of the dependence of the failure process on the principal factors that affect it: fault introduction, fault removal, and the operational environment ◦ Stochastic process ◦ Unlike hardware, sofware does not wear out  Reliability generally increases over time

 Fault prevention  Fault removal  Fault tolerance  Fault/failure forecasting