[hand with pencil]
Stuff For Sale
2004 Summer Tour
Class Stuff
Email Me
In The Press
Veggie Van Gogh

© 2002,

[this is simply a banner and menu bar]

Please patronize sponsors of this page!

Bytesmiths no longer is involved in software consulting. Maintenance of this web site is currently subsidised by unrelated business activities. Please pass the word to other interested folks, so I can continue to host this page!
Your site could be listed here, for as little as $12 per month! Go to Bytesmiths Press for details.

This site has been selected by PC Webopaedia as one of the best on this topic!
This site has been awarded a Links2Go Key Resource Award in the Smalltalk category!

[ prev | top | next ]

Waterfall Development Activity

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 

In the traditional waterfall process:

  1. The developers determine from the conceptual problem a set of requirements, that are specified, usually in the form of a prose document.

  2. The developers then propose a set of functions that the software product will perform, which is again expressed in a prose document.

  3. The developers then design a solution in general terms, which is expressed as a prose document.

  4. The developers implement the design, expressed as code that can be passed through a compiler to produce a machine executable product.

  5. The developers (or possibly testers) then test the code by exercising the machine executable representation of the code.

  6. If problems are discovered, they are reported to the developers, who fix the problems and integrate the fixes back into the code, which is once again tested.

  7. At some point, management (not formally identified here as a constraint!) decide the product is "good enough," and it is shipped.

We'll now take a more detailed look at the code implementation activity in the traditional waterfall development process.

[ prev | top | next ]