Developing real-time, automated testing for mission-critical programmable logic controller (PLC)-based control systems has been a challenge for many scientists and engineers. Some have elected to use customized software and hardware as a solution, but that can be expensive and time consuming to develop. Reginald Howard shows you a way to integrate a suite of commercially available, off-the-shelf tools and hardware to develop a scalable, Windows-based testing platform that's capable of performing an array of different tests including, but not limited to, black box, destructive, regression, and system security testing. He describes the use of the Jelinski-Morana statistical model for determining expected results from automated tests.

The Graybox Testing Methodology is used to test embedded systems. Recent studies have confirmed that the Graybox method can be applied in real-time using software executing on the target platform, expanding the capabilities of this method to include not only path coverage verification but also worst-cast/best-case path timing. Learn how this methodology has been applied in a real-time environment to validate mission-critical embedded software systems.

Increasing complexity and functionality of digital systems--coupled with time-to-market constraints--pose quality challenges. Strategies often include a mix of new development with the integration of pre-existing components from multiple sources. Ann Miller presents some of the software engineering and software management lessons learned from eight years on a large commercial satellite program, as well as several years on military satellite programs. This presentation focuses on the planned evolution of large-scale systems from the design and build of smaller components based on an end-to-end system backbone.

In testing utopia, all software products submitted for testing have thorough and comprehensive documentation describing how every program function should work. On planet Earth, however, test engineers usually have to make do under less-than-ideal circumstances. It's not uncommon for test engineers to be asked to verify the functionality of a critical legacy system which has no documented requirements whatsoever. While there are many reasons this can happen, the result is the same: You assume the role of an archeologist sifting through the layers of clues to reconstruct the specifications. Patricia Ensworth gives you instructions and tools so you'll be ready to roll up your sleeves and dig.