[hand with pencil]
Stuff For Sale
2004 Summer Tour
About
Blog
Class Stuff
Email Me
Events
Gallery
Home
In The Press
Newsletter
Services
Smalltalk
Veggie Van Gogh

Credits
© 2002,
Bytesmiths

[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 ]

Spiral 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 
on.)
Here, the spiral development activity departs radically from the proscribed waterfall analog. However, it is not so much revolutionary, as an acknowledgment of the way things really work in the waterfall world.
  1. Conceptual specifications are partitioned into functional subsystems capable of carrying out a workable portion of the concept. Conceptual specifications always deal in "what must be accomplished," never in "how we accomplish something." Such "conceptual integrity provides a major enabler for reuse." [Schultz 9406]
  2. Dependencies (or responsibilities) between these subsystems are identified, constrained by the minimum necessary integration with existing systems.
  3. Individual subsystems are prototyped in dependent order, so that each one can be tested independently.
  4. After prototyping, new concepts and possible subsystems are identified, which are rapidly accepted and are integrated, or rejected, or partially accepted.
  5. Certain commonality is identified (subject to time constraints), and the resulting subsystems are contracted into common reusable units.
Your organization's needs will most certainly impact this activity, although it is crucial in the long run to have a "contract" activity; this is the most likely source of re-usable solutions.
Let's look one step deeper into the spiral activity that actually produces the working code.

[ prev | top | next ]