Thesis (Ph. D.)--University of Texas at Austin, 1999. / Includes bibliographical references (leaves 108-118). Available also in a digital version from Dissertation Abstracts.

Würzburg, Universität, Thesis (doctoral), 2000.

Thesis (M. Ed.)--Kutztown University of Pennsylvania, 2001. / Source: Masters Abstracts International, Volume: 45-06, page: 2797. Typescript. Abstract precedes thesis as preliminary leaves. Includes bibliographical references (leaves 41-43).

Thesis (Ph. D.)--University of Texas at Austin, 2002. / Vita. Includes bibliographical references. Available also from UMI Company.

Thesis (M.A.)--West Virginia University, 2003. / Title from document title page. Document formatted into pages; contains viii, 50 p. Includes abstract. Includes bibliographical references (p. 28-34).

The study attempted to assess whether test anxiety could be successfully managed using an expressive writing or meditation anxiety reduction technique, and whether these results would be maintained one week following the manipulation. Three administrations of the Test Anxiety Inventory were collected one week before, directly after, and one week following the assignment of participants to one of three study test conditions: meditation, expressive writing, and a control (narrative account of the previous day’s events). The students were given a 24-question GRE practice exam to simulate a high-stakes test environment. Repeated measures ANOVA and ANCOVA were performed to test the effectiveness of the intervention. Relationships between GPA, procrastination, test-preparedness, and test anxiety were examined, as were the correlations among depression, worry, and test anxiety. The results of the main and exploratory analyses did not indicate any significant differences across the three conditions. Suggestions for future research include incorporating a more robust version of the treatment, recruiting more participants reporting high anxiety at baseline, and utilizing test conditions in which the participants are more invested. / text

Huffman coding is a good method for statistically compressing test data with high compression rates. Unfortunately, the on-­‐chip decoder to decompress that encoded test data after it is loaded onto the chip may be too complex. With limited die area, the decoder complexity becomes a drawback. This makes Huffman coding not ideal for use in scan data compression. Selectively encoding test data using Huffman coding can provide similarly high compression rates while reducing the complexity of the decoder. A smaller and less complex decoder makes Alternate Huffman Coding a viable option for compressing and decompressing scan test data. / text

ITC/USA 2013 Conference Proceedings / The Forty-Ninth Annual International Telemetering Conference and Technical Exhibition / October 21-24, 2013 / Bally's Hotel & Convention Center, Las Vegas, NV / The desire to control an LRU and/or MIL-STD 1760 store via an independent 1553 stream on current weapon platforms created the need for the development of the BCT-302 1553 Test Bus Card. This solution solves the issues of integration without the need to perform an aircraft OFP change. The BCT- 302 is a customized MIL-STD-1553 card for use in Teletronics Technology Corporation, (TTC), Airborne Instrumentation Multiplexer (AIM) and High-Speed Avionics Data Acquisition Unit (HSAVDAU) products. The BCT-302 card consists of two redundant MIL-STD-1553 ports. Each port is independently configurable by the AIM/HSAVDAU host processor to function as a Bus Controller (BC), Remote Terminal (RT) or Bus Monitor (BM). The system is capable of cherry picking parameters from any 1553 bus and retransmitting assembled messages to a weapon and/or an LRU in a 1553 format. This paper describes the design requirements of the BCT card and how those requirements were met during an AIM-9X launch on an F-22.

Test Driven Development is a software technique which uses automated unit tests to drive software design and to force decoupling of dependencies. This report describes the pilot study that was conducted to understand Test Driven Development process and to evaluate its pros and cons before adopting it completely across the software team. The goal of the pilot study was to use TDD principles to build part of a real life software project - in particular, to completely implement 3 user stories - and to evaluate the resulting software. The main questions being discussed are - Is it feasible to adopt TDD in the development of a real life system with databases and UI? How easy is it to convert a user story into a set of unit tests? Can a set of unit tests adequately represent a user story or are requirements lost in translation? / text

published_or_final_version / Medical Sciences / Master / Master of Medical Sciences