Specifying subtypes in Safety Critical Java programs
Abbreviated Journal Title
Concurr. Comput.-Pract. Exp.
SafeJML; Safety Critical Java (SCJ); Java Modeling Language (JML); timing behavior; duration; performance; WCET; SPECIFICATION; VERIFICATION; ABSTRACTION; Computer Science, Software Engineering; Computer Science, Theory &; Methods
Real-time and safety-critical code could benefit from the use of design patterns and frameworks that rely on subtyping and dynamic dispatch. However, modular reasoning about programs that use subtypes requires that each overriding method obeys the specifications of all methods that it overrides. For example, if method scale is specified in a supertype Vector2d to take at most 42ns to execute, then an override of scale cannot take more than 42ns to execute in any subtype, such as Vector3d. The problem is that subtype objects typically contain more information, such as the z coordinate in Vector3d, and thus their methods often require more time to execute than the methods they override. In this paper, we show how to specify timing constraints for subtypes in a way that both allows overriding subtype methods to have more time to execute and yet permits precise modular verification and checking of timing constraints. Our techniques allow object-oriented coding and design patterns based on subtype polymorphism to be used in real-time and safety-critical software. Copyright (c) 2012 John Wiley & Sons, Ltd.
Concurrency and Computation-Practice & Experience
"Specifying subtypes in Safety Critical Java programs" (2013). Faculty Bibliography 2010s. 4076.