loading...
Practical Considerations in Protocol Verification: The E-2C Case Study
Las Vegas, Nevada October 18-October 22
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ICECCS.1999.802859Fifth IEEE International Conference o ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Yifei Dong, State University of New York at Stony Brook
Scott A. Smolka, State University of New York at Stony Brook
Eugene W. Stark, State University of New York at Stony Brook
Stephanie M. White, Long Island University
We report on our efforts to formally specify and verify a new protocol of the E-2C Hawkeye Early Warning Aircraft. The protocol, which is currently in test at Northrop Grumman, supports communication between a Mission Computer (MC) and three or more Tactical Workstations (TWSs), connected by a single-segment LAN. We modeled the protocol in the PROMELA specification language of the SPIN verification tool, and used SPIN to analyze a number of properties of the protocol. Our investigation revealed a race condition that can lead to a disconnect of an MC/TWS connection when there is one lost UDP data-gram and significant timing delays. Such delays are virtually impossible under normal E-2C operating conditions, but could be due to noise on the MC/TWS LAN. A simple modification was proposed that avoids the disconnect in many situations. Practical considerations, however, mandated that the protocol be left as is: shutting down a noisy connection and reinitializing the TWS, with minimal delay and loss of information to the operator, was deemed preferable to operating in degraded mode.
Citation:
Yifei Dong, Scott A. Smolka, Eugene W. Stark, Stephanie M. White, "Practical Considerations in Protocol Verification: The E-2C Case Study," iceccs, pp.153, Fifth IEEE International Conference on Engineering of Complex Computer Systems (ICECCS'99), 1999
Usage of this product signifies your acceptance of the Terms of Use.