TestPlanTemplate測(cè)試計(jì)劃模板

1、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

2、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

3、 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

4、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. Refe

5、rences103.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 T

6、est 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 My

7、Courses 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 characteris

8、tics 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.htmPLEASE DELETE THIS PAGE FROM YOUR PLANP098XX Your Project NameTest Plans

9、& 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 pai

10、d 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

11、; 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

12、 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 Jan

13、e 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, pa

14、ss/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 s

15、pecifications 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 fea

16、ture 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 teste

17、d.Cut & Paste the team ' s specifications then add Pass/ Fail Criteria .If available, add Block Diagram indicating major inputs and outputs for final design.Engr. Spec. #ImportanceSourceSpecification (description)Unit of MeasureMarginal ValueIdealValueComments/StatusES1ES2EXAMPLE OF TABLEESn

18、1.4.6. Functions (hardware) and Features (software, customer needs)Note to Teams: A more detailed content which can be organized including some or all of the following. This portion of the test plan will grow and change as your design grows and changes so revisit periodically. More detail may occur

19、with theFinal Test Plan section.1. Tests (list or table): test # and name; test description.2. Traceability or verification matrix (table): specification # and brief description; system component embodying the spec (optional).1.4.7. Test Equipment available1.4.8. Test Equipment needed but not availa

20、ble1.4.9. Phases of TestingNote to Teams: Your testing needs may be a sequential. As an example, early testing in Senior Design I may be very informal for the purpose of evaluating the concept feasibility for the chosen technology. That is, component and/ or subsystem testing aids in gaining confide

21、nce in the chosen technology prior to full commitment. More advanced testing becomes more formal requiring good documentation. Define this plan within the team and then share with your Guide for potential feedback.Note: Refer to Dr. Reddy ' slides on MyCourses/ Content; Titled a Testing Life Cyc

22、le (slides). Component/ Device (wks 2-12)Standard functional components/ devices purchased from established manufacturers generally perform according to the data sheets. However, some critical components that are stressed to the limit in the design must be tested separately to confirm that th

23、e component can deliver the intended function under given operating conditions.List any critical components or devices requiring component testing.. Subsystem (wks 6-13)Each subsystem must be tested as a standalone unit by applying the possible input sequences and measuring the output respons

24、e and confirm with the expected response. Basically emulate the in-system inputs to conduct this experiment.In case of an embedded application, small test programs are run to test simple functions to perform at the outputs. A simple examples like switching on/off, latching, a relay, a motor.Define e

25、ach subsystem testing processes.. Integration (wks 11-15)This phase of the design is most critical.There are always problems when interfacing different modules/subsystems.Fit/ Form? Summation of tolerances? Verification of calculations and assumptionsFunction? Input/ Output, Signal Processing

26、? Synchronizing asynchronous signals? Fan-out problems? Noise problemsFor software, combine test programs you have developed for subsystem testing to communicate between the sub modules by adding one at a time to configure overall system.? Check the signal integrity and timing? Check the logic level

27、s and signal waveforms? On an oscilloscope. Reliability (wks 15-20)Note: If there is a specification, such as a drop test, out of range voltage or some other form of potentially destructive testing, discuss this with your Guide and Sponsor. As an example, this specification maybe waived depen

28、ding upon the specific customer needs.? Reliability is the most important characteristic? You can improve reliability by design.? However you may need special test procedure to characterize reliability.? Reliability test procedures are expensive.? Basically reliability test are conducted at elevated

29、 stress (electrical, tolerances, temperature .) levels. Sometimes they are invasive and destructive.. Customer Acceptance (wks 20-21)Finally you have to demonstrate the functionality and performance of the System to the customer.You have to develop a Test Plan to demonstrate the critical func

30、tional in a step-by- step fashion to prove that it satisfies customer (functional) specifications.1.5. Definitions; Important Terminology; Key Words1.5.1. Add here or remove as applicable.1.6. References1.6.1. Add here or remove as applicable.2. MSD II WKS 2-3: FINAL TEST PLANIntroduction: A brief d

31、escription as to how the team plans to implement their test process.Note to Teams: This Final Test Plan is due in Week 3 of Senior Design 2 and defines"how" the teamwill test and collect results. That is, list specific methodologies to verify systems specifications and any detailed sub-sys

32、tem specifications. This portion of the test plan may need to be revisited once testing begins as clarify of testing needs begins.2.1. Data Collection Plan; Sampling Plan2.1.1. Data Collection StructureList of tests to be performed (indicate test # and name, test description and so on).As an example

33、: Specification # and brief description, system component, test #, test date field (start/stop dates may be needed), pass/fail or test result field (verification), remarks or actions needed if test failed and signoff.. Component/ Device (wks 2-12). Relays. Air muscles. Po

34、tentiometers. Controls communication withthe relays. Controls communication withSolidWorks. Subsystem (wks 6-13).1. Elbow.2. SolidWorks Model. Integration (wks 11-15).1. Commands sent to and received by Solidworks.2. Feedback sent from Solidwor

35、ks, received by LabView.3. Commands sent to and received by relay board.4. Feedback sent from potentiometers and received by LabView.5. Joints can support each other ' s weight. Reliability (wks 15-20).1. Air muscle have already been tested for stress, just not

36、 at lengths needed for arm control..2. Test for experimental error and workings of total system through repeated positioning of elbow.0. Customer Acceptance (wks 20-21)2.1.2. Phases of Testing(If necessary, refer to the previously documented Test 1 Phase for needs). Again, focus on how

37、 the team plans to test.. Component. Subsystem. Integration. Reliability. Customer Acceptance2.1.3. Sampling TechniquesThe elbow will be moved to different positions and data will be recorded for actual position, force, pressure, time, and homing status.Test Date:

38、Test Start Time: Page _ of _Test No.Expected PositionActualPositionForcePressureTimeHoming AngleThe homing status will be determined by the homing operation, which consists of moving the elbow to the limits of its range of motion (0 or 150). Then data will be recorded for position, type of homing (n

39、ormal, hard, or soft), force, pressure, and time.Test Date: Test Start Time: Page _ of .Test No.Position00=normalCat. 110=soft, 01 Cat. 2l=hard, 11=failedForce | PressureTime2.1.4. Sample Size2.1.5. Reporting Problems; Corrective ActionIf the above testing cannot be performed, that will indicate a p

40、roblem with one or more components in the system.2.1.6. Add here or remove any other critical needs, as applicable.2.2. Measurement Capability, EquipmentIf there are measurement issues or techniques over and beyond RITs equipment, then either a, specific test devices test stands need to be designed

41、for the purpose of testing or test waiver.2.2.1. Add here.2.3. Test Conditions, Setup Instructions2.3.1. Add here or remove as applicable.2.4. Sponsor/Customer, Site Related, Requests / Considerations2.4.1. Add here or remove as applicable.2.5. Test Procedure, Work Breakdown Structure, ScheduleNote

42、to Team: Who is testing what? Why are you testing what you are testing? Are there interdependencies between subsystems (Block Diagram)? Can test equipment enable preliminary simulation of needed signals prior to integrating into the next level of completion?2.5.1. Add here or remove as applicable.2.

43、6. AssumptionsList here including reasons why or remove as applicable.2.6.1. Add here or remove as applicable.3. MSD II - WKS 3-10 DESIGN TEST VERIFICATIONNote to Teams: Populate the templates and test processes established inFinal Test PlanThese elements can be integrated or rearranged to match project characteristics or personal/team preferences.3.1. Test Results3.1.1. Component3.