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

If you thought the last slide was unusual, things are about to really get strange! In the spiral prototyping activity:

  1. Classes and class specifications are identified from the partitioned/contracted subsystem. The class specifications are as formal as needed, and are stored in the class comment. The system browsers should be modified as needed to support special organizational specification needs, rather than require the developer to leave Smalltalk to use a different environment. These classes and class specifications identify subsystem collaborators, which may eventually be further broken down. (String is broken down as a Collection of Characters , for example.)

  2. Behavior is described in terms of method names and specifications, which are stored as method comments or in method associated storage.

  3. The specified classes and methods are implemented, producing functionality.

  4. Functionality is tested, integrated, and reviewed in parallel, producing possible corrections that are fed back to implementation, additional subsystem partitioning/contracting information, and collaboration/responsibility criticism, as well as a product.

  5. This activity is iterated as allowed by market opportunity windows and resource budgets.

* In many organizations (particularly those that build hardware!) "prototype" is a dirty word, recalling blobs of solder and loose wires on an engineer's bench. We use the term to mean an unfinished product; feel free to substitute your own term if your organization is uneasy with the concept of "prototype becoming product."

[ prev | top | next ]