[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 Production 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.)

In the spiral software production activity:

  1. Developers, aided by marketing, again discover a conceptual basis for solving a problem, constrained by market requirements.

  2. Again, developers take a conceptual specification and develop the product, constrained by legacy systems and market opportunity windows. However, they have two additional outputs: components that can be applied to similar concepts, and discoveries that modify the concepts upon which they develop their product.

  3. In addition to assuring customer satisfaction, maintainers produce reusable test cases, and provide early and continuous feedback to the development activity.

Some interesting differences can be identi ed with this process:

  1. Multiple feedback loops catch problems as early in the process as they can be identified.

  2. Although not expressible in IDEF0 syntax, the feedback loops are negative feedback , meaning they tend to minimize the impact of the inputs, resources, and constraints. Negative feedback is a stabilizing influence.

  3. Waterfall feedback tends to be positive , or amplifying feedback, due to the long periods involved. For example, developers are ramped up on another project by the time defects come in from testing, so they divert resource to bug fixing, which subsequently reduces the quality of their present work, which increases the number of defects.

  4. Roles are shared: maintainers have a development responsibility, developers must understand at least some market needs.

Let's look at the spiral development activity in more detail.

[ prev | top | next ]