configuration management

Michael Sayko introduces CruiseControl, which enables the implementing CI of Java applications. Using CruiseControl's build loop, dashboard, and build resultsJSP, Michael shows how any Java development team can receive added value through this open source tool.

In Turbulent economic times such as the recent days, it is reasonable to assume that while some things will be reduced or cut, (e.g. human resources and budgets), others (e.g. documentation) will be maintained or even increased. So, what can we do to create effective and accurate CM Plans?

In this article I'd like to show some essential points for effective CM planning, which can offer a solution of reducing costs, based on the IEEE 828 standards. Basically, the goal is to reduce quantity but not quality.

Within the test scene there is a vivid discussion about the necessity and use of a certification model for the test experts. The population of testers can be roughly divided into two groups: Firstly, a group that states that it will not do a better job when certified, because the current certifications like ISTQB and ISEB focus on methods and terminology, but fail to look at the practical testing skills of the tester [Bolton, 2008]. Secondly, a group who is pro certification and regards the testing industry as a young yet not fully grown profession that lacks certification models that other professions have been using for ages [Windsor 2007]. Meanwhile, voices are heard that the test profession is accepted in the IT industry and that it has actually grown into a mature profession. The website of the last EuroSTAR conference stated that a mature profession has clearly-defined standards, codes of conduct, and a number of levels of professional competence. Having all those, we might conclude that the testing profession has indeed earned its place among the IT-professions.

I've seen countless sets of requirements and RFIs come my way for acquiring new CM/ALM tools. However, it is a very rare occasion when I see a company actually publish (and send out) the project CM Plan to potential tool vendors. In my most recent encounter of this approach, the pitch was: How would you change this plan based on your CM/ALM solution for us? This project has it right—not just a set of requirements, but an actual CM Plan, and not so much, "What does your tool do?" as, "What will our CM Plan look like with your solution?"