Wednesday, April 14, 2004
Team UML update

After working with Together for VS.Net and Enterprise Architect, our initial thoughts were that Together, or at least the description of the next version from Borland, was the product for us.  The modeling was very simple, and LiveSource was a very nice feature.  LiveSource keeps the source, and the diagram in sync at all times, kinda cool.  This was despite bugs in how the current version of Together works with VSS.  There may be work arounds, but it seemed to want to check the whole project out for every change.

So we start to contact Borland while we begin testing Enterprise Architect.  Having always been a fan of Borland, I was floored by my experience with them.  It was so difficult to talk to someone about the product.  Horribly difficult.  After leaving a number of voicemails and emails to various people I was referred to, we never got any of our serious questions answered.  But two people offered to sell it to me.  To their credit, I was contacted by a support engineer a week afterwards. 

After testing Enterprise Architect, though, it was easy to walk away from Together.  Within two hour we had the corporate trial installed, a model deployed to SQL Server, and a couple developers working in the designer.  The designer, although not as convenient then being directly in the IDE, easily makes up for it with its power and flexibility. 

EA allows users to lock the various objects within the model, and does it pretty well.  You can lock and unlock items through a context menu in the model explorer, much like vss integration in vs.net.  I'd like to see more visual notifications of which items are locked.  Sometimes you start to type in a new member, and realize the object is locked. 

In all, though, EA seems like a fantastic tool.  The learning curve is pretty minimal, and has an extremely robust feature set.  As far as team enabled editors, I didn't see anything that comes close to the feature set anywhere near the price point of EA.