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

A Sample Development Process

(This is a slide show. You really won't get 
anything out of it unless you have a graphical web browser with graphics turned 
To successfully exploit Smalltalk's strengths, you must:
  • Adopt an iterative development process. "Discovery" at multiple points is not well exploited by traditional procedures, which expect all discovery to take place months (or years) before delivery.
  • Incorporate feedback at every opportunity. Traditional procedures wait until the end of a project -- a year or more -- before incorporating lessons learned in the process.
  • Innovate new ways of measuring success. Traditional checkpoints such as "design complete" do not acknowledge that the design will change afterward.
  • Re define how old tasks are done. "Integration," "documentation," and "testing" should be a tightly integrated part of a developer's daily routine, not a phase of the project.
With some difficulty, an ideal Smalltalk process can be reconciled with established software development standards, such as ISO 9000 and Bellcore.

[ prev | top | next ]