A revised version of the DevEvent SDT requirements specification is now
available at:
<http://hackydev.ics.hawaii.edu/hackyDevSite/doc/DevEvent.html>
I've rewritten the introduction to more clearly indicate the scope of the DevEvent SDT,
revised the "Zorro" research project description, and most importantly, added a new
section to incorporate a submission by Lorin Hochstein on their research project at the
University of Maryland and how it would leverage this representation.
Please take a look and provide your comments. We can continue to revise and improve this
document even as we move into concrete implementation, as it will provide guidance on
improvements and future applications.
In terms of next steps, we are now initiating development activity related to DevEvent.
First up, of course, will be the hackySdt_DevEvent module, containing the basic
definition of DevEvent. Concurrently, we are working on a new module called
hackySensor_IdeFramework, which will provide a higher level platform for use by
Java-based IDEs along with an initial application of this framework to the IntelliJ IDE
(which will be encapsulated in the hackySensor_IntelliJ module). Thanks to Greg Bylenok
for contributing the code forming the basis for these modules. Once that is in place, we
will start migrating our other Java-based IDE sensors (JBuilder, Eclipse) to this new
framework, and introducing DevEvent sensor data collection at that time. There are some
interesting design issues that we will face as a result of the requirements document
regarding how and when a user can select which of the possible DevEvent 'families' of
events to generate.
Cheers,
Philip
