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

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

- Must combine code from different developers in an orderly manner:

  • Compile time dependencies (subclasses) are automatic,

  • Run time dependencies (users of) are explicit, ordering is automatic,

  • Conflicts are identified and resolved,

  • Support tools: conflict resolvers, differencers, etc.

- Asynchronous -- integration should not force a code freeze; developers should be able to continue working during an integration.

- Democratic -- anyone should be able to integrate, at any time -- also known as "pre-integration" or "continuous integration". Developers can deliver their modules to the integrator with a high degree of confidence that they will work.

- Controlled -- an integrator manages the integration map, and can freeze it at will.

- Clearly defined and readily identifiable integration contents -- anyone should be able to tell at a glance what is in the build.

[ prev | top | next ]