User Tools

Site Tools


modec

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
modec [2014/02/16 07:12]
yann
modec [2018/03/04 02:53] (current)
Line 18: Line 18:
 ===== MoDeC Usage ===== ===== MoDeC Usage =====
  
-Here are the two main steps to gather execution traces of some target Java program and identify occurrences of behavioural and creational design motifs in their MoDeC models.+Here are the three main steps to gather execution traces of some target Java program and identify occurrences of behavioural and creational design motifs in their MoDeC models.
  
-  ​Instrument the bytecode of the target Java program, using ''​modec.util.Instrumentor.instrumentClasses(String)'',​ see examples in ''​modec.util.Instrumentor.main(String[])''​. The input of the ''​instrumentClasses(String)''​ method is a file describing:+  ​Instrument the bytecode of the target Java program, using ''​modec.util.Instrumentor.instrumentClasses(String)'',​ see examples in ''​modec.util.Instrumentor.main(String[])''​. The input of the ''​instrumentClasses(String)''​ method is a file describing:
     * The path to the bytecodes of the classes of the target Java program;     * The path to the bytecodes of the classes of the target Java program;
     * The path to the folder where to store the instrumented bytecodes;     * The path to the folder where to store the instrumented bytecodes;
Line 27: Line 27:
     * The fully qualified name of the "​main"​ class of the target program;     * The fully qualified name of the "​main"​ class of the target program;
     * A list of paths to the Java class files to instrument, relative to the first path above.     * A list of paths to the Java class files to instrument, relative to the first path above.
-See for a complete example the file ''​MoDeC Bytecode Instrumentation Tests/Input Files/​Evaluation of ArgoUML v0.19.8.txt''​. The list of paths to the Java class files to instrument can be generated using ''​modec.tool.helper.ClassFileListGenerator.main(String[])''​. 
  
-  ​Execute the instrumented target program, using ''​modec.tool.Invoker.invokeMainClass(String)'',​ see examples in ''​modec.tool.Invoker.main(String[])''​. Running the invoker will launch the instrumented target program and open a new window. The new window shows only one button and a text field, used to insert marks (also called tags) at any user-chosen appropriate moment in the collected execution traces, for example before and after executing some particular feature.+  ​* See for a complete example the file ''​MoDeC Bytecode Instrumentation Tests/Input Files/​Evaluation of ArgoUML v0.19.8.txt''​. The list of paths to the Java class files to instrument can be generated using ''​modec.tool.helper.ClassFileListGenerator.main(String[])''​. 
 + 
 +  * Execute the instrumented target program, using ''​modec.tool.Invoker.invokeMainClass(String)'',​ see examples in ''​modec.tool.Invoker.main(String[])''​. Running the invoker will launch the instrumented target program and open a new window. The new window shows only one button and a text field, used to insert marks (also called tags) at any user-chosen appropriate moment in the collected execution traces, for example before and after executing some particular feature.
  
modec.1392534727.txt.gz · Last modified: 2018/03/04 02:53 (external edit)