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

Re-Integration Needs

(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.)

- Re-integration is necessary for "spiral" development cycle. Traditional "waterfall" development has only one integration, thus it can be big, costly, and painful. To successfully increase the frequency of integration, it must be small, inexpensive, and painless -- and it must take place on a personal basis, not only via some guru integrator.

- Support "expand contract" development pattern. This means that removal of code is a necessary part of development. Using only vendor supplied tools, it is difficult or impossible to accurately and painlessly remove code from Smalltalk.

- Changes between arbitrary development cycles must be quickly and easily identified.

- Once changes have been identified, it must be quick and simple to select which of two versions to include in the new version.

- Differencing tools must function at all levels -- not simply the difference between two methods versions, but what methods are different in two class versions, etc.

[ prev | top | next ]