Mama Cass Elliot wrote:
> In netscape.public.mozilla.seamonkey the people heard Randall Parker say
> these wise words:
> Find out exactly what the End-user (or equivalent) is needing.
As if that were trivially easy.
> Determine the logical flow necessary to do what the End-user wants (flow
> charts).
Flow charts? I doubt the newer folks in the software development field
have even *seen* a flow chart. They're not particularly practical. The
last time I heard of someone trying to teach people to use flowcharts
was an introduction to BASIC class for TRS-80 machines around 1984.
> Write the simplest, and/or most efficient code necessary to achieve the
> logical flow within each individual section - and make sure that it
> actually works before moving onto another section. i.e. the code is 100%
> bugfree and 100% in conformity to the flow chart before moving to the next
> section.
In other words, do the impossible. Software provability is a field
that's been around for decades without really becoming all that workable
on a reasonable scale.
> Done this way, the programme should be achievable without having to do re-
> writes; and should be achievable within budget and within the time
> alocated.
The reason this approach has largely been abandoned is that it didn't
work very well.
--
http://www.classic-games.com/ http://www.indie-games.com/
Taxation Is Theft
