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

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

- Planning for reuse -- "chicken and egg" problem: projects must re-use specifications and designs, or they cannot hope to re-use code. Conversely, code must be specified and designed for re-use, or it will not be re used.

- Corporate base: basic frameworks and toolkits that are assumed by developers to exist, and to have quality similar to the vendor supplied system code:

  • must be re integratable, so that developers have a palette of options from which to choose, and

  • must be quality, or developers will quickly abandon them.

  • "Chicken and egg" revisited: most infrastructures "grow" into quality through diverse usage and subsequent changes/fixes, yet inferior infrastructures never get the use needed to improve.

- Inter-team needs are different than team needs. Searching for frameworks that are suitable for re-use dominates inter-team use, while integration support, for example, is not needed at all. Unfortunately, there is sometimes a second problem for multiple teams -- a corporate culture that tolerates the "NIH syndrome".

[ prev | top | next ]