Titlebook: System Configuration Management; ECOOP‘98 SCM-8 Sympo Boris Magnusson Conference proceedings 1998 Springer-Verlag Berlin Heidelberg 1998 Co

Mettle

Coordinated editing of versioned packages in the JP programming environment,This framework also supports a streamlined user model for editing that keeps users‘ version awareness to an absolute minimum during routine development tasks. This architecture relies on two key technologies: orthogonally persistent object storage, and orthogonal versioning of hierarchical, immutable, source objects.

断断续续

0302-9743 tion with ECOOP‘98 in Brussels, Belgium, in July 1998..The volume presents 17 revised full papers carefully reviewed and selected for presentation; also included is a tutorial lecture; approximately half of the papers come from industry. The book is divided into sections on industrial experience, ex

CON

Industrial experiences from SCM current state analysis,fying goals for new practices. An industrial experiment employing SCM requirements analysis has been carried out in the VISCOUNT. project. The results of requirements analysis, and the advantages of the approach are presented, including a plan for future, work where virtual software corporations will be supported by advanced SCM systems.

BADGE

Change measurements in an SCM process, them give information not only about the amount and type of changes but also about the change process behavior. The measurements, generated from CRs by a tool, are used during the development process and in the final analysis of the project. The paper presents some of the measurements showing typical cases of lifecycle models.

Fecundity

PRCS: The project revision control system,mentation uses RCS in the back-end, the interface completely hides its presence. PRCS is free. This paper describes the advantages and disadvantages of our approach, and discusses implementation issues.

Congruous

Software configuration management and engineering data management: Differences and similarities,able in the EDM domain because they are based on assumptions which do not hold there (objects represented as text files, tools operating towards the file system). Some suggestions for further work on version models and on the architecture of version support systems are outlined.

PACT

Versioning system models through description logic,nsuring configuration completeness and consistency. The integrated version set model has been realized in ICE MAKE, a MAKE clone dealing with versioned system models. ICE MAKE constructs arbitrary version sets according to their respective dependencies and deduces features and dependencies as imposed by the propagated configuration constraints.

Meander

HALL

权宜之计

Experiences with architectural software configuration management in Ragnarok,unifying the concepts version and bound configuration. Experiences with such a model, implemented in a prototype “Ragnarok”, from three real-life, small- to medium-sized, software development projects are reported. The conclusion is that the presented model is viable and “feels natural” for software developers.