RE: IPO Charts

Why not learn from I.B.M.?  They've been doing it for a little while
now.  Their approach is first to write the user manual before doing
anything else.  Then build everything from that user manual after that.
When the program does everything in the user manual it's a release.  Any
additional requests are maintenance work and maintenance releases.  By
the way, I.B.M. has the customer write their own user manual.


-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of RicksPlace
Sent: Thursday, July 22, 2010 10:10
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: IPO Charts

Back in my day we wrote input then process then outputs. We then
designed 
the code modules by starting with the outputs, then what we had for
inputs 
and finally the processing necessary to get from the inputs to the
outputs.
Rick USA
----- Original Message ----- 
From: "Jes" <theeternalkid@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Thursday, July 22, 2010 9:45 AM
Subject: IPO Charts


I know that when we think of IPO charts, we're supposed to write output,

processing, then input.
However, whenever I write pseudo code, I write input, processing, then 
output. Is this okay to do?
I'm still a toddler when it comes to programming.
Jes

__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
http://www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind

Other related posts: