From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_20,INVALID_DATE,
	MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!husc6!bbn!rochester!pt.cs.cmu.edu!sei!ajpo!rracine
From: rracine@ajpo.sei.cmu.edu (Roger Racine)
Newsgroups: comp.lang.ada
Subject: Re: Typing Ada
Message-ID: <343@ajpo.sei.cmu.edu>
Date: 25 May 88 13:30:21 GMT
References: <12400764147.13.RCONN@SIMTEL20> <25135.580491166@mbunix>
List-Id: <comp.lang.ada>

There are many different approaches to software design.  I do not believe
that everyone can use pictures to do this.  If you are at all familiar with
the "left hemisphere" and "right hemisphere" (of the brain) theories, this
should be obvious.  Many people have difficulty thinking in words.  They
think in pictures (Einstein was one of these types of people).  

Then there are those who think in words.  They have difficulty picturing
things in their minds.  

Personally, I like to write words (Ada) and look at pictures for an overview.
I have tried to use graphics packgaes to draw the design, and find myself
"translating" the words into the graphics.  It would have been much more
efficient if I had a tool to help me write the words AND a tool to translate
the words into pictures.

The same thing was true with flowcharts.  I always wrote the code first and
then wrote the flowcharts.  When I started working on the Space Shuttle
program and found them using a flowchart generator, I was thrilled.

I view the graphical design approaches as slightly better than flowcharting.
I still prefer to design in a word-oriented manner.