Vehicle barrier impact testing with Hybrid III dummies in a 1987 Ford Escort 5-door hatchback. Test report.

Mode of access: Internet.

UTCS - functional description - enhanced first generation software.

Federal Highway Administration, Implementation Division, Washington, D.C.

Random generation of sentences from context free and context sensitive phrase structure grammars.

Bibliography: p. 67.

On the generation of parsers for BNF grammars: an algorithm,

"Supported in part by the Dept. of Computer Science, University of Illinois ... and in part by the Advanced Research Projects Agency ... under Contract no. U.S. AF 30(602)4144."

Vehicle barrier impact testing with Hybrid III dummies in a 1987 Toyota Camry 4-door sedan. Test report.

Mode of access: Internet.

Vehicle barrier impact testing with Hybrid III dummies in a 1987 Chrysler Lebaron 2-door coupe. Test report.

Mode of access: Internet.

CSTA, U.S. Army Combat Systems Test Activity : testing for excellence.

Mode of access: Internet.

Operator and organizational maintenance manual (including repair parts and special tool lists) : test stand, automotive generator, alternator, and starter, floor mounted, 10 to 50-V, 500-amp, DC, and 25 to 50-V, 100 to 400 amp, AC, testing ranges, w/800 to 11,000-RPM ... (United Manufacturing Company model AGARTS type II, part number 7336-1 ....

"November 1966."

Employee drug testing : estimated cost to test all executive branch employees and new hires : report to the Chairman, Subcommittee on the Civil Service, Committee on Post Office and Civil Service, House of Representatives /

"GAO/GGD-92-99."

Viewpoint-based testing of concurrent components

The use of multiple partial viewpoints is recommended for specification. We believe they also can be useful for devising strategies for testing. In this paper, we use Object-Z to formally specify concurrent Java components from viewpoints based on the separation of application and synchronisation concerns inherent in Java monitors. We then use the Test-Template Framework on the Object-Z viewpoints to devise a strategy for testing the components. When combining the test templates for the different viewpoints we focus on the observable behaviour of the application to systematically derive a practical testing strategy. The Producer-Consumer and Readers-Writers problems are considered as case studies.

Integrating formal specification and software verification and validation

It is not surprising that students are unconvinced about the benefits of formal methods if we do not show them how these methods can be integrated with other activities in the software lifecycle. In this paper, we describe an approach to integrating formal specification with more traditional verification and validation techniques in a course that teaches formal specification and specification-based testing. This is accomplished through a series of assignments on a single software component that involves specifying the component in Object-Z, validating that specification using inspection and a specification animation tool, and then testing an implementation of the specification using test cases derived from the formal specification.

A case study in specification and implementation testing

Achieving consistency between a specification and its implementation is an important part of software development In previous work, we have presented a method and tool support for testing a formal specification using animation and then verifying an implementation of that specification. The method is based on a testgraph, which provides a partial model of the application under test. The testgraph is used in combination with an animator to generate test sequences for testing the formal specification. The same testgraph is used during testing to execute those same sequences on the implementation and to ensure that the implementation conforms to the specification. So far, the method and its tool support have been applied to software components that can be accessed through an application programmer interface (API). In this paper, we use an industrially-based case study to discuss the problems associated with applying the method to a software system with a graphical user interface (GUI). In particular, the lack of a standardised interface, as well as controllability and observability problems, make it difficult to automate the testing of the implementation. The method can still be applied, but the amount of testing that can be carried on the implementation is limited by the manual effort involved.

Testing java interrupts and timed waits

Testing concurrent software is difficult due to problems with inherent nondeterminism. In previous work, we have presented a method and tool support for the testing of concurrent Java components. In this paper, we extend that work by presenting and discussing techniques for testing Java thread interrupts and timed waits. Testing thread interrupts is important because every Java component that calls wait must have code dealing with these interrupts. For a component that uses interrupts and timed waits to provide its basic functionality, the ability to test these features is clearly even more important. We discuss the application of the techniques and tool support to one such component, which is a nontrivial implementation of the readers-writers problem.