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

Cycle of Development

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

Cycle of development

  • Initial start or conversion to ENVY:
    • Decide on overall structure and create top level components, then sub-components.
    • Resolve name clashes; version all components.
  • After initial phase, loop as follows:
    • Make components editable.
    • Write code and integrate it with other team members. Test and bug-fix the public interface between collaborating classes. If desired, do informal code reviews.
    • Do full integration.
    • Test, fix bugs, reintegrate; repeat this step until satisfied.
    • Brand components with a version name, making them read only.
Length of cycle
  • Depends upon team size and application size
  • No shorter than two weeks recommended, except in code freeze, pre-release bug-fixing
  • Typical cycle length that worked well for teams of 6 to 12 developers was 4 weeks.
* This step includes putting third party code into ENVY. Once they are versioned, purchased components need not enter the "cycle" until the component vendor releases a new version.

[ prev | top | next ]