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

Quality Assurance

(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.)
- Other project managers are suspicious about changing established procedures, and the quality of the result is where they most often express their discomfort. This must be pre-empted with an aggressive and effective quality plan, tightly integrated into the OO development process.
- System-level testing should be easier if a continuous-testing process is adopted. If a separate testing group is customary, train them in Smalltalk so they can better characterize problem reports.
- If design documentation is maintained in the repository with the code, it should be relatively simple to surpass previous design documentation quality. Documentation is updated continuously, as the design and code change.
- Continuous testing takes place as the code is written. Continuous integration means that others begin using code as soon as it is first tested and reviewed.
- Continuous peer review process catches problems earlier, when they are less expensive to correct. (And less embarrassing!)
- The combination of continuous documentation, continuous review, continuous testing, and continuous integration results in continuous quality improvement. In this case, traditional system level testing is trivial.

[ prev | top | next ]