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

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

- Integration must be so simple that any individual can do their own at any time. Two developers performing the same integration must obtain identical results.

- Browsing -- and re-using -- other team members' code must be as simple as browsing your own.

- Version history with immutability of past releases is required.

- What is "in the build" must be readily apparent at any given instant. A developer who has "lost synch" must be immediately aware of it.

- It must have stability -- protection of shared resources, such as base classes and mature frameworks, and enforcement of developer roles.

- Project documentation must be maintained with project code -- "comments are specifications", support for external documentation at the specification level.

- Branching and merging support on multiple levels -- method, class, sub-module, module, project.

[ prev | top | next ]