Visualizing software development effort

by John on July 23, 2008

Thomas Guest posted a great article today called Distorted Software that, among other things, points out the problem with software diagrams with big boxes and little arrows:

big boxes, little arrows

Most of the work will go into making the connections work.  In other words, the bulk of the work is in the little arrows, not the big boxes. He suggests a better diagram might look like this:

big arrows, little boxes

{ 3 trackbacks }

The Third Bit » Blog Archive » What My Students Have Learned This Summer
07.23.08 at 16:08
LEGO blocks and organ transplants — The Endeavour
02.03.11 at 11:12
interactive everything » Development Tips & Resources (Roundup #1)
12.21.11 at 13:49

{ 5 comments… read them below or add one }

1

Steve Holden 07.23.08 at 18:18

Interfaces are important. Who’d have thought it? ;-)

It’s a very good lesson to learn.

2

Thomas Guest 07.24.08 at 03:13

John, I’m pleased you liked the article. Thanks for the link and the summary.

Steve, you’re right, interfaces are important. My point is that our pictures don’t show just how important they are. :-)

3

Wyndekah 07.24.08 at 11:21

IDEF anyone

4

David Bolter 07.29.08 at 13:32

Nice post :)

For some reason reminds me of the Sensory Homunculus.
(pic: http://jwz.livejournal.com/422384.html)

5

Mark 02.04.11 at 17:32

This is spot on, and very well communicated. Kudos.

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>