Change Management
Articles
CM Generations and a Vision for the Future It was 1978 when I first introduced change packages (a.k.a. updates) as the central feature of an in-house CM system. It's still in use today supporting a 40 million LOC project. It was 1982 when I introduced the concept of streams to rationalize branching along the product roadmap. Little did I know that a quarter century later, these concepts would just be starting to move to the forefront. |
||
Learning from Concurrent, Parallel, and Distributed Systems Design This month we do a bit of a context switch from the world of parallel development to the world of concurrent, parallel, and distributed systems design (and then back again). The purpose is to see if any of the same patterns of concurrent, parallel, and distributed processing apply to the case of concurrent, parallel, and distributed development. |
||
Bug Counts vs. Test Coverage Occasionally, we encounter projects where bug counts simply aren't as high as we expect. Perhaps the product under test is in its second or third release cycle, or maybe the development team invested an inordinate amount of time in unit testing. Whatever the reason, low bug counts can be a cause of concern because they can indicate that pieces of functionality (which potentially contain bugs) are being missed. When low bug counts are encountered, management may begin to wonder about the quality of testing. This article covers techniques for dealing with low bug counts, and methods for reassuring management that coverage is being achieved. |
Andrew Lance
March 21, 2002 |
|
Beyond Compare 3 for Testers: An Evaluation This article is an evaluation of Beyond Compare as it can be used in a software testing context. Jey and Areeb discuss what the tool does, specific ways it is used, similar tools, learning curves, support, and licensing. |