This preview shows page 1. Sign up to view the full content.
Unformatted text preview: Prototyping and Testing
S. Laguette ME 128 Fall 2007 October 31, 2007
10/31/07 ME128 1 Prototyping and Testing
Prototyping Prototyping: Types Prototyping: Process Testing Test: Types Case Study 10/31/07 ME128 2 Prototyping
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.
10/31/07 ME128 3 Prototyping: Hardware
Present to customers for reaction to design
Size correct for application? Components placed for ease of use? Wood, foam, cardboard 10/31/07 ME128 4 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
10/31/07 ME128 5 Prototypes: Types
Low-Fidelity High-Fidelity Exploratory Experimental Operational Horizontal Vertical Diagonal Global Local
10/31/07 throw-away prototype that Aset of screens entire set of that models A Aprototypeofthatmodels the single Aprototypedrawings (e.g., A prototype that isto A prototype used Astoryboard)of project Anprototypeprototype that a iterativedynamic, used to a expanded provide clarify awith that system; features but with few features but system many an down toprovide validate systemrefined usability-critical horizontal is static,to identify a progressively goals, non-computerized, computerized, working horizontal prototype that much detail; aavertical littleit detail; a vertical specificationshorizontal component; particular the planned of level, until becomesto examine requirements, mock-up modela greater then ofsystem's non-working the final modelsofaa system's slice of slice prototype designs, or vertical below that the systeminterfaceis pointto alternativethat forand system chart from top user number of on onefrom the structure features structure chart feature focused investigate a large and covers multiple levels of toplanned system bottom; to a useful top down mostspecific complex system the the later stages of the in system's structure depth most useful in chart stages of design design early ME128 6 Prototype: Process
Build low-fidelity prototype Re-specify, re-design, re-evaluate Freeze these specifications Finish building the product 10/31/07 ME128 7 Testing
Subjecting a device to conditions that indicate its weaknesses, behavior characteristics, and modes of failure. Ultimate goal: satisfied customer 10/31/07 ME128 8 Testing: 3 Basic Reasons
Basic Information Verification
Includes vendor evaluation, vendor comparison, and component limitability 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 a product to ensure compliance with specified and implied requirements
ME128 9 Validation 10/31/07 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 10/31/07 ME128 10 Test: Types
Verification Validation Black Box White Box Hardware Testing Software Testing Functional Testing Robustness Testing Stress Testing Safety Testing Regression Testing 10/31/07 ME128 11 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
10/31/07 ME128 12 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.
10/31/07 ME128 13 References
Text, Reference King, P.H. and R.C. Fries, Design of Biomedical Devices and Systems, Marcel Dekker, 2003 King, P.H. lectures series 10/31/07 ME128 14 ...
View Full Document
- Fall '08