Beware of ArgoUML. It's broken in important ways (object ID's get lost, property pages don't work, it loses your drawings, etc. etc.). I used it for the beginnings of a project (twice, with 0.8 and 0.91) and stopped using it after it had lost my work (twice) and saved itself in a mode it wouldn't open. I was on the argouml mailing list for a while, and the developers there seem to be banging away on their different corners without getting a handle on underlying design problems. Their UML parser comes from a different group, and every time the UML parser changes, Argo breaks. I suspect that the design needs a serious re-thinking.
(I wrote a Perl script that will diagnose broken Object ID's in Argo output files, if anyone's interested)
If you want a resonably stable diagramming tool that outputs a parseable file format, you might look at TCM (though it only runs on Unix systems under X Windows).
My approach to this was to write my own UML editor in Squeak. If you have Squeak, you can get a taste of this editor by looking at the NK-ConnectorsDemo.056.pr project on Bob's Super Swiki (via the FIND button in the Squeak Project Navigator).
I am building this into a real product. I am, however, unclear as to exactly what support I could provide for Perl in it. Perhaps someone has some suggestions.
I have also built a Perl module for accessing Rational Rose models via its OLE Automation interface; if you're interested, contact me.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.