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?
Ideas and opinions great fully received.
Regards,
Ashley
I prefer doing design of the functionality of large systems with
diagrams of boxes and arrows, which have enough of a functionality
that an intelligent person understands what is behind it. The diagram
should always fit on one page. If you need to, drill into one box a
bit more. But the resolution to which you go down really depends on
how intelligent the people you work with are. A good overview design
can go a long way towards getting a persistent system. Try to make the
different components as independent of each other as possible, and it
will be easy to distribute the work.
As for data models - well, you make an initial design (maybe an
ER-Diagram) and then let it grow as you discover more needs.
Most of all: keep things simple - your developers will value it.
Cheers,
Silvia.
_______________________________________________
coders mailing list
[email protected]
http://lists.slug.org.au/listinfo/coders
