RE: [Eclipsedotnet-developers] UML modeller

[Kunle O. <kun...@vi...>]

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

Still trying to find time to continue/complete my work on the 3.x
core/runtime.

> But the point of this mail is that I believe we should first=20
> start by doing some/a-lot-of schematics (I would opt for UML=20
> diagrams) for this, before we start developing code, so that=20
> we can catch/solve as many problems as possible in design=20
> time. So, what I wanted to know is: which UML modeller would=20
> you prefer to use (if any)?
>
> It would be preferable that everyone used the same modeller,=20
> so that the diagrams will always look the same for everyone.=20
> We _could_ export the diagrams to XMI and import them in=20
> another tool, but XMI diagram import/export nowadays is...=20
> well, crappy. :-( (Maybe when everyone starts following OMG's=20
> Diagram Interchange specification, this will change...). I=20
> believe it would also be preferable that the modeller used=20
> would be free/open-source (although I would place more focus=20
> on the "free" part), so that everyone could access it without=20
> any (legal) problems.

Some choices to consider would include:
- Poseidon for UML (commercial Java - grew out of ArgoUML, has free =
edition)
- ArgoUML (open source Java - used it many years ago, was a bit flaky)
- MonoUML (open source C# - never used it)
- VS 2005

Cheers,

Kunle