Both the paradigm and the tool are being addressed in the ongoing work on HeNCE. The HeNCE graphs are restrictive. It may be possible to develop less restrictive graphs. The current graph constructs need to be evaluated as to their usefulness. It may be that some constructs are not needed and that new ones need to be developed. This can be addressed through implementing examples in the HeNCE paradigm. There are also interesting areas to explore with respect to the HeNCE tool. The editor could be extended to support hierarchy in the graphs. This would allow the programmer to create larger programs. The trace animation tool could also use these techniques when animating a program run. More debugging and profiling need to be added. Allowing breakpoints to be placed on the graph and parameter contents examined or altered at runtime would be useful. Multiple trace files could be displayed in a comparative manner, showing the relative times for executing a program on different virtual machines. It would also be useful to have the HeNCE tool coordinate the execution of source level debuggers over the configured machines. HeNCE could be extended so that during program execution, it takes into account the load and speed of the machines and network when mapping subroutines to machines. This information could be experimentally determined by the HeNCE tool.