Greetings, I'm currently using Visio with UML templates. One reason I like it is that it is not pedantic like Rose.. Doesn't try to do too much - allows you to use license to say what you mean and leave out unimportant detail. IMHO trying to be to detailed in UML forces design decisions that are best left until later. I believe architecture rarely should specify all the details - and coding is part of design.
I'm currently adopting a lightweight methodology - a bit like XP. However, I do significant analysis up-front then use XPs user story card, small releases and automated unit-testing. From a steering point-of-view small releases really focuses your mind on what's important and gets stuff in front of the customer asap to create a feedback loop. I'm using static class and object-interaction diagrams as needed to keep people (and myself) in the picture. Cheers, Jon Mark Johnson wrote: > UML diagram: http://husted.com/struts/resources/uml-jps.pdf > > free UML modelling software: http://gentleware.de > (poseidon community edition based on open source argouml, but more > user-friendly, good doc, etc; generates java class stubs from class > diagrams, and claims to 'reverse-engineer' class diagrams from source) > > -- > > Mark Johnson > [EMAIL PROTECTED] > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
