How Do OOP Programmers Flowchart?

Lew Pitcher queries: "I recently attended a presentation of a code documentation tool that, among other things, produced a flowchart of the analyzed code. The vendor sells this one product for analyzing both mainframe code (COBOL, 390 Assembler, PL1, etc.) and 'distributed' code (C#, Java, C++, Smalltalk, etc). I haven't kept up with the 'modern' techniques (I prefer Nassi-Shneiderman charts, but I still have my flowcharting template), and wondered if modern 'OOP' programmers use flowcharts. If they don't, what is the preferred technique for diagramming an OOP program?"

Comments

Legos

[Anonymous Coward]

I build my objects out of legos.

Here's the new "modern technique"

[illuminatedwax]

Here's the new "modern technique"... pay attention, it gets complicated!

.______________.
| o o o o o o o|
| Outsource to |
| o .India. o o|
|______________|
o o o o|o o o o
o o o .V. o o o
o o o END o o o

--Stephen

Legos are for start-ups. Duplos are the future!!!

[Tactical Skyrider]

Legos?!?

HAH!

Your Legos are FAR inferior to my Duplos! *cough*ASP.NET*cough*

Re:OOP coders don't flowchart

[rmohr02]

Thanks
for
adding
your
own
newlines
it
make s
things
so
much
easier
to
read.

Re:If you've got any sense you don't use flowchart

[Moeses]

I prefer a less formal design approach best exemplified by this guiding principle:

A design should be written on the smallest napkin possible, but not smaller.

Anything more than that is gravy. ;)

Twisted technique...

[JediTrainer]

What if I outsourced my *own* job to India? Pay some guy $100 per month to do my job, so I can sit on my ass all day and play games? Heck - get two guys - it's time for a raise!

Anybody try it? Can it be done?