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

Individual-Group Needs Mismatch

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

- There is no distinction between system code, your own code, and the code of other developers -- "If it's in my image, I must have written it, unless I don't recognize it, and it seems to be dealing with the Furblesnotzer subsystem, then maybe it is Joe's code, except that Sue was working on Furblesnotzer last week, and then maybe..."

- A "module" of code is ad-hoc, undefined, carries no semantics. Generally, a class category or change set (ST 80) or a class (ST/V), but rarely a cohesive whole.

- No cross developer browsing -- except by convention, or by snooping around in other developers' home directories!

- Isolated change management -- you cannot effectively have multiple people working on one "module" (whatever that is).

- No documentation support -- "structured commentary" is not state of the art among CASE tools.

- Integration synchronization -- generally, project milestones require that everybody freeze development in order to proceed with integration.

[ prev | top | next ]