Greetings, folks:

This Thursday (09.16.2004) at noon in POST 307, we will be reviewing 
the Command Invocation classes in the hackyStdExt module. To perform 
this review:

0. Install and/or update (a) the Eclipse Jupiter plug-in and (b) The 
Hackystat Jupiter sensor.
1. Update the hackyStdExt module from CVS.
2. Select "CommandInvocationReview1" as the ReviewID.

Please review the following files:
* CommandInvocationTrend.java
* TestCommandInvocationTrend.java
* CommandTrendActiveTime.java

I am particularly concerned about the following:

1. CommandInvocationTrend displays a chart with the invocation 
frequency of all commands defined in hackystat. Because there are so 
many commands, the chart is hard to read. How can I make this more 
readable (ex. display just the 10 most popular analyses or divide the 
analyses into groups)?

2. Is there a better way to test CommandInvocationTrend and similar 
analyses that use the command invocation logs which are local to each 
hackystat installation? Right now we are only checking that the table 
is retrieved with the correct labels. One option is to use the test 
framework to invoke certain commands a number of times, then check that 
the invocation frequency of these commands is at least that number.

3. I would like to see if there is any relationship between things like 
active time and coverage to command invocation frequency 
with "telemetry-style" charts. Are the two charts created in 
CommandTrendActiveTime an acceptable way to do this, or should I create 
telemetry streams?

-------------------------------------------------------------
Supplemental Links and Resources:

The Hackystat Code Review Guidelines:
* http://hackydev.ics.hawaii.edu/hackyDevSite/doc/Review.html

The Elements of Hacky Style:
* http://hackydev.ics.hawaii.edu/hackyDevSite/doc/EHS.html

Jupiter Code Review Tool documentation:
* http://csdl.ics.hawaii.edu/Tools/Jupiter/Core/doc/UsersGuide.html

Hackystat Jupiter Sensor documentation:
* 
<http://hackystat.ics.hawaii.edu/hackystat/controller?
Page=help&Subpage=install&Sensor=Eclipse-Jupiter>

Thanks for reviewing the code!

Melissa


Reply via email to