Difference between revisions of "Benchmark Template - Java track"

From CRV
Jump to: navigation, search
(Created page with "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 e...")
 
 
Line 1: Line 1:
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).
+
'''Name of benchmark''' Two or three sentences that describe the benchmark. These can mention the domain, scope or source or the benchmark. Or might suggest the purpose of the benchmark i.e. to demonstrate a certain feature. ''List of categories''
  
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).
+
== Benchmark Data ==
  
Please use the below template to create your benchmark Wiki pages.
+
=== The Trace Part ===
Do not modify the template.
+
  
----
+
Please upload your Java program to the server and include the necessary information (see rules document) here
  
[[ Benchmark Template - Java track ]]
+
=== The Property Part ===
  
----
+
See the rules for the necessary descriptions
  
 +
==== Informal Description ====
  
== Team 0 (ExampleName) ==
+
==== Demonstration Traces ====
  
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 [http://www.ficticiousAddress.com].
+
==== Formal Specification ====
  
* [[ Java Team0 Benchmark1 |  Benchmark 1 ]]
+
==== A FO-LTL Specification ====
  
 +
== Clarification Requests ==
  
== Team 1 (BeepBeep3) ==
+
This is a space where other teams can ask for clarifications and the submitting team can answer. When a team requests a clarification, the team should be mentioned in the request and the request timestamped. The team submitting the benchmark should ensure they watch this page so that they get notifications of questions.
 
+
== Team 2 (Larva) ==
+
 
+
== Team 3 (MarQ) ==
+

Latest revision as of 18:23, 20 May 2016

Name of benchmark Two or three sentences that describe the benchmark. These can mention the domain, scope or source or the benchmark. Or might suggest the purpose of the benchmark i.e. to demonstrate a certain feature. List of categories

Benchmark Data

The Trace Part

Please upload your Java program to the server and include the necessary information (see rules document) here

The Property Part

See the rules for the necessary descriptions

Informal Description

Demonstration Traces

Formal Specification

A FO-LTL Specification

Clarification Requests

This is a space where other teams can ask for clarifications and the submitting team can answer. When a team requests a clarification, the team should be mentioned in the request and the request timestamped. The team submitting the benchmark should ensure they watch this page so that they get notifications of questions.