i-node one

Sysloggin' one day at a time.

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Pages

  • How to Get the WWN of Sun FiberChannel HBAs for LUN Masking
  • Solaris jumpstart info
  • Solaris/SPARC memory errors

Recent Posts

  • SoBe Bottle Cap Qoute 21-Feb-2006
  • How to Identify Good Chocolate 20-Feb-2006

Categories

Archives

  • February 2006
  • January 2006
  • December 2005
  • November 2005
  • October 2005
  • September 2005
  • August 2005
  • July 2005
  • June 2005
  • May 2005
  • April 2005
  • February 2005
  • January 2005
  • December 2004
  • November 2004
  • October 2004
  • September 2004
  • August 2004

Powered by Genesis

You are here: Home / blogosphere / Spiral learning

Spiral learning

13-Feb-2005 By Jim

Iterations

Spirals show up everywhere from fractals to nautilus shells. Software developers know the spiral as iterative development–a model in stark (positive) contrast to the old linear waterfall model.

One huge problem with the waterfall model is that in its traditional form, it’s not based in reality. It assumes that it’s entirely possible for each stage to be done perfectly (and permanently) and then thrown over the fence (or cubicle wall) to the next group in the system. Nice theory, that. The guys doing the requirements finish their job and then, hey, they might as well all go on vacation. Their work is done. And so on down the line until the product is delivered to the users. The name itself (waterfall) describes the key limiting characteristic of the waterfall model–it’s one way only. Water doesn’t go back up.

User experience designers (especially with games) often use a spiral model to keep cycling the user through stages of interest/motivation, engagement, and payoff (I described the user experience spiral headrush.typepad.com…

Filed Under: blogosphere