The problem of CASE tool integration has several concerns that overlap with those of configuration management (CM), so much so that a discussion of one topic is often difficult to separate from a discussion of the other. To illustrate, we note that when choosing a solution to a problem in configuration management, we often must make choices that involve understanding process requirements, examining the services available (and their semantics), and analyzing implementation constraints. We also note that these activities are done simultaneously with making design trade-off decisions related to the integration of these process, service, and mechanism concepts. These factors are applicable to CM, but are not particular to CM: most of these same issues underlie any set of decisions one makes about combining a set of CASE tools into an integrated environment. However, CM and its relationship to CASE tool integration in general poses a unique set of problems. This is most apparent when we realize that CM is sometimes considered as a service (or set of services) provided by the environment or its framework, sometimes as a service provided by a separate stand-alone tool, and sometimes as an integral aspect of each individual CASE tool. These competing views lead to overlaps in functionality and responsibility between individual tools and the environment’s (or framework’s) CM capabilities. For instance: • A fundamental issue for CM is data redundancy. This results when different tools store the same data in separate repositories. Correspondingly, different data models may make data sharing (a fundamental issue for tool integration) difficult. • Version management (VM) and CM services provided by individual tools are frequently linked with private tool data model and data management services. These VM and CM services are not always delegable — sometimes these services are an intricate part of tool function (e.g., for multi-user support and build). • The VM and CM services provided by individual tools may imply or enforce vendor-specific VM/CM policies, as opposed to the CM policies of the environment.