Difference between revisions of "Java track"

From CRV
Jump to: navigation, search
(Team 4 (Mufin))
(Team 2 (Larva))
Line 23: Line 23:
  
 
== Team 2 (Larva) ==
 
== Team 2 (Larva) ==
 +
LARVA is a runtime verification platform for runtime verification of critical systems. The language was specifically designed to allow a user to specify the security properties of a JAVA software system. Once these are specified in a text file, the compiler generates the necessary code in JAVA and AspectJ which verifies that the properties in the script are being adhered to during the execution of the system. The advantage of taking this approach is that the monitoring is done without manually changing any code in the system being monitored. Further information about the tool can be found at [http://www.cs.um.edu.mt/svrg/Tools/LARVA/].
  
 
== Team 3 (MarQ) ==
 
== Team 3 (MarQ) ==

Revision as of 14:38, 2 June 2016

The Java track is concerned with the monitoring of Java programs. A benchmark will consist of a Java program and a specification (see the rules document).

Please follow the example of Team 0 in how to organise your submission i.e. provide a team name and description and create a page per benchmark (named Track TeamX BenchmarkY).

Please use the below template to create your benchmark Wiki pages. Do not modify the template.


Benchmark Template - Java track



Team 0 (ExampleName)

The ExampleName tool works by magic dust and hope, utilising a new constant time algorithm for sorting. This paragraph is an example of the fact that there should be a few sentences written about the team and its tool. The tool is developed by John Lennon and Tintin. Further information about the tool can be found at [1].


Team 1 (BeepBeep3)

Team 2 (Larva)

LARVA is a runtime verification platform for runtime verification of critical systems. The language was specifically designed to allow a user to specify the security properties of a JAVA software system. Once these are specified in a text file, the compiler generates the necessary code in JAVA and AspectJ which verifies that the properties in the script are being adhered to during the execution of the system. The advantage of taking this approach is that the monitoring is done without manually changing any code in the system being monitored. Further information about the tool can be found at [2].

Team 3 (MarQ)

Team 4 (Mufin)