On 24 Jan 2007, Silvia Pfeiffer <[EMAIL PROTECTED]> wrote: > >Ashley wrote: > > > >Afternoon Peoples, > > > >I've landed an opportunity that could lead me designing a system where > >the coders are overseas. I'm used to designing and coding myself, or > >at most one other. > > > >So I figured I needed a good modelling tool and asked a mate, who > >works in this space more than I, what UML tool he uses at the moment. > > > >His reply was, none. > > > >"UML is a productivity tool with a negative coefficient". > > > >So in the situation described what design tools are people using at > >the moment? Are they language dependant, or general tools? Has UML > >fallen out of favour?
I think the key thing is to get all the developers to really grok the purpose and underlying ideas of your system, so that they know how and where to apply their own talents. The right way to communicate that will depend on the project -- it might be a block diagram as Sylvia says, or UI mockups, or textual description. I can imagine UML being valuable where the domain model is complex and not easily explained or remembered -- such as business applications where there is a lot of arbitrary complexity that doesn't inherently "make sense" but does need to be precisely modelled. But I don't know if that's really what you have. So my 2c would be to consider: 1 What do I need to communicate to other developers to let them make good independent decisions? 2 What is a good way to represent that information? (is one of the uml models appropriate?) 3 What tools should I use to produce that? -- Martin _______________________________________________ coders mailing list [email protected] http://lists.slug.org.au/listinfo/coders
