Abstract
Testing large and complex software is an inherently difficult process that must be as systematic as possible to provide adequate reliability and quality assurance. This is particularly true for a complex real-time operating system in which an ad hoc testing approach would certainly fail to affirm the quality and correctness of the requirements specification, design, and implementation. We discuss applying systematic strategies to the testing of real-time operating system RTOS under development in the Esprit III project 8906 OMI/CLEAR.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
Full Text 
Sign-in/Register to access full text options
Sign-in/Register to access full text options 
Paper version not known
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
