Version 0.0, Pre-Alpha
Home | Download | Source | FAQ | Contributors
Hosted on
A Javadoc doclet for relating source code sections to requirements and changes.
Jell is a Java development utility that may be used to track what is implemented where in Java source code. It is based on the Javadoc Doclet API, and uses a configurable tag to relate methods, inner classes, and variables to a list of reference numbers. The reference numbers are typically functional requirement numbers, defect tracking id's, change order numbers, or impact analysis id's.
The output is XML by default, but can be configured to apply an XML style sheet to produce a different format (html, rtf, etc.)
I got this idea when playing around with the doclet API around the JDK 1.2 timeframe. I've since used the Doclet API for a few tools, but this one is much less situation specific than the others. So here it is. I hope it proves to be somewhat handy to a few people.
Currently in pre-Alpha, but you can build from the source tree. Jell will go alpha by the middle of January, 2001.
Download the source code using the instructions here. Special thanks for the leader in Open Source Incubation, SourceForge. I mention them again because they host the CVS source tree for Jell.
The jell module is the main source tree, and a great starting point if you want to build from the source, or take a look at my shoddy work. The directory tree is laid out for your compiling pleasure. Simply download and install ANT, and run the build script as explained in the ReadMe.
The website module is where this and the other Jell web site pages are managed. It's really not worth looking at.
Before you try Jell out, you will need to gather a few things.
Jell runs on JDK 1.2 and above. If you need support for older versions, I could always use some more hands!
This is currently an early access edition, but it was too tempting to ignore. Download it from Sun's Java site, and follow the ReadMe that comes with the source to find out where to place it. I strongly suggest leaving this out of your classpath or jdk /lib/ext directory. It contains an XML parser that will cause a conflict error if you already have a parser on your classpath.
OK, so I lied. It's a command-line tool, so there aren't any real screen shots per se. I'll link to an example output file shortly. Once there is an html XSL and some other more user friendly outputs, I'll add these as well.
|
100% Java |
Jell may be used anywhere there is a jvm. |
|
Configurable |
Output may be relocated, tag can be renamed. |
|
XML |
Ah, yes, a buzz-word. Now we're getting somewhere. |
|
World-Friendly |
Ready for international messages, errors and the like. I'll continue to add other languages after the first release. |
Oh yes, and what would a requirement tracking tool be without Requirements? Well, sort of. These were actually written after the fact for this site, to demonstrate use of the tool. The reference table in the upcoming examples refers to these requirement and change numbers.
If you would like to help, right now the best thing would be to tell me if you find Jell useful. Also, I could use feedback on problems, recommended features, etc. But mostly feedback from anyone that uses the tool.
This is still mostly a one-man-band; however, I would like to thank Kevin Metzger for suggesting that Jell handle cross-referencing of requirements.
No need right now, I'm just getting started.
Last updated on $Date: 2002/01/07 04:56:22 $