P09XXX Your Project NameTest Plans & Test ResultsBy: Team Member, Team Member, Team Member, Team MemberTable of contentsNote: Once you complete each of the three sections, right click on the table below and select Update Field to update the Table of Contents.)1. MSD I: WKS 8-10 PRELIMINARY TEST PLAN 31.1. Introduction; Overview; Summary; Purpose; History, etc31.2. Project Description; Sub-Systems/ Critical Components Being Tested31.3. Approval; Guide, Sponsor31.4. Test Strategy31.5. Definitions; Important Terminology; Key Words 51.6. References52. MSD II WKS 2-3: FINAL TEST PLAN 62.1. Data Collection Plan; Sampling Plan 62.2. Measurement Capability, Equipment 82.3. Test Conditions, Setup Instructions 82.4. Sponsor/Customer, Site Related, Requests / Considerations 82.5. Test Procedure, Work Breakdown Structure, Schedule 82.6. Assumptions 83. MSD II - WKS 3-10 DESIGN TEST VERIFICATION 93.1. Test Results93.2. Logistics and Documentation93.3. Definition of a Successful Test, Pass / Fail Criteria93.4. Contingencies/ Mitigation for Preliminary or Insufficient Results93.5. Analysis of Data Design Summary 93.6. Conclusion or Design Summary 93.7. Function/ Performance Reviews 93.8. References103.9. Appendices10General Notes to Teams:Please remove this page from your final test plan and test results.Not all categories in this template will apply to your project. Eliminate these categories that may not apply. Also, if there are key elements not covered, please add those items.This Test Document lists the processes and categories by which you are going to verify your final design. Fundamentally, the testing needed to prove your project meets specifications. These specifications may be categorized into features, functions and performance. MSD I Timeline and MSD II Timeline on MyCourses offers a typical example of the timing of testing. You may need to modify key milestones to apply to the specific demands of your project.The plan should be understandable by an engineer not familiar with the project.These elements can be integrated or rearranged to match project characteristics or personal/ team preferences. It may be more helpful to include traceability information (mapping of tests to specifications, customer needs, functions and features).References:http:/www.coleyconsulting.co.uk/testplan.htmhttp:/www.isixsigma.com/library/content/c040920a.aspPLEASE DELETE THIS PAGE FROM YOUR PLANP098XX Your Project NameTest Plans & Test Results1. MSD I: WKS 8-10 PRELIMINARY TEST PLANNote to Teams: The Preliminary Test Plan is due at the completion of Senior Design 1 (Week 10) and is inclusive of both the systems specifications and specifications within and between the major sub-systems. Particular attention should be paid to the interfaces between the sub-systems since different team members may be testing each. Since the chosen technologies and associated specifications are complete at the end of Senior Design 1, the test needs should be easily comprehended and documented below.1.1. Introduction; Overview; Summary; Purpose; History, etc.Note to Team: Select the appropriate title. As an example, cut & paste information for theOne PageSummary document and apply specifically to testing of the project specifications and features.1.1.1. Add here.1.2. Project Description; Sub-Systems/ Critical Components Being TestedNote to Team: If you have a high level block diagram depicting your major sub-systems, you may want to insert here.Pick the appropriate title and or add here or remove as applicable.1.2.1. Add here.1.3. Approval; Guide, SponsorApproved by:Team Members - List team members.Guide - Professor Jane DoeSponsor - NASA, Charlie Simons1.4. Test StrategyNote to Teams: The important components of the Test Plan and later Final Test Plan are:1.4.1. What you ll test (and what you won t test)1.4.2. How you ll test: equipment and materials needed, test configurations and procedures, pass/fail criteria1.4.3. Responsibilities and the approval process1.4.4. Risks and contingenciesNote to Teams: These elements can be integrated or rearranged to match project characteristics or personal/team preferences. It may be more helpful to include traceability information (mapping of tests to specifications and, if appropriate, to requirements and functions).1.4.5. Product Specifications, Block Diagram, and Pass/ Fail CriteriaNote to Teams: The structure of this test plan template is often consistent with the structure utilized for engineering specifications: for each specification or feature there is a defined test method or procedure, and pass/fail criteria to demonstrate compliance with the specification or feature. The team sdetailed Block Diagram developed during Concept Development and System Level Design is also an excellent tool to list the major interfaces to be tested.Cut & Paste the