Javaanal: Java documentation assessment utility |
|||
PurposeThis utility lets a project manager assess how well-documented a suite of Java software is, and to repeat that assessment as often as required during the life of the project. Javaanal takes the output from Sun's JavaDoc utility (a set of HTML files) and analyses its content to tell you:
EnvironmentJavaanal is written in Visual Basic 5.0 (sorry), and will run under Win95 or 98, and possibly NT. Javaanal assumes that you have used JavaDoc (rather than any other Java documentation package) to generate a set of HTML files describing your project. JavaDoc works by stripping out specially-formatted comments from your code, and incorporating them into a framework that it creates from your code's structure. Javaanal will not work properly if your source code comments are in any language other than English, although it will work happily with both US and International English. UseTo use Javaanal, first get JavaDoc to generate your HTML files, then run Javaanal and give it the directory that holds the HTML files, and the name of an output file. Javaanal looks at the files in the directory, and picks out any that start with "Package" - it assumes that these are the top-level package descriptions for the packages in your project. It will then drill down into the other HTML files as it comes across references to them in the package documentation. Javaanal provides two forms of output - on the screen it will generate a single "percent complete" figure that indicates how your project is going. The output file is comma-delimited (suitable for opening with Excel, etc), and gives stats on each package as follows:
The number of words of documentation actually required are estimated by the utility at:
You can use the raw data given in the output file to calculate your own required documentation level if you wish. Javaanal estimates the number of actual words of documentation by taking the number of times common words are found ('commonwords' variable above), and multiplying by seven. Note that JavaDoc actually puts each source code comment into the HTML files twice; this is taken into account in Javaanal's calculations. InterpretationInterpreting this kind of broad measure requires considerable expertise, and it is usually necessary to have the actual content of the documentation sampled by a documentation expert. After all, Javaanal can't tell whether your documentation actually makes sense! However, broadly if your percentage of ideal documentation is low, it will mean that:
If you have any concerns about interpretation, please get in touch with us and we'll help you out. DisclaimerHCi makes no representation whatsoever about the effectiveness, usefulness, utility or safety of this product. It is provided free of charge, and HCi would like to warn potential users that this product may provide misleading, dangerous, and just plain silly results if not used by our staff experts. Download and use entirely at your own risk. Download it!Click here to download (about 1.5M) version 1.3 of the utility. To install, unzip it and then run setup.exe. |
||
|
back to ARTICLES Etc Contents to HCi Services |
||
HCi has formed a new consulting arm called Realisation. Click here to visit the Realisation site for further information.