Distributed con guration management is intended to support the activities of projects that span multiple sites. NUCM is a testbed that we are developing to help us explore the issues of distributed con guration management. NUCM separates con guration management repositories (i.e., the stores for versions of artifacts) from con guration management policies (i.e., the procedures by which the versions are manipulated) by providing a generic model of a distributed repository and an associated programmatic interface. This paper describes the model and the interface, presents an initial repository distribution mechanism, and sketches how NUCM can be used to implement two, rather di erent, con guration management policies, namely checkin/check-out and change sets.

. The introduction of Java has been heralded as a revolution in network computing. Certainly, machine and operating system independent applets flittering through the Internet promised to jazz up web surfing; but could they be used to advantage for distributed computing ? The authors had encountered substantial problems in implementing a distributed revision control system, called WWRC, based on passive Web browsers. Java seemed to offer solutions to these problems. To this end, the authors have developed WWCM, a successor to WWRC written in Java. WWCM extends the concepts of WWRC to distributed configuration management by using CME---a new configuration management API. WWCM demonstrates that most of the design difficulties encountered with WWRC can be solved with Java. Furthermore, WWCM offers a test bed for a configuration management paradigm called template regulated alternative development. 1 Introduction There has been a flurry of development pertaining to the Intern...

Despite the growing number of organizations that have lost track of their application landscape and have suffered from a sharp increase in application portfolio complexity, a comprehensive and systematic approach to Application Portfolio Management (APM) still appears far from being adopted. To move the adoption process along, this paper develops a comprehensive framework assimilating and extending previous research and presents an APM process comprising data collection, analysis, decision-making, and optimization phases. This paper also presents an approach for evaluating software tools for APM and identifies which software tool families are best able to provide support for specific purposes. With this integrated conceptual guideline for APM and its translation into a model for measuring appropriate practical support, this paper not only allows for a move more deeply into the research area but also offers advice for both researchers and practitioners.