Thread: [Eclipsedotnet-developers] UML modeller

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I think it's time we start thinking about "upgrading"/evolving Eclipse.NET's
technological architecture (both in its plugin architecture, and maybe in
its UI layer as well). What I mean by this is that we should start thinking
about upgrading the current (and terrible) implementation.

But the point of this mail is that I believe we should first start by doing
some/a-lot-of schematics (I would opt for UML diagrams) for this, before we
start developing code, so that we can catch/solve as many problems as
possible in design time. So, what I wanted to know is: which UML modeller
would you prefer to use (if any)?

It would be preferable that everyone used the same modeller, so that the
diagrams will always look the same for everyone. We _could_ export the
diagrams to XMI and import them in another tool, but XMI diagram
import/export nowadays is... well, crappy. :-( (Maybe when everyone starts
following OMG's Diagram Interchange specification, this will change...).
I believe it would also be preferable that the modeller used would be
free/open-source (although I would place more focus on the "free" part), so
that everyone could access it without any (legal) problems.

Put your opinions in this mailing list, people.

Best regards,
JS

P.S.: I know everyone is horribly busy. I am too. But when I say that we
should start doing this, I only mean that maybe we should start putting some
spare time (if any is available) into this. Don't interpret this as pressure
to commit stuff ;-) .

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.0.0/266 - Release Date: 21-02-2006

Thread: [Eclipsedotnet-developers] UML modeller

eclipsedotnet-developers