[Panel-devel] kicker is a mess

[Wade Olson]

True, which is why UML is considered one of many artifacts in software
development.

If you're an architect and the only thing you transfer to your
programmers: UML, or if you're a programmer and your designer only
gives you UML, something's grossly wrong.  The name alone tells you
what it is, otherwise it'd be UDL: Unified Description Language.

Like XML or similar, old-schoolers condemn it, marketers promote it as
a holy grail, and the pragmatic see it as just another tool and apply
it where userful.


On 10/3/05, Aaron J. Seigo <aseigo at kde.org> wrote:
> On Monday 03 October 2005 08:24, Wade Olson wrote:
> > To me, UML diagrams allow for both better introductions to new
> > participants, as well as helps more experienced people to refine the
> > code.
>
> high level code documentation is excellent for helping people do design
> recovery (which happens when learning a new code base as well as hunting for
> design issues 6 months after having written something yourself ;). i would
> welcome an ongoing documentation of plasma as it takes shape.
>
> on the flip side, i find uml nearly useless for describing new design concepts
> as it says everything about structure to me and almost nothing about the
> why's and wherefore's implied by the design. which is to say: what the person
> creating that design was thinking at the time.
>
> --
> Aaron J. Seigo
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
>
>
>