Session 13 Page 11 ECE361 Engineering Practice Verification & Test Plan

Session 13 Page Days til the Competition The Fans Await…

Session 13 Page 33

Session 13 Page 44 Design Process Assures Design will meet Requirements Requirements Specification BrainstormingTrades Preliminary Design Requirements vs. Capabilities Detailed Design Review ImplementationTestingReporting Stage 1 Stage 1 – Problem Definition & Potential Solutions Stage 2 Stage 2 – Design Stage 3 Stage 3 – Verification Deliver = $$$ This process is part of what we call Systems Engineering

Session 13 Page 55 Verification Plan Prepares Your Design for Customer “Sell-Off” The PDS describes the requirements for your design The Design Review presents your design to the customer The next step is providing proof to the customer that your design meets requirements –This is provided in the form of results from the various types of verification exercises you undertake –These exercises are described in a verification plan, which includes the test plan

Session 13 Page 66 What is the Verification Plan? Each PDS requirement must be verified to the customer –Prove that the system meets the requirements, to customer’s satisfaction –Can mean renegotiation of requirements or contract… –All of this is presented in a Verification Plan for customer approval Document presented to customer outlining plans for verification of design’s performance against requirements –Includes verification matrix and test plan –Eventually includes test results

Session 13 Page 77 Verification Includes Testing Each requirement is verified using one of several methods, as approved by the customer –Inspection – e.g., the box shall be blue –Analysis – e.g. the lifetime shall be 5 years –Demonstration – e.g. the device shall make three shots within 5 seconds –Test – e.g. the signal level at the output of the filter shall be greater than 1 mV For those items which are to be verified by test –Each test and its success criteria are to be documented in a test plan –Results must be documented to verify performance against requirements

Session 13 Page 88 Verification Matrix is Implemented as a Table Each requirement (“shall”) is entered as a line in the table, with a number/letter ID designator –Every requirement should be included –These requirement IDs can be used in the test plan to better organize the information Columns identify requirement ID, requirement, verification method, and comments –Verification methods are analysis (A), demonstration (D), inspection (I), and test (T) This should be a single page table presented early in the verification plan

Session 13 Page 99 Test Plan Purpose: To define the tests, their order and importance, and evaluation criteria –A complete list of all requirements to be tested –Establish a sequential order for testing –Assign priority to each test –Define the criteria for successful test results –Provides data for design refinement Results: Detailed records of all test setups and test results –Record ALL the conditions and results of testing –Test results available to client/customer –Redesign of system to overcome failure

Session 13 Page 1010 Test Plan Details Detailed testing specifications –The robot will be placed at the far right corner of the starting area and read the first data card in no more than 5 seconds. –The robot will read every data or operator card correctly 99 out of 100 times. Lack of detail in results shows lack of planning –The robot will complete the course quickly (how quickly?) –The robot will read the data and operator cards correctly (every time?)

Session 13 Page 1111 Amateurs test until it works. Pros test until it no longer fails. - Unknown

Session 13 Page 1212 Team Assignment Continue prototype construction Prepare verification plan including –Design Update –Verification Matrix –Test Plan Complete list of tests to be performed Details of test conditions/apparatus Criteria for successful test results Schedule of testing Use report format, with cover memo initialed by team members

Session 13 Page 1313 ECE 361 Assignments TEAM ACTIVITY – Continue Construction and Test Work! TEAM ASSIGNMENT - Prepare verification plan using report format Due 24,25 October in class, one per team, hard copy