Jomtool generates Java source code from OMT object-oriented design models. The user creates the analysis-level static object model in the OMTool diagramming tool, refines it with design-level information, and runs Jomtool to generate Java code from the model. Method bodies and file import lists are manually edited by the user directly in the files — all other semantics are derived from the OMTool model. The manually-edited parts are preserved through successive runs of Jomtool.

 [illegible screenshot of OMT model]

It turns out that there are design decisions and tricky details involved in deriving practical, "real-world" Java code from OMT models, and I had to address some of those those issues in the course of refining Jomtool for my own use.

I wrote Jomtool in Sep-1996, as a tool to help me implement some of my Master's thesis prototypes, which had big and hairy object models. At the time, all of the OMT-to-Java code generators (even those in CASE systems that cost five figures a seat) sucked, so I quickly hacked a useful one up in Emacs Lisp. I later used Jomtool in the development of SMORES, HtmlChewer, EdgeIRC, MyPaper, Butterfly, and MindShare.

The name "Jomtool" is derived from the name "Java" and the name of the "OMTtool" diagram editor (from the GE Advanced Concepts Center). The name suggests the catchy marketing slogan of "We be jom'n wit Jomtool, mon!"

You can download file jomtool.el. It was was released 22-Jul-2000 under the GNU Public License, just for grins.

© Copyright Neil Van Dyke      Contact