Chapter 12 Prototyping and Testing Design of Biomedical Devices and Systems By Paul H. King Richard C. Fries.

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Chapter 11 Design, prototyping and construction 1.
Testing Relational Database
Andrea Maurino Web Service Design Methodology Batini, De Paoli, Maurino, Grega, Comerio WP2-WP3 Roma 24/11/2005.
Design, prototyping and construction
Testing Workflow Purpose
Lecture 8: Testing, Verification and Validation
SOFTWARE TESTING. Software Testing Principles Types of software tests Test planning Test Development Test Execution and Reporting Test tools and Methods.
Verification and Validation
Testing and Quality Assurance
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor Formal Methods in Software Engineering1.
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
Illinois Institute of Technology
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
Principle of Functional Verification Chapter 1~3 Presenter : Fu-Ching Yang.
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
Introduction to Computer Technology
What Exactly are the Techniques of Software Verification and Validation A Storehouse of Vast Knowledge on Software Testing.
Testing: Chapter 13 "You make it, I’ll break it".
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
Extreme Programming Software Development Written by Sanjay Kumar.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
Chapter 1: Introduction to Software Testing Software Testing
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.
CMSC 345 Fall 2000 Unit Testing. The testing process.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Based on D. Galin, and R. Patton.  According to D. Galin  Software quality assurance is:  A systematic, planned set of actions necessary to provide.
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
Safety Critical Systems 5 Testing T Safety Critical Systems.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Chapter 10 Verification and Validation of Simulation Models
Software Testing Process By: M. Muzaffar Hameed.
Prototyping. REVIEW : Why a prototype? Helps with: –Screen layouts and information display –Work flow, task design –Technical issues –Difficult, controversial,
Requirements Validation
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Software Testing and Quality Assurance 1. What is the objectives of Software Testing?
Software Development Life Cycle (SDLC)
Software Quality Assurance and Testing Fazal Rehman Shamil.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
SOFTWARE TESTING SOFTWARE TESTING Presented By, C.Jackulin Sugirtha-10mx15 R.Jeyaramar-10mx17K.Kanagalakshmi-10mx20J.A.Linda-10mx25P.B.Vahedha-10mx53.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Verification and Validation. Topics covered l Verification and validation planning l Program Testing l Software inspections.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
TQS - Teste e Qualidade de Software (Software Testing and Quality) Introduction To Software Testing Concepts João Pascoal.
Testing Multimedia Products
Verification & Validation
Object oriented system development life cycle
Chapter 10 Verification and Validation of Simulation Models
Chapter 11 Design, prototyping and construction 1.
Lecture 09:Software Testing
Verification and Validation Unit Testing
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Progression of Test Categories
Chapter 10 – Software Testing
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
Software Verification and Validation
Software Verification and Validation
Software Verification and Validation
OBJECTIVE QUALITY ASSURANCE TESTS TESTING STRATEGIES
Think about your view of QA
Software Reviews.
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

Chapter 12 Prototyping and Testing Design of Biomedical Devices and Systems By Paul H. King Richard C. Fries

Prototyping  Hardware Easily modified and extensible model of a system, including location of individual hardware components. Easily modified and extensible model of a system, including location of individual hardware components.  Software Easily modified and extensible model (representation, simulation or demonstration) of a planned software system, likely including its interface and input/ output functionality. Easily modified and extensible model (representation, simulation or demonstration) of a planned software system, likely including its interface and input/ output functionality.

Prototyping: Hardware  Present to customers for reaction to design Size correct for application? Size correct for application? Components placed for ease of use? Components placed for ease of use?  Wood, foam, cardboard

Prototyping: Software  Sometimes used to precede hardware models  Functioning example of final product  Determines if it satisfies the customer’s needs early in process  Allow testing of changes in processes prior to actual implementation of changes

A set of screens that provide a dynamic, computerized, working model of the planned system A throw-away prototype used to clarify project goals, to identify requirements, to examine alternative designs, or to investigate a large and complex system A prototype used to validate system specifications An iterative prototype that is progressively refined until it becomes the final system A prototype that models many features but with little detail; a horizontal slice of a system’s structure chart from the top down to a specific depth most useful in the early stages of design A prototype that models few features but with much detail; a vertical slice of a system’s structure chart from top to bottom; most useful in the later stages of design A prototype that is horizontal down to a particular level, then vertical below that point A prototype of the entire system; an expanded horizontal prototype that models a greater number of features and covers multiple levels of the system’s structure chart A prototype of a single usability-critical system component; a vertical prototype that is focused on one feature Prototypes: Types LLLLow-Fidelity HHHHigh-Fidelity EEEExploratory EEEExperimental OOOOperational HHHHorizontal VVVVertical DDDDiagonal GGGGlobal LLLLocal A set of drawings (e.g., storyboard) that provide a static, non-computerized, non-working mock-up of user interface for the planned system

Prototype: Process  Build low-fidelity prototype  Re-specify, re-design, re-evaluate  Freeze these specifications  Finish building the product

Testing  Subjecting a device to conditions that indicate its weaknesses, behavior characteristics, and modes of failure.  Ultimate goal: satisfied customer

Testing: 3 Basic Reasons  Basic Information Includes vendor evaluation, vendor comparison, and component limitability Includes vendor evaluation, vendor comparison, and component limitability  Verification Process of evaluating the products of a given phase to correctness and consistency with respect to the products and standards provided as input to that phase Process of evaluating the products of a given phase to correctness and consistency with respect to the products and standards provided as input to that phase  Validation Process of evaluating a product to ensure compliance with specified and implied requirements Process of evaluating a product to ensure compliance with specified and implied requirements

Testing: Defined  Establishing confidence that a device does what it is supposed to do  The process of operating a device with the intent of finding errors  Detecting specification errors and deviations from the specification  Verifying that a system satisfies its specified requirements or identifying differences between expected and actual results  The process of operating a device or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component

Test: Types  Verification  Validation  Black Box  White Box  Hardware Testing  Software Testing  Functional Testing  Robustness Testing  Stress Testing  Safety Testing  Regression Testing

Stress Testing  Designed to ascertain how the product reacts to a condition in which the amount or rate of data exceeds the amount or rate expected.  Help determine margin of safety that exists  Include Duration and Worst Case Scenario

Black Box  Verifies that the end-user requirements are met from the end-user’s point of view  Performed without any knowledge of internal structure  Tester is only interested in finding circumstances in which the device or program does not behave according to its specification.

Determining Sample Size and Test Length  MTBF (Mean Time Between Failure) Basic measure of reliability for repairable items Basic measure of reliability for repairable items  (sample size)(test time) = MTBF goal (X 2 α;2r+2 )/2  Example: Calculate the test time for a device that has an estimated MTBF of 20 per million hours if you have only fifteen units to test. List your assumptions.