configuration management

The IDE has emerged as the de-facto development tool in many Java shops. As the Java IDE evolved, team support became an important aspect of the tool and plays a prominent role in the popular Java development environment, IBM WebSphere Studio Application Developer 5.0 (WSAD). The clean design of the SCM interface to WSAD means configuration managers do not need to craft a custom solution to integrate their organization’s SCM tool with the IDE.

It seems so obvious that we should develop systems based on requirements, and yet it turns out to be rather hard to do and thus many organizations are doing it very badly. From a software configuration management standpoint, we could perhaps leave the whole process of requirements engineering to one side and focus on the management of requirements and thus the aspects of change control and traceability. That would perhaps be unduly ducking the issue, and, of course, we can’t resist giving an opinion anyway!

Abstract
No one wants to deliver a poor-quality product. But our projects often seem like a struggle between the Quality Assurance personnel and those who have other jobs. Do some people really not care about quality? If that is not the case, then why does it so often seem that way?

Performing an SCM product evaluation is important so that the product selected meets the needs of the application being developed. Typically, there is not as much time spent evaluating SCM products as needed, even though an SCM product will be one of the more highly used tools in the application lifecycle. It is with this in mind that it is important to understand the levels of an SCM product evaluation and the level of risk each assumes.