Extend Developer Documentation

[arcanefoam]

Can you provide additional details on what is needed to provided a new benchmark project?

• The set of Java interfaces that must be implemented.
• Where and what in the gradle files (or elsewhere) has to be added to let the benchmark know there is a new tool to be tested?

Also, your generation documentation mentions the changes that have to be done... perhaps an example file with values and the explanation of the result obtained with those values would help a lot.

[szarnyasg]

I am pretty much slammed with tasks nowadays, mostly centered around a related project, the LDBC SNB benchmark, so there is little chance I can improve the docs now.

The recommended workflow to define a new tool is to copy an existing implementation, preferably one that is similar to the one you want to implement (e.g. another EMF tool), change the dependencies and rework the classes to suit the new tool. Then, add the tool to the BenchmarkScript.groovy scripts and execute a new run of the benchmark.