1. www.vektrex.com - slide 1 1 ATML TestDescription Usage Report Vektrex Electronic Systems, Inc. www.vektrex.com June 2007

2. www.vektrex.com - slide 2 2 www.vektrex.com - slide 2 Vektrex Presentation Agenda High-level TestDescription usage case Test Strategy ->TestDescription fit Prototype Test Description Tool Discussion

3. www.vektrex.com - slide 3 3 www.vektrex.com - slide 3 Vektrex TestDescription as a Test Design Document? Problem: Data in current unstructured design docs (e.g. Test Strategy, Test Requirements) is not computer readable Proposed Solution: Use ATML TestDescription for design documentation Concerns: Fit – Is the Schema a good match for the data? Usability – Will data in this form be practical?

4. www.vektrex.com - slide 4 4 www.vektrex.com - slide 4 Vektrex TestStrategy -> TestDescription Mapping Fit Criteria Good – Element well associated with data Fair – Document info mapped to DocumentOther Poor – Field level data not in Schema Note: Could be contained in DocumentOther

5. www.vektrex.com - slide 5 5 www.vektrex.com - slide 5 Vektrex Good Mapped Elements UUT Information –Part #/Vendor –Performance Characteristics –Fault Data –Cooling requirements Document Information –Operation –Functional Description –Assembly Diagrams –Wiring Diagrams –Logic Diagrams –Block Diagrams –Parts List –FMECA –Testing Concept (Strategy)

6. www.vektrex.com - slide 6 6 www.vektrex.com - slide 6 Vektrex Fair Mapped Elements ATE Documentation ATE/UUT Compatibility Tradeoff Analysis Test Constraints Test Program Specification Non-Compliance Interface Hardware (IH) Preliminary Design Evaluation Glossary

7. www.vektrex.com - slide 7 7 www.vektrex.com - slide 7 Vektrex Poorly Mapped Elements Title Source information (Author, Organization) Document Date Program Information Legal Notices (Distribution, Destruction, Export) Revision History TPS References Keywords

8. www.vektrex.com - slide 8 8 www.vektrex.com - slide 8 Vektrex Test Strategy Cover Page

9. www.vektrex.com - slide 9 9 www.vektrex.com - slide 9 Vektrex Test Strategy to TestDescription Element Mapping Fit

10. www.vektrex.com - slide 10 10 www.vektrex.com - slide 10 Vektrex Extension Recommendations Poor Fit Elements –Short Term: Use TestDescription schema Extensions if needed –Long Term: Consider adding to future TestDescription & Common schemas Fair Fit Elements –Short Term: Other or Extension documentation nodes –Long Term: Consider as TestDescription schema doc nodes Good Fit Elements –No extensions needed

11. www.vektrex.com - slide 11 11 www.vektrex.com - slide 11 Vektrex Test Description Tool Prototype Goals: Capture test design process information Explore usability issues –Creation of new documentation –Transfer of existing documentation –Viewing and Document navigation –Review/Distribution Explore Interchange Issues

12. www.vektrex.com - slide 12 12 www.vektrex.com - slide 12 Vektrex Prototype TestDescription Tool TestDescription Data –Create –Navigate –Edit Existing –Save

13. www.vektrex.com - slide 13 13 www.vektrex.com - slide 13 Vektrex Prototype: UUT Performance Characteristics

14. www.vektrex.com - slide 14 14 www.vektrex.com - slide 14 Vektrex DetailedTestInfo: Tests

15. www.vektrex.com - slide 15 15 www.vektrex.com - slide 15 Vektrex DetailedTestInfo: Sequences

16. www.vektrex.com - slide 16 16 www.vektrex.com - slide 16 Vektrex Prototype TestDescription Tool (cont.) Diagram Data

17. www.vektrex.com - slide 17 17 www.vektrex.com - slide 17 Vektrex Embedded XML Diagram in RTF

18. www.vektrex.com - slide 18 18 www.vektrex.com - slide 18 Vektrex Discussion Does TestDescription make sense as an ATE Design Document? What extensions make sense and when? How should we handle embedded diagrams?