We describe a prototype architecture for the runtime monitoring of Java programs using a smartphone. An online tool can produce an AspectJ file which, when woven with the program to be monitored and executed, instantiates a GUI window where XML events from the program's execution are output in the form of QR codes. A smartphone application, using the device's embedded camera, captures these codes and converts them back into events that are then fed to an onboard runtime monitor. We illustrate the feasibility of this approach by monitoring runtime properties on the execution of a video game by pointing a handheld Android phone at the game's screen and obtaining realtime feedback.

1. Portable Runtime Verification with
Smartphones and Optical Codes
Kim Lavoie, Corentin Leplongeon, Simon
Varvaressos, Sébastien Gaboury, Sylvain Hallé
Fonds de recherche
sur la nature
et les technologies
NSERC
CRSNG

2. instruction;
instruction;
instruction;
instruction;
instruction;
Program
Monitor

3. instruction;
instruction;
instruction;
instruction;
instruction;
Program
Monitor

4. instruction;
instruction;
instruction;
instruction;
instruction;
Program
Monitor X

5. instruction;
instruction;
instruction;
instruction;
instruction;
Program
Monitor X

6. instruction;
instruction;
instruction;
instruction;
instruction;
Program
vs.
Monitor X

7. instruction;
instruction;
instruction;
instruction;
instruction;
Program Monitor

8. instruction;
instruction;
instruction;
instruction;
instruction;
Program Monitor

9. instruction;
instruction;
instruction;
instruction;
?
instruction;
Program Monitor

10. instruction;
instruction;
instruction;
instruction;
instruction;
Program Monitor

11. Nintendo's R.O.B.

12. PROTOTYPES
void Mario.jump(int height);
<event>
<method>jump</method>
<x>
{this.getX();}
</x>
<y>
{this.getY();}
</y>
<height>
{height}
</height>
</event>

13. <event>
<method>
jump
</method>
<x>3</x>
<y>109</y>
<height>
221
</height>
</event>
<event>
<method>
haveShell
</method>
</event>
<event>
<method>
crouch
</method>
<x>201</x>
<y>56</y>
</event>
. . .
. . .

16. Code size (bytes)
Decoding rate

17. Decoding time
0.1 sec./frame
Monitoring time
0.005 sec./event