CPSC 873 John D. McGregor Session 3 Requirements V & V.

Slides:



Advertisements
Similar presentations
Lecture 8: Testing, Verification and Validation
Advertisements

Testing and Quality Assurance
Software Failure: Reasons Incorrect, missing, impossible requirements * Requirement validation. Incorrect specification * Specification verification. Faulty.
Overview Lesson 10,11 - Software Quality Assurance
January 20, 2002ECEN5033 University of Colorado, Testing OO Software Part Two 1 Testing Object-Oriented Software – Testing Models Software Engineering.
1 Software Testing and Quality Assurance Lecture 37 – Software Quality Assurance.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 9 Title : Reliability Reading: I. Sommerville, Chap. 16, 17 and 18.
1 Software Testing Techniques CIS 375 Bruce R. Maxim UM-Dearborn.
CPSC 872 John D. McGregor Session 12 Software Design, cont’d.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Software Reliability: The “Physics” of “Failure” SJSU ISE 297 Donald Kerns 7/31/00.
Software Reliability Categorising and specifying the reliability of software systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 1.
Software Faults and Fault Injection Models --Raviteja Varanasi.
Software Testing Content Essence Terminology Classification –Unit, System … –BlackBox, WhiteBox Debugging IEEE Standards.
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
Chapter 8 – Software Testing Lecture 1 1Chapter 8 Software testing The bearing of a child takes nine months, no matter how many women are assigned. Many.
Software Defect Prevention Using Orthogonal Defect Classification
Instructor: Peter Clarke
Software Testing Course Shmuel Ur
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
1 Software Testing and Quality Assurance Lecture 33 – Software Quality Assurance.
Software Testing. What is Software Testing? Definition: 1.is an investigation conducted to provide stakeholders with information about the quality of.
DEFECTS By K.KARTHIKE. WHAT IS DEFECTS? Software bug, a failure of computer software to meet requirements Software bug The term defect and its relationship.
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Copyright John C. Knight SOFTWARE ENGINEERING FOR DEPENDABLE SYSTEMS John C. Knight Department of Computer Science University of Virginia.
Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.
Test vs. inspection Part 2 Tor Stålhane. Testing and inspection A short data analysis.
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Tutorial 1: Date: 19/09/2012 Instructor: Hanif Ullah
Learning Outcomes: Did You Learn What We Said You Should Learn? Russell Taylor.
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
Defect resolution  Defect logging  Defect tracking  Consistent defect interpretation and tracking  Timely defect reporting.
Software Reliabilty1 Software Reliability Advanced Software Engineering COM360 University of Sunderland © 1998.
CPSC 873 John D. McGregor Session 9 Testing Vocabulary.
1 Software Architecture in Practice Quality attributes (The amputated version)
Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.
CPSC 871 John D. McGregor Module 2 Session 2 Fault Analysis.
CPSC 871 John D. McGregor Module 1 Session 4 Requirements Review.
CPSC 871 John D. McGregor Module 8 Session 1 Testing.
CPSC 871 John D. McGregor Module 6 Session 2 Validation and Verification.
TESTING FUNDAMENTALS BY K.KARTHIKEYAN.
CPSC 871 John D. McGregor Module 8 Session 3 Assignment.
 Software Testing Software Testing  Characteristics of Testable Software Characteristics of Testable Software  A Testing Life Cycle A Testing Life.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Testing Integral part of the software development process.
CPSC 875 John D. McGregor Design Concept C5. ALISA
CPSC 372 John D. McGregor Module 8 Session 1 Testing.
Prepared by: Fatih Kızkun
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Testing Tutorial 7.
John D. McGregor Session 9 Testing Vocabulary
John D. McGregor Session 5 Domain Analysis, cont’d
John D. McGregor Session 3 Requirements V & V
Fault Tolerance In Operating System
John D. McGregor Session 9 Testing Vocabulary
Software Reliability: 2 Alternate Definitions
Critical Systems Validation
John D. McGregor Session 4 Requirements V & V - continued
John D. McGregor Session 9 Testing Vocabulary
Charakteristiky kvality
Critical Systems Validation
John D. McGregor Session 5 Error Modeling
Chapter 10 – Software Testing
Baisc Of Software Testing
Quality Management, Peer Review, & Architecture Review Board
Machine Protection PLC Based System Verification and Validation Plan
Presentation transcript:

CPSC 873 John D. McGregor Session 3 Requirements V & V

IEEE Definitions Mistake – a human action that produces an incorrect result. Fault [or Defect] – an incorrect step, process, or data definition in a program. Failure – the inability of a system or component to perform its required function within the specified performance requirement. Error – the difference between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition.

Context Target of verification Upstream source of information Impact on downstream

Level of integrity Usually on a scale from 1 – 4 Measure of how important the element is to health and safety Value is assigned based on the consequences of the action

Coverage The portion of the target of verification that is touched by the verification actions As the level of integrity increases the coverage must increase as well.

Orthogonal defect classification “types” of defects are categorized

One purpose

Defect types

Defect types - 2

Defect types - 3

Reliability growth curve

triggers What causes a fault to become an error and lead to a failure? Trigger – the idea of what initiated the cascade

Review Triggers Backward compatibility Lateral compatibility Design conformance Concurrency Operational semantics Documentation consistency/completeness Rare situation

Function test triggers Test coverage Test sequencing Test interaction Test variation Simple path coverage Combination path coverage

System test triggers Recovery/exception handling System startup and restart Workload stress/volume Hardware configuration and software configuration Normal mode

es/SRSFinalPDF.pdf es/SRSFinalPDF.pdf d?doi= &rep=rep1&type=pdf d?doi= &rep=rep1&type=pdf df/Chap_9.pdf df/Chap_9.pdf

assignment Due Sept 2 by 11:59pm ed to johnmc Use the requirements in the SRS Assign a level of integrity to each main numbered requirement; give a rationale for each value Think about each requirement and relate it to one of the defect categories. In other words what type of defect is likely to reside in the part of the system covered by the requirement.