in reply to Re: Re: All in one
in thread All in one

This is one reason why a good design layout is important, probably with UML. You can view the complete design at once and immediately see how each class relates to the others, all in one diagram. No need to jump between a bunch of files.
I wasn't talking about the situation where you proudly show your design in a conference room using a spiffy powerpoint presentation. I was more thinking of a situation where it's 11:45 PM, the bug needs to be fixed at 9 AM or the customer (who's 6 timezones ahead of you) will have to be paid damages and you are trying to figure out what piece of code is mangling your data incorrectly.

I've yet to see a UML diagram that indicates where the bugs are.

Abigail

Replies are listed 'Best First'.
Re: Re: All in one
by hardburn (Abbot) on Jan 13, 2004 at 15:10 UTC

    I wasn't talking about the situation where you proudly show your design in a conference room using a spiffy powerpoint presentation.

    Nor was I. I was addressing the point that heavy OO is hard to work through because the complete design is scattered throughout a large number of files. UML helps here because even a crappy design will at least show all the crap in one place, provided the code matches what is in that diagram.

    ----
    I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
    -- Schemer

    : () { :|:& };:

    Note: All code is untested, unless otherwise stated

[reply]
[d/l]

In Section Meditations