John D. McGregor Session 3 Requirements V & V

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

Lecture 8: Testing, Verification and Validation
Testing and Quality Assurance
Chapter 4 Quality Assurance in Context
PERTEMUAN - 2 SOFTWARE QUALITY. OBJECTIVES After completing this chapter, you will be able to: ■ Define software, software quality and software quality.
INFORMATION TECHNOLOGIES SAFETY AND QUALITY THROUGH INFORMATION TECHNOLOGY WSRS Ulm – 20 Sept St. Ramberger / Th.Gruber 1 Experience Report: Error.
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.
Software Quality Assurance For Software Engineering && Architecture and Design.
Software Integration and Documenting
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing.
Software Reliability: The “Physics” of “Failure” SJSU ISE 297 Donald Kerns 7/31/00.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 24 Slide 1 Critical Systems Validation 1.
Software Testing Content Essence Terminology Classification –Unit, System … –BlackBox, WhiteBox Debugging IEEE Standards.
Implementation Considerations Yonglei Tao. Components of Coding Standards 2  File header  file location, version number, author, project, update history.
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 Defect Prevention Using Orthogonal Defect Classification
Instructor: Peter Clarke
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.
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.
Software Quality Assurance SE Software Quality Assurance What is “quality”?
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.
CPSC 372 John D. McGregor Module 2 Session 1 More on requirements and the Investment Decision.
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.
Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.
Safety-Critical Systems T Ilkka Herttua. Safety Context Diagram HUMANPROCESS SYSTEM - Hardware - Software - Operating Rules.
Software Testing and Quality Assurance Software Quality Assurance 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
Tutorial 1: Date: 19/09/2012 Instructor: Hanif Ullah
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
CS 505: Thu D. Nguyen Rutgers University, Spring CS 505: Computer Structures Fault Tolerance Thu D. Nguyen Spring 2005 Computer Science Rutgers.
Defect Classes and the defect repository
CPSC 873 John D. McGregor Session 9 Testing Vocabulary.
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.
SYSE 802 John D. McGregor Module 4 Session 0 Where are we?
CPSC 873 John D. McGregor Session 3 Requirements V & V.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
Failure Modes, Effects and Criticality Analysis
CPSC 875 John D. McGregor Design Concept C5. ALISA
CPSC 372 John D. McGregor Module 8 Session 1 Testing.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
John D. McGregor Session 9 Testing Vocabulary
John D. McGregor Session 9 Testing Vocabulary
Software Design Methodology
John D. McGregor Session 4 Requirements V & V - continued
John D. McGregor Session 9 Testing Vocabulary
Critical Systems Validation
Testing and Test-Driven Development CSC 4700 Software Engineering
What is software quality?
John D. McGregor Session 5 Error Modeling
Baisc Of Software Testing
Quality Management, Peer Review, & Architecture Review Board
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
John D. McGregor Session 16 Where are we? Where are we going?
What is software quality?
Presentation transcript:

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

Context Air pressure Hydraulic pressure wow redundant velocity Single point of failure

Software development industry Systems software Application software Middleware and tools Internet software

Variations on a central theme Revenue Expectations Significant impact on business model – Amazon Significant impact on operations – fly-by-wire Cost Custom - 75% or more of total product cost Off the shelf – 10% of total cost Cloud Computing Services Entertainment Software Electronic Commerce

Variations on a central theme - 2 Time to deliver DevOps Continuous engineering Lifetime Must last as long as accompanying product Until next upgrade

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 Upstream source of information Target of verification 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 into non-overlapping groups Originated in IBM

NASA’s ODC

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

http://www.cs.odu.edu/~mln/ltrs-pdfs/NASA-2003-cr212426.pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.197.5917&rep=rep1&type=pdf http://www.cs.cuhk.hk/~lyu/book/reliability/pdf/Chap_9.pdf http://itech.fgcu.edu/faculty/zalewski/CEN4935/Projects/SampleSRS-AirTrafficControl.html

Get the English description of the example Get the AADL model https://github.com/osate/examples/tree/master/ARP4761 Get the English description of the example https://wiki.sei.cmu.edu/aadl/index.php/ARP4761_-_Wheel_Brake_System_%28WBS%29_Example github https://wiki.sei.cmu.edu/aadl/index.php/ARP4761_-_Wheel_Brake_System_(WBS)_Example